Hi Ralf, very cool! Just needs some fixing for Python3. I just gave your write access on bitbucket py-trunk - would you care to add bin-for-dist/generate_standalone_pytest.py? (if in doubt i can do the python3 fixing)
And do you think it makes sense to honour "py.XYZ" symlinks pointing to 'py.test' which would make the other tools available without duplication? cheers, holger On Wed, Dec 23, 2009 at 17:13 +0100, sch...@gmail.com wrote: > holger krekel <hol...@merlinux.eu> writes: > > > > >> spurred by this discussion I'm now creating a single file py.test script > >> which includes the whole py library. This would allow people to drop > >> that script in ~/bin/ and run it with any virtualenv they are using > >> *without* installing the py lib first (well strictly speaking it is > >> installed as a single file). What do you think about that? > > > > Interesting. Curious how you approach this. Encoding a zip-file into > > the single-file? There is the matter of startup-time because > > there would be no sensible '.pyc' files. But OTOH distributing a > > single script is useful enough to make up for this penalty. > > If you try this and have issues feel free to drop by #pylib on freenode > > or mail here for help. > > it uses base64-encoded zlib-compressed pickled source code and a custom > importer object. > > I've created a git repo on github: > http://github.com/schmir/standalone-py.test > > You'll have to run the following commands in order to checkout and > create a single file: > > ,---- > | git clone git://github.com/schmir/standalone-py.test.git > | python standalone-py.test/generate-single-file.py > | cp standalone-py.test/py.test ~/bin/ > `---- > > or you could download the script from: > > http://schmir.github.com/standalone-py.test/py.test > > I'm also attaching a patch against py-1.1.1. > > Regards, > - Ralf > -- _______________________________________________ py-dev mailing list py-dev@codespeak.net http://codespeak.net/mailman/listinfo/py-dev
