On approximately 1/27/2010 1:08 AM, came the following characters from the keyboard of Glenn Linderman: > Without reference to distutils, it seems the pieces are: > > 1) a way to decide what to include in the package > 2) code that knows where to put what is included, on one or more > platforms > 3) the process to create the ZIP file that includes 1 & 2, and call it > an appropriate name.py > > 3 looks easy, once 1 & 2 are figured out. distutils might provide the > foundation for 1. 2 sounds like something a distutils application > might create. I'm not sure that distutils is in the business of > building installer programs, my understanding is that it is in the > business of providing a standard way of recording and interpreting > bills of materials and maybe dependencies, but that is based only on > reading discussions here, not reading documentation. I haven't had a > chance to read all the module documentation since coming to python. 3 was rather easy, and has come in handy for me, as it turned out: see http://code.activestate.com/recipes/577042/ -- Glenn -- http://nevcal.com/ =========================== A protocol is complete when there is nothing left to remove. -- Stuart Cheshire, Apple Computer, regarding Zero Configuration Networking
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4