You might want to read https://www.dfwpython.org/repo/Presentations/2008-10-04-PyArkansas-PythonEggsIntro/eggs-introduction.pdf
It covers a lot of ground; I used it to work out how to distribute a pure Python package, but I am sure it mentions compiled packages too. In my case I ended up using setuptools (easy_install) and distutils. (Not sure if you asking just about compiling, or more general packaging, but IIRC it covers both). Andrew Travis wrote: > So, > > Recently I made a fix to the zlib module that I need for use at work. > > I would like other employees to be able to use it without recompiling > python. > > I assume I can just rename it and distribute it as a python extension. > > I was wondering how I can provide a way for other employees to build it. > > I saw a "Universal Unix Makefile for Python extensions" that looks > promising. > > Is this the accepted way to compile python extensions still? > -- > Crypto ergo sum. http://www.subspacefield.org/~travis/ > Do unto other faiths as you would have them do unto yours. > If you are a spammer, please email j...@subspacefield.org to get > blacklisted. > -- > http://mail.python.org/mailman/listinfo/python-list > > -- http://mail.python.org/mailman/listinfo/python-list
