Hi All, I'm pleased to announce a new release of buildout-versions. This release: - Makes Buildout Versions check its own version has been pinned. - Makes Buildout’s version constraints agnostic of the case of distribution names. - Has a bit of a documentation tidy-up. The PyPI page is here: http://pypi.python.org/pypi/buildout-versions The documentation is here: http://packages.python.org/buildout-versions/use.html If you have any problems or suggestions, please let me know on this list or the Simplistix open source google group! cheers, Chris
Op 13-08-10 17:02, Chris Withers schreef:
Hi All,
I'm pleased to announce a new release of buildout-versions.
This release:
- Makes Buildout Versions check its own version has been pinned.
- Makes Buildout’s version constraints agnostic of the case of distribution names.
- Has a bit of a documentation tidy-up.
The PyPI page is here: http://pypi.python.org/pypi/buildout-versions
The documentation is here: http://packages.python.org/buildout-versions/use.html
If you have any problems or suggestions, please let me know on this list or the Simplistix open source google group!
I am used to buildout.dumppickedversions instead, but buildout-versions is growing on me. Perhaps it is just that the name is a few characters smaller. :) I tried 1.3 and I have just one minor gripe; with python2.4 you get a SyntaxError when first installing it in a buildout: Getting distribution for 'buildout-versions'. install_dir /Users/mauritsvanrees/shared-eggs/tmpdGrmyf File "build/bdist.macosx-10.6-i386/egg/buildout_versions/tests/test_constrain.py", line 55 with ShouldRaise(IncompatibleVersionError( ^ SyntaxError: invalid syntax File "/Users/mauritsvanrees/shared-eggs/tmpdGrmyf/buildout_versions-1.3-py2.4.egg/buildout_versions/tests/test_constrain.py", line 55 with ShouldRaise(IncompatibleVersionError( ^ SyntaxError: invalid syntax Got buildout-versions 1.3. I am used to those errors (due to scripts in Zope and Plone packages that use RestrictedPython, which has slightly different syntax) and know they are usually harmless. In this case it is harmless too: it is in a test, so it will not show up during normal use; and with python 2.5 or higher this syntax is fine. So for other users who see this: don't worry, be happy. :-) And to you: perhaps rewrite this one test for python2.4 to avoid possible confusion. Anyway, the extension seems to work fine so far. I think I may sneak it into a next project and see if anyone notices. :-) Thanks for your work, -- Maurits van Rees Programmer, Zest Software
On 08/13/2010 10:42 PM, Maurits van Rees wrote:
Anyway, the extension seems to work fine so far. I think I may sneak it into a next project and see if anyone notices. :-)
I already snug it into several projects without anyone noticing. Not seeing any message when there's nothing to report is way prettier. Only I had to revert it back for one project as I needed to make a tarball out of it with z3c.sourcerelease. Somehow that one did not pick up buildout-versions, even though buildout.dumppickedversions. So there was no buildout-versions egg in the everything-included .tgz! I might have to re-run the test now that 1.3 is out as that pins itself, too. Perhaps it also un-hides itself for z3c.sourcerelease? Reinout -- Reinout van Rees - reinout@vanrees.org - http://reinout.vanrees.org Programmer at http://www.nelen-schuurmans.nl "Military engineers build missiles. Civil engineers build targets"
On 08/18/2010 03:11 PM, Reinout van Rees wrote:
On 08/13/2010 10:42 PM, Maurits van Rees wrote:
Anyway, the extension seems to work fine so far. I think I may sneak it into a next project and see if anyone notices. :-)
I already snug it into several projects without anyone noticing.
Not seeing any message when there's nothing to report is way prettier.
Only I had to revert it back for one project as I needed to make a tarball out of it with z3c.sourcerelease. Somehow that one did not pick up buildout-versions, even though buildout.dumppickedversions. So there was no buildout-versions egg in the everything-included .tgz!
I might have to re-run the test now that 1.3 is out as that pins itself, too. Perhaps it also un-hides itself for z3c.sourcerelease?
Actually, I was already using 1.3, so I guess this is a bug. I'll look deeper into this when the project is ready. Reinout -- Reinout van Rees - reinout@vanrees.org - http://reinout.vanrees.org Programmer at http://www.nelen-schuurmans.nl "Military engineers build missiles. Civil engineers build targets"
Reinout van Rees wrote:
Only I had to revert it back for one project as I needed to make a tarball out of it with z3c.sourcerelease. Somehow that one did not pick up buildout-versions, even though buildout.dumppickedversions. So there was no buildout-versions egg in the everything-included .tgz!
I might have to re-run the test now that 1.3 is out as that pins itself, too. Perhaps it also un-hides itself for z3c.sourcerelease?
Actually, I was already using 1.3, so I guess this is a bug. I'll look deeper into this when the project is ready.
I don't know anything about z3c.sourcerelease, so any pointers you can give would be helpful! (my only guess: you don't have buildout-versions in development mode? The only thing similar to what you described was when I had buildout-versions in develop mode in my ~/.buildout/default.cfg... Chris
Maurits van Rees wrote:
worry, be happy. :-) And to you: perhaps rewrite this one test for python2.4 to avoid possible confusion.
Patches accepted ;-) (otherwise I'll get to it when I get to it)
Anyway, the extension seems to work fine so far. I think I may sneak it into a next project and see if anyone notices. :-)
Thanks! Chris
participants (3)
-
Chris Withers
-
Maurits van Rees
-
Reinout van Rees