Re: Understanding virtual environment paths

On Thu, Nov 22, 2012 at 10:19 AM, Luisa Beck wrote: > But say I create a virtual environment and install a script that depends on > another script that I haven't included in the virtual environment. That > leads me to an error because the script can't be found in that virtual

Re: Understanding virtual environment paths

Hi Javier, That's super helpful. Thank you! Just to make sure I'm understanding correctly: You write "there's nothing to block you from accessing anything outside the environment. just the defaults are set up so you have to intentionally do it, not by accident." So in other words, the

Re: Understanding virtual environment paths

On Wed, Nov 21, 2012 at 7:30 PM, Luisa Beck wrote: > (I'm imagining the virtual environment like a sandbox around my project. I > can play with the things I put into the sandbox.) So when I place a file > outside of that, can I still access it when my virtual environment is >

Re: Understanding virtual environment paths

The virtual environment is like a sandbox that has its own python executable and its own python libraries. Your .db file is perfectly accessible from inside the env. On Wed, Nov 21, 2012 at 9:30 PM, Luisa Beck wrote: > I have a question about virtual environments: > > Say

Understanding virtual environment paths

I have a question about virtual environments: Say I've activated a virtual environment. I'm working with SQlite3 (already installed on my Mac 10.6.8) and I save a .db file outside of my project directory. If I save the path outside the project directory, will I still have access to it when