Skip to content
This repository has been archived by the owner on May 14, 2020. It is now read-only.

Be virtualenvwrapper-aware? #23

Open
dtgay opened this issue Jul 28, 2013 · 3 comments
Open

Be virtualenvwrapper-aware? #23

dtgay opened this issue Jul 28, 2013 · 3 comments

Comments

@dtgay
Copy link
Owner

dtgay commented Jul 28, 2013

Pythong could help you set up or work with your virtualenv, perhaps. Could be an added level of convenience, but the user probably already has a virtualenv which they pip installed Pythong to.

@ryansb
Copy link
Contributor

ryansb commented Jul 28, 2013

So a workflow like this:

$ pythong myproject
<set up project>
<pythong automatically creates a venv with your project already "setup.py develop"'d
(myproject) $ 

@dtgay
Copy link
Owner Author

dtgay commented Jul 28, 2013

That'd be slick. Where would pythong be installed to? The system? Another virtualenv? Maybe we could package this for Fedora soon. Threebean was gonna give me a packaging tutorial.

@ryansb
Copy link
Contributor

ryansb commented Jul 28, 2013

I guess the system, but I hadn't really thought about that. Maybe have it check if you're in a venv, and if so to setup.py develop the newly created project in that venv, but I don't think it should auto-install to the system.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants