At 08:17 AM 9/2/2007, Kent Johnson wrote:
>Dick Moores wrote:
>>
>>>- add a .pth file to site-packages/ that contains the path to the
>>>dir you want to add to sys.path
>>I tried this with no PYTHONPATH. I put pointers.pth in
>>site-packages\ with the single line, E:\PythonWork\Functions\ .
>>Fu
Dick Moores wrote:
> Thanks, Kent.
>
> At 05:40 AM 9/2/2007, Kent Johnson wrote:
>> There are quite a few ways to get a module into the search path,
>> modifying PYTHONPATH is just one way. Some others:
>> - create a site-packages/ dir in the Python lib dir. Put your
>> modules and packages ther
Thanks, Kent.
At 05:40 AM 9/2/2007, Kent Johnson wrote:
>There are quite a few ways to get a module into the search path,
>modifying PYTHONPATH is just one way. Some others:
>- create a site-packages/ dir in the Python lib dir. Put your
>modules and packages there and they will be found by Pytho
"Kent Johnson" <[EMAIL PROTECTED]> wrote
> PYTHONPATH is for your own customizations of sys.path, it is not the
> entirety of sys.path. AFAIK you don't have to define it at all if
> you
> don't want to use it.
All true. The point of PYTHONPATH is that you could have several
users all running pyt
Dick Moores wrote:
> At 01:08 AM 9/1/2007, Alan Gauld wrote:
>
>> "Dick Moores" <[EMAIL PROTECTED]> wrote
>>
>> > > > And another question is, exactly what should go into PYTHONPATH?
>> >
>> > >Its what goes into sys.path.
PYTHONPATH is for your own customizations of sys.path, it is not the
enti
At 01:08 AM 9/1/2007, Alan Gauld wrote:
"Dick Moores"
<[EMAIL PROTECTED]> wrote
> > > And another question is, exactly what should go into
PYTHONPATH?
>
> >Its what goes into sys.path.
I've found that whether I'm using Command Prompt, IDLE, or Ulipad, that
they add a lot to sys.path.
When PYTHONP
"Dick Moores" <[EMAIL PROTECTED]> wrote
> > > And another question is, exactly what should go into PYTHONPATH?
>
> >Its what goes into sys.path.
>
> >In other words its where your local modules are stored.
> >Much more flexible. I'm a big fan of environment variables!
>
> I don't think I follow y
At 05:25 PM 8/31/2007, Kent Johnson wrote:
>Dick Moores wrote:
>>XP, Python 2.5.1
>>I installed 3.0 alpha out of curiosity in a separate folder from
>>2.5.1. Then I found that both 2.5.1's IDLE and my main Python
>>editor Ulipad would no longer open. My first idea was that the
>>installation of
At 04:20 PM 8/31/2007, you wrote:
>"Dick Moores" <[EMAIL PROTECTED]> wrote
>
> > and ulipad.pyw. How can I get back to where I was before, without
> > that annoying console opening?
>
>Sorry, no idea - thats why I never install alpha software! :-)
>
> > PYTHONPATH:
> > E:\Python25\;E:\PythonWork\;
Dick Moores wrote:
> XP, Python 2.5.1
>
> I installed 3.0 alpha out of curiosity in a separate folder from
> 2.5.1. Then I found that both 2.5.1's IDLE and my main Python editor
> Ulipad would no longer open. My first idea was that the installation
> of 3.0 somehow changed my path. But it didn'
"Dick Moores" <[EMAIL PROTECTED]> wrote
> and ulipad.pyw. How can I get back to where I was before, without
> that annoying console opening?
Sorry, no idea - thats why I never install alpha software! :-)
> PYTHONPATH:
> E:\Python25\;E:\PythonWork\;E:\Programs\Ulipad3.7\
>
> And another question
XP, Python 2.5.1
I installed 3.0 alpha out of curiosity in a separate folder from
2.5.1. Then I found that both 2.5.1's IDLE and my main Python editor
Ulipad would no longer open. My first idea was that the installation
of 3.0 somehow changed my path. But it didn't. After uninstalling
3.0, and
12 matches
Mail list logo
