On Wed, Nov 21, 2012 at 7:30 PM, Luisa Beck <emmi.b...@gmail.com> 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 > active?
the 'sandboxing' of the virtual environment is not like chroot or a virtual machine: - it's only about what python code you use, not about what that code can do. the whole machine's resources are still accessible: the whole filesystem(s), RAM, network, etc. it's just a different Python installation that doesn't conflict with what you already have, or with other virtualenvs. - it's not about security, but about reducing mistakes. 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. -- Javier -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
