- 19 Mar, 2018 40 commits
-
-
David Wilson authored
-
David Wilson authored
It's used at least by the copy module, even though the result is still mostly a no-op. _remote_chmod() doesn't accept octal mode, it accepts symbolic mode. So implement a symbolic parser in helpers.py.
-
Alex Willmer authored
Fixes #90
-
Alex Willmer authored
Found due to a LGTM warning about unused loop variable (related). As far as I can tell the callback was sending fullname multiple times. KeyError check added because I found NestedTest failed - mitogen.parent had mitogen as one of it's related, and mitogen was not in the cache. Refs #61
-
Alex Willmer authored
Since the for loops don't contain any break statements the StreamErrors will always be raised when the loop completes without the method resturning. See https://lgtm.com/rules/5980098/ Refs #61
-
Alex Willmer authored
Refs #61
-
Alex Willmer authored
Both these addtions are to address warnings in https://lgtm.com/projects/g/dw/mitogen/alerts/?mode=list. Namely that if a class defines an equality method then it should also define an inequality and a hash method. Refs #61
-
Alex Willmer authored
This seemed a reasonable streamlining, but I'm happy to be overruled.
-
Alex Willmer authored
This documents the existing behaviour, which may not be the intended.
-
Alex Willmer authored
These test the current behviour, which may not be exactly the intended behaviour. Refs #98
-
David Wilson authored
-
David Wilson authored
-
David Wilson authored
Farewell, shifty hacker dude! May your 0days be many and your indictments be few
-
David Wilson authored
Some differences are eventually likely to become permanent, because the existing behaviour is unforgiveable.
-
David Wilson authored
Still needs a ton of work to emulate argument handling, shell selection, and output emulation in every case. Unsurprisingly, Ansible documents none of this.
-
David Wilson authored
Sending just via .call_async() would previously crash the child, now it generates CallError like intended.
-
David Wilson authored
-
David Wilson authored
-
David Wilson authored
-
Alex Willmer authored
Python 2.4 does not support explicit relative imports. They were added at Python 2.5, along with `from __future__ import absolute_import`. On 2.x this will mean the import is first (implicitly) tried relative, but on 3.x it will always be tried absolute. Fixes #92
-
David Wilson authored
-
David Wilson authored
-
David Wilson authored
-
David Wilson authored
-
David Wilson authored
-
David Wilson authored
-
David Wilson authored
-
Alex Willmer authored
Hopefully these are correct, and clearerabout the behaviour/pre-conditions of these methods.
-
Alex Willmer authored
-
Alex Willmer authored
Not sure how they got there, but Django doesn't use Jinja without explicit configuration.
-
Alex Willmer authored
-
Alex Willmer authored
-
Alex Willmer authored
This matches a tweak made in 8765f761c995c31c9bff6287d881f0e9b5d0cfc5
-
Alex Willmer authored
-
David Wilson authored
There is only so much trackpad-driven yEd work one man can handle
-
Alex Willmer authored
I took the liberty of renaming ModuleFinder.STDLIB_DIRS to _STDLIB_PATHS, since it felt like an implementation detail that shouldn't be baked into a public API and stdlib can also be imported from e.g. a zip file. I also changed it to a set to handle any duplicates. Fixes #86
-
David Wilson authored
-
David Wilson authored
-
David Wilson authored
-
David Wilson authored
-