Packages that install Python modules shouldn't be installing Eggs, as distro-managed modules should be "bare". It shouldn't be hard to detect this happening in a sanity test, and warning the user.
Since we moved to wheels, is this still needed?
Might be worth having the test still, to catch people installing with legacy stuff.
Dear all, I'm a newcomer, I have submitted a patch following instruction at: http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded Please help to review.
Created attachment 4944 [details] proposed patch
I can't see the patch on the list, did you submit it to openembedded-core@lists.openembedded.org? I'm not sure that patch will work, as it depends on the recipe explicitly RDEPENDing on python3-eggs. A recipe which is installing an egg inadvertently won't do that.
Hi Mr. Ross Burton > I'm not sure that patch will work,(In reply to Ross Burton from comment #5) > I can't see the patch on the list, did you submit it to > openembedded-core@lists.openembedded.org? I've submitted to openembedded-core@lists.openembedded.org. You can search for the mail subject: setuptools3: adding sanity check to detect python-eggs install > I'm not sure that patch will work, as it depends on the recipe explicitly > RDEPENDing on python3-eggs. A recipe which is installing an egg > inadvertently won't do that. I'm sorry, but can you give me an example. My understanding is: - Each python module will be managed by a separate recipe. - To install python-eggs, user will specify IMAGE_INSTALL += ' python-eggs', - or it will be installed when RDEPENDing of a recipe have 'python-eggs'
> I'm sorry, but can you give me an example. My understanding is: > - Each python module will be managed by a separate recipe. > - To install python-eggs, user will specify IMAGE_INSTALL += ' python-eggs', > - or it will be installed when RDEPENDing of a recipe have 'python-eggs' That's not right. A 'python egg' is .zip file which contains a module (where as a bare module is just a directory of files). There is no file called 'python-eggs'. However since this bug was created the Python world has moved on a lot and I'm not convinced it's worth checking for eggs anymore. They were used by easy_install which has been entirely replaced by pip. Sorry, but I think I'll close this: the check will be obsolete.