Log file Viewer

[00:51:26] <Alex_Gaynor> jezdez: getting a 500 on https://caniusepython3.com/check/56ec0e1c-5f1f-4863-b166-f8b593360421

[12:40:56] <jezdez> Alex_Gaynor: yeah, there were some bugz

[12:40:56] <jezdez> should work now

[12:45:57] <Alex_Gaynor> jezdez: no worries, thanks!

[17:22:25] <jay> How do I create a virtualenv in an existing project?

[17:32:42] <DanielHolth> virtualenv /tmp/some-environment ; /tmp/some-environment/bin/pip install -e .

[17:34:12] <DanielHolth> when you are in your project's directory with its setup.py

[17:40:00] <jay> so now I have something like this, virtualenv /vagrant/some-directory ; --no-site-packages env

[17:40:04] <jay> anything wrong with that?

[17:45:34] <jay> or should it be like virtualenv --no-site-packages ; /vagrant/some-directory env

[17:46:36] <DanielHolth> no that's not quite right

[17:46:52] <DanielHolth> usually virtualenv with no arguments is what you want. what is "/vagrant/some-directory env" supposed to do?

[17:47:14] <DanielHolth> You can execute ". /vagrant/some-directory/bin/activate" if you want the virtualenv python to be on your path

[17:47:53] <jay> ok so --no-site-packages is depreciated, so it would just be virtualenv /vagrant/some-directory

[17:48:14] <jay> and that will install into an existing directory?

[17:49:20] <DanielHolth> yes, it's common to virtualenv on top of an old virtualenv that needs updatin'

[17:50:16] <jay> great, it worked

[17:50:18] <jay> thank you

[17:52:18] <DanielHolth> sure

[21:13:37] <dropdrive> Hi, should I expect setuptools "development mode" to work for namespace packages? Given my understanding of .pth and .egg-link, it seems like this is simply not supported. Is this correct?