List of useful npx (NPM Package Runner) commands.
Using NPX we can execute/run node binaries without the need to install it locally or globally.
List of useful npx (NPM Package Runner) commands.
Using NPX we can execute/run node binaries without the need to install it locally or globally.
import logging | |
import pexpect | |
from airflow.hooks.base_hook import BaseHook | |
class SFTP(object): | |
""" | |
Requires openssh_client. Spawns process to execute sftp command. | |
""" |
""" | |
An alternative text clip for Moviepy, relying on Gizeh instead of ImageMagick | |
Advantages: | |
- Super fast (20x faster) | |
- no need to install imagemagick | |
- full-vector graphic, no aliasing problems | |
- Easier font names | |
Disadvantages: |
to check if the server works - https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice | |
stun: | |
stun.l.google.com:19302, | |
stun1.l.google.com:19302, | |
stun2.l.google.com:19302, | |
stun3.l.google.com:19302, | |
stun4.l.google.com:19302, | |
stun.ekiga.net, | |
stun.ideasip.com, |
This procedure explains how to install MySQL using Homebrew on macOS Sierra 10.12
$ /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
At this time of writing, Homebrew has MySQL version 5.7.15 as default formulae in its main repository :
Using py.test is great and the support for test fixtures is pretty awesome. However, in order to share your fixtures across your entire module, py.test suggests you define all your fixtures within one single conftest.py
file. This is impractical if you have a large quantity of fixtures -- for better organization and readibility, you would much rather define your fixtures across multiple, well-named files. But how do you do that? ...No one on the internet seemed to know.
Turns out, however, you can define fixtures in individual files like this:
tests/fixtures/add.py
import pytest
@pytest.fixture
""" | |
TL/DR: | |
Never instantiate mock.Mock() directly. | |
Instead use either mock.create_autospec(YourClass) OR mock.patch('YourClass', autospec=True). | |
The "spec" feature of Mock is great, it helps avoid your mocked API drifting out of sync with your real API. | |
But there is a gotcha if you are mocking classes directly - it's easy to mock the class but you need to | |
ensure the spec applies to the *instance* as well. | |
""" |
/* | |
* I add this to html files generated with pandoc. | |
*/ | |
html { | |
font-size: 100%; | |
overflow-y: scroll; | |
-webkit-text-size-adjust: 100%; | |
-ms-text-size-adjust: 100%; | |
} |