You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the working set has a distribution installed as a wheel, it'll be mistaken for a "developed" distribution
(that's the older terminology for "editable"). Actually, all versions of pkg_resources I've tried (including 26) give them the DEVELOP_DIST precedence. It's not clear to me whether its intentional from the setuptools side, but correctly identifiying distributions that are from the develop buildout options (or extension) is really important in the freeze/extract processes.
I don't expect this to be a problem right now : as far as I know, zc.buildout largely ignores wheels for now, and we've consistently advised everybody to run in a totally clean virtualenv, meaning all that's installed has been installed by zc.buildout. Bottom-line: the upcoming 1.9.2 release can proceed without solving this.
Still, it's a small timebomb that should be on the todo-list.
See while trying to understand the tests problems with Babel solved by #82, cause actually I had Babel as a wheel.
The text was updated successfully, but these errors were encountered:
If the working set has a distribution installed as a wheel, it'll be mistaken for a "developed" distribution
(that's the older terminology for "editable"). Actually, all versions of
pkg_resources
I've tried (including 26) give them theDEVELOP_DIST
precedence. It's not clear to me whether its intentional from the setuptools side, but correctly identifiying distributions that are from thedevelop
buildout options (or extension) is really important in the freeze/extract processes.I don't expect this to be a problem right now : as far as I know,
zc.buildout
largely ignores wheels for now, and we've consistently advised everybody to run in a totally clean virtualenv, meaning all that's installed has been installed byzc.buildout
. Bottom-line: the upcoming 1.9.2 release can proceed without solving this.Still, it's a small timebomb that should be on the todo-list.
See while trying to understand the tests problems with Babel solved by #82, cause actually I had Babel as a wheel.
The text was updated successfully, but these errors were encountered: