Brian wrote:
I've been banging my head against this for the past hour, and I'm
hoping someone here can set me straight.
[Snip]
but, using the same same python, I'm able to import the module from
the interactive interpreter. The PATH and PYTHONPATH environment
variables are identical in
JM,
Thanks for the response, you're correct '' is pre-pended to the path
in interactive mode. I've tried adding . to my PYTHONPATH and it
doesn't solve the problem.
When imported from interactive python the paste.deploy module is located at:
import paste.deploy
paste.deploy.__path__
Brian Brinegar wrote:
JM,
Thanks for the response, you're correct '' is pre-pended to the path
in interactive mode. I've tried adding . to my PYTHONPATH and it
doesn't solve the problem.
When imported from interactive python the paste.deploy module is located at:
import paste.deploy
On Thu, Jan 26, 2012 at 8:49 AM, Jean-Michel Pichavant
jeanmic...@sequans.com wrote:
Brian Brinegar wrote:
JM,
Thanks for the response, you're correct '' is pre-pended to the path
in interactive mode. I've tried adding . to my PYTHONPATH and it
doesn't solve the problem.
When imported
I've been banging my head against this for the past hour, and I'm
hoping someone here can set me straight.
I have a virtualenv setup for a Pyramid app and I'm having trouble
importing the paste.deploy module in a standalone, non-Pyramid script
within the virtualenv.
For testing purposes I have a
On Wed, Jan 25, 2012 at 9:25 PM, Brian brian.brine...@gmail.com wrote:
Under what situations would a module be available to through the
interactive interpreter but not the non-interactive?
I don't know if it matches your situation, but one such case is this:
The interactive interpreter (and
