- 25 Mar, 2012 2 commits
-
-
Luke Macken authored
-
Luke Macken authored
-
- 24 Mar, 2012 10 commits
-
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
- Create a new pyrasite.tests.utils module - Popen(shell=True) was causing our test suite not to run on ubuntu - Use a pidfile to know when a program is running, and rm to stop it
-
Luke Macken authored
This makes it easier to share code within our test modules, while being able to write imports that work on py2.4 through 3.
-
Luke Macken authored
-
- 23 Mar, 2012 4 commits
-
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
- 22 Mar, 2012 11 commits
-
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
- 21 Mar, 2012 12 commits
-
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
-
Luke Macken authored
Conflicts: pkgs/fedora/pyrasite.spec pyrasite/__init__.py setup.py
-
Luke Macken authored
-
Luke Macken authored
-
- 20 Mar, 2012 1 commit
-
-
Luke Macken authored
pyrasite.inject will now do this for us, to ensure that our payloads can always 'import pyrasite'
-