Re: [Distutils] Which buildout to use?
Hi, I'm didn't follow the full thread so I apologize if I'm off topic If I remember correctly I had a couple of issues last year with numpy/ matplotlib and buildout because the two first weren't compliant with python packages. I think numpy got python packaging compatibility for 1.5.0 so if your numpy's system wide installation is lower than that you most probably have no python package information hence Regards, Xavier. ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Which buildout to use?
On 17-08-11 08:16, Xavier Ordoquy wrote: If I remember correctly I had a couple of issues last year with numpy/ matplotlib and buildout because the two first weren't compliant with python packages. I think numpy got python packaging compatibility for 1.5.0 so if your numpy's system wide installation is lower than that you most probably have no python package information hence I've got 1.5.1 with a proper numpy-1.5.1-py2.6.egg-info directory in the site-packages. But I also didn't trust numpy completely :-) , so I also did the tests with psycopg2: same result. Reinout -- Reinout van Reeshttp://reinout.vanrees.org/ rein...@vanrees.org http://www.nelen-schuurmans.nl/ If you're not sure what to do, make something. -- Paul Graham ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Which buildout to use?
On 17-08-11 04:23, Chris Withers wrote: Maybe pin numpy to the version provided by the system? Just a guess and nothing I've tried... *Partial hurray sound* Actually... that works. If I pin numpy to 1.5.1, buildout uses my site-packages one! We're one step further! Next hurdle: I don't want to pin that package, as I don't particularly care which numpy version it is as long as it is recent enough. If I pin 1.5.12, it'll be fine on my OSX machine, but ubuntu probably has a slightly different version. And our webserver might be hanging one ubuntu version back. So: is there a way to *force* buildout to use the site-packages one, regardless of the version? (Provided it matches some minimum version requirement in case I provided one, of course). I can't find it in the docs. osc.recipe.sysegg has a force-sysegg option that does just that. Reinout -- Reinout van Reeshttp://reinout.vanrees.org/ rein...@vanrees.org http://www.nelen-schuurmans.nl/ If you're not sure what to do, make something. -- Paul Graham ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] buildout-versions not showing pinned versions
Op 17-08-11 05:32, B.Nanda Kishore schreef: Well that was something new for me. Having two versions of the same package in the same buildout file. Actually I was installing a few distributions in my workplace. So some distros have version pinned in their setup.py install_requires section, and when I run the buildout expecting the versions to be printed, its not printing those alone. So mentioning the version was not in the buildout file originally, but I see your point of putting them in [versions] section. But tell me this. In the above example(pinning a version number in install_requires section of setup.py) expecting the version of the package to be printed is a valid usecase right ? Is it not ? I know from the example which you gave previously there seems to be some ambiguity from which version to pick if there are multiple versions. right ? Thats why its left out or ? The goal of buildout-versions (or its cousin buildout.dumppickedversions) is to list all packages that are not pinned. When a package is not pinned, buildout picks the most recent version. That may work today and fail horribly tomorrow if this unpinned package is updated in backwards incompatible ways. If buildout-versions prints anything I consider this an error in my buildout. If I agree the correct versions have been picked I add the printed versions to the [versions] section, rerun the buildout and now buildout-versions should not print anything anymore. In other words: buildout-versions does not print all versions, just the not-pinned ones that buildout has picked. Like Chris said, this is intentional. -- Maurits van Rees Web App Programmer at Zest Software: http://zestsoftware.nl Personal website: http://maurits.vanrees.org/ ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] buildout-versions not showing pinned versions
On Tue, Aug 16, 2011 at 10:14 PM, Chris Withers ch...@simplistix.co.uk wrote: *Why* are you pinning in the eggs line? At Zope, we've had to do this when different processes constructed by a build had to use different versions of libraries. buildout-versions aside, it's not that unusual a case. -Fred -- Fred L. Drake, Jr. fdrake at acm.org A person who won't read has no advantage over one who can't read. --Samuel Langhorne Clemens ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] buildout-versions not showing pinned versions
On 17/08/2011 05:40, Fred Drake wrote: On Tue, Aug 16, 2011 at 10:14 PM, Chris Withersch...@simplistix.co.uk wrote: *Why* are you pinning in the eggs line? At Zope, we've had to do this when different processes constructed by a build had to use different versions of libraries. buildout-versions aside, it's not that unusual a case. Indeed, I believe I did explain that usecase ;-) Myself, I'd just use multiple buildouts, and I don't think I've ever bumped into the situation you're describing, but nonetheless, if you've pinned the version some other way, then buildout-versions won't tell you that it hasn't been pinned... cheers, Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] buildout-versions not showing pinned versions
On 16/08/2011 20:32, B.Nanda Kishore wrote: Actually I was installing a few distributions in my workplace. So some distros have version pinned in their setup.py install_requires section, This is pretty evil. Why on earth are you doing this? You should only ever place version limits in install_requires, and even then, only if there are compatibility issues with a library a package depends on. eg: install_requries=['SomePackage 2.0'] and when I run the buildout expecting the versions to be printed, For the third time, why are you expecting versions to be printed here? You've pinned the version required, so buildout-versions won't report it as unpinned... But tell me this. In the above example(pinning a version number in install_requires section of setup.py) expecting the version of the package to be printed is a valid usecase right ? Wrong. Is it not ? No, it is not. cheers, Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
