Re: Adopting virtualenv package maintenance
Paul Moore <[email protected]>
| Newsgroups | gmane.comp.python.distutils.devel |
|---|---|
| Message-ID | <CACac1F8vVMUH=OHn4RmWGESAGudCmP5O4s=6tsQbSTkdPbe-iQ@mail.gmail.com> |
On Sat, 8 Sep 2018 at 04:36, Brett Cannon <[email protected]> wrote: > - activate_this.py (which provides critical inline activation for us when >> people invoke "pipenv run" from the command line) >> > It might make sense to try and add an 'activate' command to venv, e.g. > 'python -m venv --activate .venv' as a UX convenience. > It should probably be noted that the "activate_this" script (and indeed, all of the activation scripts, etc) are not anything special. Users can relatively easily write their own, or a customised version. Sure, providing the scripts is a convenience, and they are somewhat tricky to get right, but the fact that venv doesn't provide activate_this isn't a showstopper. Paul -- Distutils-SIG mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/mm3/archives/list/[email protected]/message/OXJPWRHZJG4QAZNDDEFSLOB3KLYAAFE5/