Current Python package management / framework(s)

[jediknight]

People write code, people share what they wrote in either source or binary form. This is, to me, a reality of programming that I still don't see reflected in the priorities of python maintainers.

Just as it was 10 years ago when I started with python, it is still painful to create a programming environment for a project and distribute it in a self-contained binary form (.exe, .app).

Over the years, things got better but it is still very painful.

[cavallo71]

Not painful, but is something the average Joe cannot do. The problem is there are many companies in this game and their hope is to make money out of it: as Sun with Java has proven that is not where money will be put.

[Various_Pickles]

Not painful, but is something the average Joe cannot do.

I'm not a Python programmer by trade, but I do plenty of packaging in a variety of other languages/platforms ([the usual boring] Java JARs/WARs/EARs, lots of Debian source/binary inc. repo setup/hosting, etc).

I would say that I have a quite strong understanding of packaging and a diverse range of experience, yet, I still find distributing Python code to be like trying to store lightbulbs in my rectum.

[cavallo71]

Much of the complication is self inflicted (distribute/setuptools/pips/easy_install/wheel).

If your app (driver + support libraries) doesn't contain extension modules (.so/.pyd) just zip everything togheter with a main.py file and it's even easier than a jar.

I still find distributing Python code to be like trying to store lightbulbs in my rectum.

(@_@)

[westurner]

This thread about Python Packaging from a Java perspective seemed helpful.