Specific egg versions are ignored when newer eggs are around
Bug #105081 reported by
Christian Theune
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Buildout |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Buildout might ignore a specific egg requirement for a recipe:
- Have a newer version of an egg in your eggs directory
- Use 'recipe=
Buildout will go and fetch the older version, but it will *use* the newer version when installing a part with this recipe.
Changed in zc.buildout: | |
status: | Unconfirmed → Needs Info |
To post a comment you must log in.
I can't reproduce this.
The following test passes for me:
Buildout might ignore a specific egg requirement for a recipe:
- Have a newer version of an egg in your eggs directory =olderversion' in your buildout.cfg to request an
- Use 'recipe=
older version
Buildout will go and fetch the older version, but it will *use*
the newer version when installing a part with this recipe.
>>> write(' buildout. cfg',
... '''
... [buildout]
... parts = x
... find-links = %(sample_eggs)s
...
... [x]
... recipe = zc.recipe.egg
... eggs = demo
... ''' % globals())
>>> print system(buildout), buildout. easy_install: Getting new distribution for demo buildout. easy_install: Got demo 0.3 buildout. easy_install: Getting new distribution for demoneeded buildout. easy_install: Got demoneeded 1.1
buildout: Installing x
zc.
zc.
zc.
zc.
>>> print system(join('bin', 'demo')),
3 1
>>> write(' buildout. cfg',
... '''
... [buildout]
... parts = x
... find-links = %(sample_eggs)s
...
... [x]
... recipe = zc.recipe.egg
... eggs = demo ==0.1
... ''' % globals())
>>> print system(buildout), buildout. easy_install: Getting new distribution for demo==0.1 buildout. easy_install: Got demo 0.1
buildout: Uninstalling x
buildout: Installing x
zc.
zc.
>>> print system(join('bin', 'demo')),
1 1