Comments for ( f o o b a r . l u )

Comment on A comprehensive guide through Python packaging (a.k.a. setup scripts) by exhuma

exhuma — Sat, 19 May 2012 10:14:00 +0000

You are correct… I think this was a copy paste error
It’s fixed now. I also added tiny little bit of explanation around this topic. Thanks for the spot!

Comment on A comprehensive guide through Python packaging (a.k.a. setup scripts) by exhuma

exhuma — Sat, 19 May 2012 10:09:00 +0000

I tried it and got a max recursion error… I added the section to the post. Any idea what might go wrong?

Comment on A comprehensive guide through Python packaging (a.k.a. setup scripts) by exhuma

exhuma — Sat, 19 May 2012 08:59:00 +0000

Interesting. Good to know. I’ll edit it into the post!

Comment on A comprehensive guide through Python packaging (a.k.a. setup scripts) by Anon

Anon — Fri, 18 May 2012 14:17:00 +0000

Also, according to the following comment, `python setup.py develop` obsolete with pip: http://stackoverflow.com/questions/3606457/removing-python-module-installed-in-develop-mode#comment10771810_3606457

Comment on A comprehensive guide through Python packaging (a.k.a. setup scripts) by Anon

Anon — Fri, 18 May 2012 13:29:00 +0000

Excellent guide - thanks! I’m missing a note to set include_package_data=True though; I thought this was required for MANIFEST.in to work correctly?

Comment on A comprehensive guide through Python packaging (a.k.a. setup scripts) by guesty-guest-guest

guesty-guest-guest — Thu, 17 May 2012 20:54:00 +0000

For a beginner, this is definitely amazeballs. Thank you.

Comment on A comprehensive guide through Python packaging (a.k.a. setup scripts) by exhuma

exhuma — Tue, 15 May 2012 16:44:00 +0000

Interesting… I never ran into such problems… but then again, I only package as source dists. I never had the need to do a bdist. But when the day comes, I hope I’ll remember your comment

I will leave this as a comment and don’t edit it into the main article, as – in my opinion – this is something quite specific. And I don’t want to overcomlicate it.

Unless someone thinks this is essential of course…

Comment on A comprehensive guide through Python packaging (a.k.a. setup scripts) by Richard Jones

Richard Jones — Tue, 15 May 2012 00:05:00 +0000

Yes, it works identically to the Real PyPI. Thanks!

Comment on A comprehensive guide through Python packaging (a.k.a. setup scripts) by Alex Clark

Alex Clark — Mon, 14 May 2012 19:51:00 +0000

Whoah, poorly marketed indeed. Good to know about this, thanks!

Comment on A comprehensive guide through Python packaging (a.k.a. setup scripts) by Nicholas Retallack

Nicholas Retallack — Mon, 14 May 2012 19:50:00 +0000

To add some complication to this, if you want to build other package types like RPM (via bdist_rpm), setup will copy your whole source tree including the setup.py file, and then run it again in its new environment, with different arguments. This can be frustrating. I ended up adding some hooks into my setup.py file to detect whether it was in the first or second run, and change the arguments on the second run to match the first.

Also frustrating is attempting to build more than one package from the same setup.py file. Due to the copy-and-re-run thing, it will always look for a file called setup.py in the second phase regardless of what the first file was named, so you can’t really place two install scripts in the same place. It doesn’t know the arguments from the first run either, so it will forget which package it was building. If you have any comments to make these use cases easier, I’d love to hear em.