Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why I read « Helper script to rebuild virtualenv.py from virtualenv_support » in comment but the code don't use virtualenv_support folder content ? #464

Closed
harobed opened this issue Aug 19, 2013 · 5 comments

Comments

@harobed
Copy link

harobed commented Aug 19, 2013

Hi,

in this comment I read « Helper script to rebuild virtualenv.py from virtualenv_support » https://github.com/pypa/virtualenv/blob/develop/bin/rebuild-script.py but this code don't embed virtualenv_support folder but virtualenv_embedded folder.

I suggest to embed also virtualenv_support folder content in virtualenv.py or/and in virtualenv bootstrap http://www.virtualenv.org/en/latest/#creating-your-own-bootstrap-scripts

What do you think about ?

Best regards,
Stephane

@pfmoore
Copy link
Member

pfmoore commented Aug 19, 2013

You're right - the comment should say virtualenv_embedded.

Historically, virtualenv_support could not be embedded in the same way, because it included the setuptools eggs, which were installed using easy_install, which has to have the eggs as files in the filesystem (and there's no point in embedding the files just to write them back to the filesystem each time we run virtualenv).

Currently the support files are just sdists, which we unpack to the filesystem and install from there. In principle we could unpack direct from the embedded form, so it's possible (but fiddley). I'm not sure how much benefit there would be, though.

And longer term, we might want to switch to using wheels rather than sdists, at which point we'd need to see whether embedding is viable and has any benefits all over again.

So basically, I'm interested in the idea, but I doubt there's enough gain to be had to make it worthwhile. If you're interested enough to create a patch, I'll review it, but even then I'm afraid I'm not willing to promise that it will be accepted. But I will think about this some more, and who knows, I may become more enthusiastic...

Thanks for the interesting suggestion.

@dstufft
Copy link
Member

dstufft commented Aug 19, 2013

One benefit to not embedding them is it makes it easier for the Linux distros to put them in a more proper place. If that's something we care about I don't know.

@pnasrat
Copy link

pnasrat commented Aug 19, 2013

From my perspective we should be considerate of downstream packaging.

Paul

On 19 August 2013 15:18, Donald Stufft notifications@github.com wrote:

One benefit to not embedding them is it makes it easier for the Linux
distros to put them in a more proper place. If that's something we care
about I don't know.


Reply to this email directly or view it on GitHubhttps://github.com//issues/464#issuecomment-22897147
.

@harobed
Copy link
Author

harobed commented Aug 19, 2013

Proposition instead embed setuptools and pip in virtualenv : #465

@dstufft dstufft mentioned this issue Jan 5, 2015
5 tasks
@stale
Copy link

stale bot commented Jan 15, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Just add a comment if you want to keep it open. Thank you for your contributions.

@stale stale bot added the wontfix label Jan 15, 2019
@stale stale bot closed this as completed Jan 22, 2019
@pypa pypa locked and limited conversation to collaborators Jan 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants