How To Package Your Python Code • Hacker News Board

Re: How To Package Your Python Code

#31

Post by dearmash » Mon, Nov 19, 2012, 5:13 PM UTC

doesnt_know wrote: post #25

dearmash wrote: post #24

I apologize for the spam, but apparently I'm unable to save articles for some reason. I'd like to read this later, and I want to see if a comment will work.

If only there was some way to save a url within the software that we use to browse the web. That would be an incredibly useful feature, someone here should consider developing an addon or put in a feature request for such a thing.

Touche. Rather than ask other people if there exist issues with the intended story saving and voting features, I will start using browser bookmarks. Thank you for your valuable feedback. Pre-emtpive: "I know this is not the proper place to file a 'bug-report'"

*edit: not alone (semi-old) http://news.ycombinator.com/item?id=4164468

Re: How To Package Your Python Code

#32

Post by norlowski » Mon, Nov 19, 2012, 7:09 PM UTC

Awesome job. I had been stressing about getting my code up there but your tutorial made it easy.

Re: How To Package Your Python Code

#33

Post by cdavid » Tue, Nov 20, 2012, 8:11 AM UTC

pak wrote: post #29

The fact that there is no good, canonical guide for doing this in Python is one of the reasons I moved away from it and toward Ruby. With Ruby I had no problems writing and forking gems using the canonical guide ( http://guides.rubygems.org/make-your-own-gem/ ). With Python, navigating the hell that is packaging is just demoralizing when it comes time to give end users a complicated chunk of code. (Setuptools is trul…

if setuptools is a hack on top of bad design, distribute has exactly the same issues, since it is simply a fork that was started because of the impression that setuptools dev was stalled. None of the (numerous) design issues from setuptools have been fixed in distribute.

Re: How To Package Your Python Code

#34

Post by JulianWasTaken » Tue, Nov 20, 2012, 10:47 PM UTC

borntyping wrote: post #11

JulianWasTaken wrote: post #2

Taking a quick look through this it looks pretty good! I find that beginners have tons of trouble navigating the slightly tricky waters that is packaging in Python, so more resources is great. One thing I think is missing is to point out not to use setuptools, but to use the less broken, more maintained, drop in replacement distribute ( http://guide.python-distribute.org/ ). That website also has some further informa…

Doesn't distribute miss out on a few of setuptools really useful features, like develop installs?

It has develop. I rarely use it, but it's there. AFAIK it is not missing any features that setuptools has but I stick to the simple stuff.

Re: How To Package Your Python Code

#35

Post by JulianWasTaken » Tue, Nov 20, 2012, 10:48 PM UTC

storborg wrote: post #3

JulianWasTaken wrote: post #2

Taking a quick look through this it looks pretty good! I find that beginners have tons of trouble navigating the slightly tricky waters that is packaging in Python, so more resources is great. One thing I think is missing is to point out not to use setuptools, but to use the less broken, more maintained, drop in replacement distribute ( http://guide.python-distribute.org/ ). That website also has some further informa…

Thanks, I'll definitely add that to the "See Also" section. Can you elaborate on the places where setuptools is broken? I wanted to keep things as simple as possible for the sake of this tutorial, and I think the described constraints should avoid any setuptools bugs.

There are various posts on the distribute/setuptools/distutils mailing list. I don't keep track personally, but I do know that it's pretty widely accepted at this point to use distribute.

Re: How To Package Your Python Code

#36

Post by [deleted] » Tue, Nov 20, 2012, 10:48 PM UTC

storborg wrote: post #3

JulianWasTaken wrote: post #2

Taking a quick look through this it looks pretty good! I find that beginners have tons of trouble navigating the slightly tricky waters that is packaging in Python, so more resources is great. One thing I think is missing is to point out not to use setuptools, but to use the less broken, more maintained, drop in replacement distribute ( http://guide.python-distribute.org/ ). That website also has some further informa…

Thanks, I'll definitely add that to the "See Also" section. Can you elaborate on the places where setuptools is broken? I wanted to keep things as simple as possible for the sake of this tutorial, and I think the described constraints should avoid any setuptools bugs.

[deleted]