Mailman 3 December 2005 - Distutils-SIG

Updated installation instructions for EasyInstall/setuptools
by Phillip J. Eby 16 Dec '05

16 Dec '05

I just checked in (and updated on the Wiki) the installation instructions for setuptools and EasyInstall to cover a lot of frequently-asked questions and problems (e.g. how do I install without net access?), as well as to explain additional approaches to custom installation locations. The new docs on custom installation are at: http://peak.telecommunity.com/DevCenter/EasyInstall#custom-installation-loc… And the main installation instructions, now with better troubleshooting and alternatives information, is at: http://peak.telecommunity.com/DevCenter/EasyInstall#installation-instructio… Please let me know whether these are more helpful than the old versions. I've also added a new section to the setuptools manual called "What Your Users Should Know": http://peak.telecommunity.com/DevCenter/setuptools#what-your-users-should-k… This section provides developers using setuptools with notes on what they should tell users about installing their project -- such as that they should read the "custom installation" docs if they plan to install anywhere but the primary site-packages, and tips on issues ranging from system packaging (0.6a9dev+ only) to lack of network access. Feedback on this new manual section would also be appreciated. There is only one more feature I'm planning to add before the official release of setuptools 0.6a9: support for building and installing shared libraries linked to Python extensions. If you are not using the 0.6a9 development version yet, I encourage you to upgrade as soon as practical so that I can address any problems you find before making the official release. To install the in-development version, just run: ez_setup.py setuptools==dev after first making sure you have done any pre-installation steps described by the updated installation instructions above. Thanks, and please let me know of any questions or problems you may have with any of the above.

1 0

Naming conventions for module unit tests?
by Todd Greenwood-Geer 15 Dec '05

15 Dec '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 To the list : Anyone have any good naming conventions for module tests? [module name]_unittest.py test_[module_name].py unittest_[module_name].py Then there's the issue of differentiating unit tests from functional tests, scenario tests... Here's my off the cuff definition for these things: unit test : fine grained tests, usually testing individual methods functional test : coarser grained tests, usually testing an aggregation of methods, usually a single module scenario tests : even coarser grained tests, not focused on code testing per se, focused on testing actual usage scenarios from beginning to end. Then there are the aggregations of tests, drts and bvts. Anyone out there come across a useful naming structure for all this? Perhaps: [aggregation]_[level]_[module].py drt_unittest_foo.py bvt_functionaltest_foo.py Or am I overly complicating things again? - -Todd John J Lee wrote: | On Sat, 10 Dec 2005, Todd Greenwood-Geer wrote: | |> -----BEGIN PGP SIGNED MESSAGE----- |> Hash: SHA1 |> |> Thanks John. That was biting me in several places. Is there a standard |> practice/naming convention for module unit tests? I was trying something |> like [module name]_unittest.py. | | That's a list question, surely -- post to the list! | | | John | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDoGHuz6uXX4lQc/URAntjAJ0UAs/e4CP7LO/y0w/ukO57TSRoVQCaApbC 1My/W9koS6HaJ1aeh4pGdWU= =eWeG -----END PGP SIGNATURE-----

3 2

Splitting large packages into multiple eggs
by Bob Ippolito 14 Dec '05

14 Dec '05

I'm currently refactoring PyObjC and py2app to be setuptools- friendly, but one issue I'm coming across is that PyObjC is a large package, and normally people wouldn't want to include all of it. The way to do that would be to split it up into lots of eggs, so py2app can include the subset of eggs that are necessary. The issue at hand is how to structure the setup.py to support creation of multiple eggs, with an egg for installation purposes that depends on everything. PyObjC can be broken up into about 30 eggs, one for each package, one for the Xcode support (which depends on py2app and altgraph), one for all of the tests (or maybe separate eggs for each test suite). Obviously I'm not looking to create 30+ setup.py files, so what do I do? -bob

4 7

Re: [Distutils] local development scenarios
by Phillip J. Eby 14 Dec '05

14 Dec '05

At 06:22 PM 12/10/2005 -0800, tgreenwood wrote: >Phillip - >Perhaps this is another obvious rtfm question, but here goes. How can I >add custom actions to the build? I'm used to writing ant scripts to >create build targets and chain dependencies, etc. > >In the python/egg world, I'd like to do the same thing. For instance, >I'd like to define a target that would: >~ - generate the egg ala bdist_egg >~ - generate my restructured text documentation (vim.vst)...not sure how >to call this from vim yet, but I'm sure it's possible >~ - run my unittest suite >~ - deploy resulting egg to my ftp site The 'alias' command lets you define new "setup.py" commands as a combination of existing commands: http://peak.telecommunity.com/DevCenter/setuptools#alias-define-shortcuts-f… The 'upload' command sends eggs and/or source distributions to PyPI: http://peak.telecommunity.com/DevCenter/setuptools#upload-upload-source-and… And you can extend setuptools with new commands via entry points, although usually it's best to package these in a separate egg from the project you will use them on: http://peak.telecommunity.com/DevCenter/setuptools#creating-distutils-exten… http://peak.telecommunity.com/DevCenter/setuptools#adding-commands

2 3

Re: [Distutils] bdist_nsis, bdist_deb, bdist_msi, bdist_inno, bdist_pkgtool, bdist_sdux, etc.
by M.-A. Lemburg 14 Dec '05

14 Dec '05

Martin v. Löwis wrote: > M.-A. Lemburg wrote: >> Would any of the authors (I've tried to CC them) be willing to >> contribute their distutils command to the PSF for integration ? > > I was hoping to contribute bdist_msi before 2.5. Before that, I need > atleast two more releases; I have some feedback on which I haven't > reacted on, yet. Would be nice for have bdist_msi in 2.5, but it's good to know that this is on your schedule. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Dec 14 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::

1 0

eggs on distutils-sig
by M.-A. Lemburg 13 Dec '05

13 Dec '05

Hi everybody, as you may have noticed, the distutils-sig list has recently gotten flooded with setuptools (egg generator) related postings. While setuptools is a nice add-on for distutils, the discussions around it do not necessarily bring the distutils package itself forward. I'm wondering whether we should ask the eggs fans to start a new mailing list for egg support and development. What do you think ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Dec 07 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::

7 7

Re: [Distutils] [Pyobjc-checkins] [PyObjC-svn] r1763 - in branches/pyobjc-setuptools: . Lib/pyobjc.egg-info
by Bob Ippolito 12 Dec '05

12 Dec '05

On Dec 11, 2005, at 1:45 PM, Ronald Oussoren wrote: > On 11-dec-2005, at 22:26, bob(a)red-bean.com wrote: > >> Author: bob >> Date: Sun Dec 11 15:26:36 2005 >> New Revision: 1763 >> >> Modified: >> branches/pyobjc-setuptools/Lib/pyobjc.egg-info/PKG-INFO >> branches/pyobjc-setuptools/Lib/pyobjc.egg-info/requires.txt > > Should these be in the repository in the first place? AFAIK > the .egg-info directory is created and maintained by setuptools. I don't know, I've seen them in other repositories and there's one in setuptools itself. -bob

2 1

Installing stuff using setuptools w/ Python from CVS HEAD?
by skip＠pobox.com 10 Dec '05

10 Dec '05

On my Mac Powerbook (OSX 10.3.9) I routinely use Python built from CVS HEAD as my day-to-day Python interpreter. Today I tried installing Myghty 0.99a using that interpreter: % python setup.py easy_install . --------------------------------------------------------------------------- This script requires setuptools version 0.6a5 to run (even to display help). I will attempt to download it for you (from http://cheeseshop.python.org/packages/2.5/s/setuptools/), but you may need to enable firewall access for this script first. I will start the download in 15 seconds. --------------------------------------------------------------------------- Downloading http://cheeseshop.python.org/packages/2.5/s/setuptools/setuptools-0.6a5-py2… Traceback (most recent call last): File "setup.py", line 2, in <module> use_setuptools() File "/Users/skip/src/Myghty-0.99a/ez_setup.py", line 74, in use_setuptools egg = download_setuptools(version, download_base, to_dir, download_delay) File "/Users/skip/src/Myghty-0.99a/ez_setup.py", line 122, in download_setuptools src = urllib2.urlopen(url) File "/Users/skip/local/lib/python2.5/urllib2.py", line 130, in urlopen return _opener.open(url, data) File "/Users/skip/local/lib/python2.5/urllib2.py", line 367, in open response = meth(req, response) File "/Users/skip/local/lib/python2.5/urllib2.py", line 475, in http_response 'http', request, response, code, msg, hdrs) File "/Users/skip/local/lib/python2.5/urllib2.py", line 405, in error return self._call_chain(*args) File "/Users/skip/local/lib/python2.5/urllib2.py", line 340, in _call_chain result = func(*args) File "/Users/skip/local/lib/python2.5/urllib2.py", line 483, in http_error_default raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) urllib2.HTTPError: HTTP Error 404: Not Found Even "python setup.py --help" doesn't work. I can understand that there's no packages/2.5 directory on cheeseshop yet. Is there a way to work around this problem? Thx, -- Skip Montanaro Katrina Benefit Concerts: http://www.musi-cal.com/katrina skip(a)pobox.com

2 2

Determining if a module is in an egg or not
by Bob Ippolito 09 Dec '05

09 Dec '05

I started refactoring py2app, modulegraph, etc. for setuptools and eggs. After doing dependency resolution via modulegraph, py2app needs to know which of those dependencies are in eggs and where those eggs are so that it can just throw the egg (and its dependencies) into the application bundle instead of doing the normal py2app thing. Is there an API to map __file__ paths to eggs? It seems possible for zip and directory eggs by walking up os.path.dirname(__file__) and using find_distributions, but that doesn't seem to work for "setup.py develop" eggs. -bob

2 1

Using printf from within a C extension
by mike cantor 09 Dec '05

09 Dec '05

Hi, I am extending python with C and trying to debug with printf. The code below succssfully returns the string "hello" when compiled and called, but the "can print from in here phrase" does not reach python stdout. Is there something screwy with my environment or is there some trick to this that I don't know. Any help would be greatly appreciated! -mike #include <Python.h> static PyObject* helloworld(PyObject* self) { printf("can print from in here?"); return Py_BuildValue("s", "hello"); } static char hw_docstr[] = "hello docstr"; static PyMethodDef hw_funcs[] = { {"helloworld", (PyCFunction)helloworld, METH_NOARGS, hw_docstr}, {NULL} }; void inithelloworld(void) { Py_InitModule3("helloworld",hw_funcs, "simple module"); }

2 1