Distributed self-replicating programs in Python
Go to file
Alex Willmer 29529c9a5c tests: Fix GetModuleViaPkgutilTest fetching .pyc
On my laptop (Ubuntu 17.10, Python 2.7.14 in a virtualenv),
`test_regular_mod` fails with

```
AssertionError: "\nimport sys\n\n\ndef say_hi():\n    print 'hi'\n" !=
'\x03\xf3\r\n\xbbW\xd5Yc\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x00\x00@\x00\x00\x00s\x19\x00\x00\x00d\x00\x00d\x01\x00l\x00\x00Z\x00\x00d\x02\x00\x84\x00\x00Z\x01\x00d\x01\x00S(\x03\x00\x00\x00i\xff\xff\xff\xffNc\x00\x00\x00\x00\x00\x00\x00\x00\x01\x00\x00\x00C\x00\x00\x00s\t\x00\x00\x00d\x01\x00GHd\x00\x00S(\x02\x00\x00\x00Nt\x02\x00\x00\x00hi(\x00\x00\x00\x00(\x00\x00\x00\x00(\x00\x00\x00\x00(\x00\x00\x00\x00sF\x00\x00\x00/home/alex/src/mitogen/tests/data/module_finder_testmod/regular_mod.pyt\x06\x00\x00\x00say_hi\x05\x00\x00\x00s\x02\x00\x00\x00\x00\x01(\x02\x00\x00\x00t\x03\x00\x00\x00sysR\x01\x00\x00\x00(\x00\x00\x00\x00(\x00\x00\x00\x00(\x00\x00\x00\x00sF\x00\x00\x00/home/alex/src/mitogen/tests/data/module_finder_testmod/regular_mod.pyt\x08\x00\x00\x00<module>\x02\x00\x00\x00s\x02\x00\x00\x00\x0c\x03'
```

`__file__` contains the path of the compiled `.pyc`, not the `.py`
source file.
2017-10-20 19:48:26 +01:00
docs docs: convert paragraph to footnote. 2017-10-16 17:56:23 +05:30
examples mitop: fix overlong command lines corrupting the followign line 2017-10-05 22:41:51 +05:30
mitogen first stage: Remove/dedent else block 2017-10-18 00:34:14 +01:00
tests tests: Fix GetModuleViaPkgutilTest fetching .pyc 2017-10-20 19:48:26 +01:00
.gitignore gitignore: distutils output files 2017-10-08 14:28:28 +01:00
.travis.yml Add first_stage_test to Travis. 2017-10-16 20:53:40 +05:30
README.md Fix lnik. 2017-10-02 17:32:53 +05:30
dev_requirements.txt Add mock requirement 2017-10-06 23:30:44 +01:00
preamble_size.py Remove context.key from preamble_size.py too. 2017-09-27 14:02:01 +05:30
setup.py setup: Trove classifiers 2017-10-08 14:27:30 +01:00

README.md

Running The Tests

Build Status

Your computer should have an Internet connection, and the docker command line tool should be able to connect to a working Docker daemon (localhost or elsewhere for OS X etc.) that can run new images.

The IP address of the Docker daemon must allow exposing ports from running containers, e.g. it should not be firewalled or port forwarded.

If in doubt, just install Docker on a Linux box in the default configuration and run the tests there.