On 5/15/2023 3:26 AM, Barry wrote:
On 15 May 2023, at 05:39, Thomas Passin wrote:
On 5/14/2023 11:08 PM, Chris Angelico wrote:
On Mon, 15 May 2023 at 12:07, Thomas Passin wrote:
Well, no, why would you assume that? I started to use Linux - in VMs -
because I had to make sure that my cros
On Mon, 15 May 2023 at 14:38, Thomas Passin wrote:
>
> On 5/14/2023 11:08 PM, Chris Angelico wrote:
> > On Mon, 15 May 2023 at 12:07, Thomas Passin wrote:
> >> Well, no, why would you assume that? I started to use Linux - in VMs -
> >> because I had to make sure that my cross-platform java/jytho
> On 15 May 2023, at 05:39, Thomas Passin wrote:
>
> On 5/14/2023 11:08 PM, Chris Angelico wrote:
>>> On Mon, 15 May 2023 at 12:07, Thomas Passin wrote:
>>> Well, no, why would you assume that? I started to use Linux - in VMs -
>>> because I had to make sure that my cross-platform java/jytho
On 5/14/2023 11:08 PM, Chris Angelico wrote:
On Mon, 15 May 2023 at 12:07, Thomas Passin wrote:
Well, no, why would you assume that? I started to use Linux - in VMs -
because I had to make sure that my cross-platform java/jython Tomcat
program would work right on Linux. Why, for example, woul
On Mon, 15 May 2023 at 12:07, Thomas Passin wrote:
> Well, no, why would you assume that? I started to use Linux - in VMs -
> because I had to make sure that my cross-platform java/jython Tomcat
> program would work right on Linux. Why, for example, would I think to
> install Idle from the packa
On 5/14/2023 7:28 PM, Chris Angelico wrote:
On Mon, 15 May 2023 at 09:22, Thomas Passin wrote:
You made a little slam against Windows, but you will find it harder to
get things working on Linux. Ubuntu, like many other Linux distros,
does not come with pip and Tk (needed for Idle) installed, a
On Mon, 15 May 2023 at 09:22, Thomas Passin wrote:
> You made a little slam against Windows, but you will find it harder to
> get things working on Linux. Ubuntu, like many other Linux distros,
> does not come with pip and Tk (needed for Idle) installed, and it's not
> so obvious how to install t
On 5/14/2023 3:00 PM, Grizzy Adams via Python-list wrote:
Sunday, May 14, 2023 at 11:11, Mats Wichmann wrote:
Re: PythonPath / sys.path (at least in part)
[snip]
I have since moved up (a little) so only ~4 years old, I then updated pip from
9.x to 19.1
reason its an old version is it'
On 5/13/23, Grizzy Adams via Python-list wrote:
>
> I have tried adding my dir in registry to the existing PythonPath
>
> [HKEY_CURRENT_USER\Software\Python\PythonCore\3.4\PythonPath]
> @="D:\\Shades\\Tools\\Python\\Lib;D:\\Shades\\Tools\\Python\\DLLs"
>
> that did
On 5/14/23 13:00, Grizzy Adams via Python-list wrote:
Sunday, May 14, 2023 at 11:11, Mats Wichmann wrote:
Re: PythonPath / sys.path (at least in part)
On 5/14/23 10:43, Barry wrote:
I take it you have business reasons to use an obsolete version python.
Where did you get your version of
Sunday, May 14, 2023 at 11:11, Mats Wichmann wrote:
Re: PythonPath / sys.path (at least in part)
>On 5/14/23 10:43, Barry wrote:
>> I take it you have business reasons to use an obsolete version python.
>> Where did you get your version of python from?
>In fact, a *nine* y
On 5/14/23 10:43, Barry wrote:
I take it you have business reasons to use an obsolete version python.
Where did you get your version of python from?
In fact, a *nine* year old version of Python that reached end-of-life
four years ago.
Just sayin'
Python version shouldn't have anything to d
> On 14 May 2023, at 16:32, Grizzy Adams via Python-list
> wrote:
>
> Hi All
>
> My first post (repeated)
>
> I am having a problem with PythonPath / sys.path
>
> I have a dir where I keep all my current work, but I can't seem to add it to
> Py
Hi All
My first post (repeated)
I am having a problem with PythonPath / sys.path
I have a dir where I keep all my current work, but I can't seem to add it to
PythonPath / sys.path
When I try to import one of my modules I see
>>>import My_Working_File
Traceback (most recent call
>different versions of the same package in different projects
>
>but recently I start using pip install --target for
>zipapp<https://docs.python.org/3.10/library/zipapp.html#creating-standalone-applications-with-zipapp>
> things, and then I use this pip's option (--targe
jects
but recently I start using pip install --target for
zipapp<https://docs.python.org/3.10/library/zipapp.html#creating-standalone-applications-with-zipapp>
things, and then I use this pip's option (--target) and add its target folder
to PYTHONPATH and target folder's bin direc
On 09/03/2021 22:52, Cameron Simpson wrote:
On 09Mar2021 05:00, Larry Martell wrote:
Which is considered better? Having a long import path or setting PYTHONPATH?
For example, in a project where 50% of the imports come from the same top
level directory is it better to add that dir to the path
On 09Mar2021 05:00, Larry Martell wrote:
>Which is considered better? Having a long import path or setting PYTHONPATH?
>
>For example, in a project where 50% of the imports come from the same top
>level directory is it better to add that dir to the path or reference it in
>the im
Which is considered better? Having a long import path or setting PYTHONPATH?
For example, in a project where 50% of the imports come from the same top
level directory is it better to add that dir to the path or reference it in
the import statements?
--
https://mail.python.org/mailman/listinfo
All: I propose that all empty entries with $PYTHONPATH be ignored.
This would eliminate some accidents that can lead to security problems.
I thought it'd be easiest to explain by drafting a PEP, so please see
this first draft below.
Thanks! Comments welcome.
--- David A. Wh
used to add all the folders & sub-folders in environment variables under
> PYTHONPATH but this has two constrains.
>
> 1, Any new folders created need to be added in environment variables all the
> times. After certain limit, environment variables will not be accepted new
> p
Prasad Rajassekaran writes:
> I would want to set python path programmatic in my project. So that, all
> other directories files can be imported without any issues.
You can extend "sys.path" programmatically to control
where Python looks for top level packages/modules (as
you apparently have alr
0
Aim:-
I would want to set python path programmatic in my project. So that, all other
directories files can be imported without any issues.
Problem statement:-
I used to add all the folders & sub-folders in environment variables under
PYTHONPATH but this has two constrains.
1, Any
Le mardi 27 mars 2018 07:42:57 UTC+2, dieter a écrit :
> oyono writes:
> > ...
> > I was thinking, maybe it could have been done this way to enforce not
> > running module files that are supposed to be bundled into packages as
> > "independant" python scripts...Therefore, running "python script.
oyono writes:
> ...
> I was thinking, maybe it could have been done this way to enforce not running
> module files that are supposed to be bundled into packages as "independant"
> python scripts...Therefore, running "python script.py" should be reserved to
> effectively independant python scrip
Le lundi 26 mars 2018 08:11:02 UTC+2, dieter a écrit :
> adrien oyono writes:
> > I have recently read the documentation about how imports work on python,
> > and I was wondering why, when you execute a python file, the current
> > directory is not added by default to the PY
he current
>>> directory is not added by default to the PYTHONPATH ?
>>
>> Maybe, to avoid surprises?
>>
>> You can invoke a script from different positions in your file system.
>> If PYTHONPATH would automatically get ".", the script's behaviour
On Sun, Mar 25, 2018 at 11:10 PM, dieter wrote:
> adrien oyono writes:
>> I have recently read the documentation about how imports work on python,
>> and I was wondering why, when you execute a python file, the current
>> directory is not added by default to the PYTHONPATH
adrien oyono writes:
> I have recently read the documentation about how imports work on python,
> and I was wondering why, when you execute a python file, the current
> directory is not added by default to the PYTHONPATH ?
Maybe, to avoid surprises?
You can invoke a script from
Hello everyone,
This is my first email to the python list, I'll try my best to do it well.
TL;DR
I have recently read the documentation about how imports work on python,
and I was wondering why, when you execute a python file, the current
directory is not added by default to the PYTHO
hello,
I am a bit confused, i use spyder, when i execute in ipython console
program start fails with message 'Attribute error'
when I start same program via python console everything works fine, even
start from terminal workes fine.
It seems that i python does not load Pythonpath
Op Saturday 23 May 2015 20:13 CEST schreef Mark Lawrence:
> On 23/05/2015 18:30, Cecil Westerhof wrote:
>>
>> I should have checked better. I think I found a bug that made it
>> look like PYTHONPATH does not work.
>>
>> In bash I give:
>> echo $PYTHONPATH
Op Saturday 23 May 2015 19:30 CEST schreef Cecil Westerhof:
> I should have checked better. I think I found a bug that made it
> look like PYTHONPATH does not work.
>
> In bash I give:
> echo $PYTHONPATH
> this gives:
> .:/home/cecil/Python/PythonLibrary
>
> Then I st
On 23/05/2015 18:30, Cecil Westerhof wrote:
I should have checked better. I think I found a bug that made it look
like PYTHONPATH does not work.
In bash I give:
echo $PYTHONPATH
this gives:
.:/home/cecil/Python/PythonLibrary
Then I start ipython3 and get/do the following
gt;>>
>>>>> On 22/05/2015 06:20, Cecil Westerhof wrote:
>>>>>> I am looking into using ipython instead of bash. But when I
>>>>>> call a python program from ipython PYTHONPATH is not set. So
>>>>>> pythonscripts that need a m
gt; I am looking into using ipython instead of bash. But when I call
>>>>> a python program from ipython PYTHONPATH is not set. So
>>>>> pythonscripts that need a module through PYTHONPATH will not
>>>>> work.
>>>>>
>>>>> I c
Op Saturday 23 May 2015 17:00 CEST schreef Laura Creighton:
> In a message of Sat, 23 May 2015 16:08:00 +0200, Cecil Westerhof
> writes:
>> That is not the problem:
>> os.environ['PYTHONPATH']
>> gives:
>> .:/home/cecil/Python'
>>
>> As I
In a message of Sat, 23 May 2015 16:08:00 +0200, Cecil Westerhof writes:
>That is not the problem:
>os.environ['PYTHONPATH']
>gives:
>.:/home/cecil/Python'
>
>As I interpret it is that the very handy shell variable is not used in ipython.
>
>--
>
when I call
>>>> a python program from ipython PYTHONPATH is not set. So
>>>> pythonscripts that need a module through PYTHONPATH will not
>>>> work.
>>>>
>>>> I could do something like:
>>>> !PYTHONPATH=~/Python/PythonLibrary pyth
Cecil Westerhof wrote:
> Op Saturday 23 May 2015 11:12 CEST schreef Mark Lawrence:
>
>> On 22/05/2015 06:20, Cecil Westerhof wrote:
>>> I am looking into using ipython instead of bash. But when I call a
>>> python program from ipython PYTHONPATH is not set. So
Op Saturday 23 May 2015 11:12 CEST schreef Mark Lawrence:
> On 22/05/2015 06:20, Cecil Westerhof wrote:
>> I am looking into using ipython instead of bash. But when I call a
>> python program from ipython PYTHONPATH is not set. So pythonscripts
>> that need a module throug
On 22/05/2015 06:20, Cecil Westerhof wrote:
I am looking into using ipython instead of bash. But when I call a
python program from ipython PYTHONPATH is not set. So pythonscripts
that need a module through PYTHONPATH will not work.
I could do something like:
!PYTHONPATH=~/Python
I am looking into using ipython instead of bash. But when I call a
python program from ipython PYTHONPATH is not set. So pythonscripts
that need a module through PYTHONPATH will not work.
I could do something like:
!PYTHONPATH=~/Python/PythonLibrary python2 …
But I find that a little bit
fa...@vt.edu wrote:
> I have the following directory /home/me/projects/modulename.
>
> I update PYTHONPATH using the following command:
> export PYTHONPATH=$PYTHONPATH:/home/me/projects/modulename
>
> It seems to have been added:
> [me@machine ~]$ python -c "
On Tue, Mar 3, 2015 at 9:47 PM, wrote:
> On Tuesday, March 3, 2015 at 10:43:27 PM UTC-5, Zachary Ware wrote:
>> Try adding /home/me/projects to PYTHONPATH instead of
>> /home/me/projects/modulename.
>
> Ah, that worked! Yes, I see that the modulename must be visible. Than
On Tuesday, March 3, 2015 at 10:43:27 PM UTC-5, Zachary Ware wrote:
> On Tue, Mar 3, 2015 at 9:25 PM, wrote:
> > I have the following directory /home/me/projects/modulename.
> >
> > I update PYTHONPATH using the following command:
> > export PYTHONPATH=$PYTHONPATH:/
he following directory /home/me/projects/modulename.
>
>
>
> I update PYTHONPATH using the following command:
>
> export PYTHONPATH=$PYTHONPATH:/home/me/projects/modulename
>
>
>
> It seems to have been added:
>
> [me@machine ~]$ python -c "import sys; print(sy
he following directory /home/me/projects/modulename.
>
>
>
> I update PYTHONPATH using the following command:
>
> export PYTHONPATH=$PYTHONPATH:/home/me/projects/modulename
>
>
>
> It seems to have been added:
>
> [me@machine ~]$ python -c "import sys; print(sy
On Tue, Mar 3, 2015 at 9:25 PM, wrote:
> I have the following directory /home/me/projects/modulename.
>
> I update PYTHONPATH using the following command:
> export PYTHONPATH=$PYTHONPATH:/home/me/projects/modulename
>
> It seems to have been added:
> [me@machine ~]$ python
Is there a file named __init__.py in the modulename dir?
Best regards
On Wed, Mar 4, 2015 at 11:25 AM, wrote:
> I have the following directory /home/me/projects/modulename.
>
> I update PYTHONPATH using the following command:
> export PYTHONPATH=$PYTHONPATH:/home/me/projects/modul
I have the following directory /home/me/projects/modulename.
I update PYTHONPATH using the following command:
export PYTHONPATH=$PYTHONPATH:/home/me/projects/modulename
It seems to have been added:
[me@machine ~]$ python -c "import sys; print(sys.path)"
['',... '/hom
On Mon, Feb 23, 2015 at 3:14 PM, Ethan Furman wrote:
> On 02/23/2015 01:00 PM, Tobiah wrote:
>
>> Anyway, it raises the question as to whether having '.' in the
>> PYTHONPATH is at all a sane thing to do.
>
> The current directory is added to sys.path /only/
Relative imports only work with the "from ... import ..." form.
— SpaghettiToastBook
On Mon, Jul 1, 2013 at 3:54 PM, Tobiah wrote:
>> Are you familiar with absolute and relative imports:
>> http://docs.python.org/release/2.5/whatsnew/pep-328.html
>
>
> Doesn't seem to work:
>
> Python 2.7.3 (de
Steven D'Aprano writes:
> On Mon, 01 Jul 2013 14:38:50 -0700, rusi wrote:
>> 2. The __future__ is not necessary in python 2.7 [Not necessary or not
>> allowed I not know :-) ]
>
> Not necessary.
IIRC that it is needed, to solve the OP problem: one thing is the
syntax, which under Python 2.7 is e
On 1 Jul 2013 20:58, "Tobiah" wrote:
>>
>> Are you familiar with absolute and relative imports:
>> http://docs.python.org/release/2.5/whatsnew/pep-328.html
>
>
> Doesn't seem to work:
>
> Python 2.7.3 (default, May 10 2012, 13:31:18)
> [GCC 4.2.4 (Ubuntu 4.2.4-1ubuntu4)] on linux2
> Type "help", "
On Mon, 01 Jul 2013 14:38:50 -0700, rusi wrote:
> On Tuesday, July 2, 2013 1:24:30 AM UTC+5:30, Tobiah wrote:
>> > Are you familiar with absolute and relative imports:
>> > http://docs.python.org/release/2.5/whatsnew/pep-328.html
>>
>> Doesn't seem to work:
>> Python 2.7.3 (default, May 10 2012,
On Tuesday, July 2, 2013 1:24:30 AM UTC+5:30, Tobiah wrote:
> > Are you familiar with absolute and relative imports:
> > http://docs.python.org/release/2.5/whatsnew/pep-328.html
>
> Doesn't seem to work:
> Python 2.7.3 (default, May 10 2012, 13:31:18)
> [GCC 4.2.4 (Ubuntu 4.2.4-1ubuntu4)] on linux
Are you familiar with absolute and relative imports:
http://docs.python.org/release/2.5/whatsnew/pep-328.html
Doesn't seem to work:
Python 2.7.3 (default, May 10 2012, 13:31:18)
[GCC 4.2.4 (Ubuntu 4.2.4-1ubuntu4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
On Monday, July 1, 2013 11:59:35 PM UTC+5:30, Tobiah wrote:
> So today, I created a file called 'formatter.py',
> and my program broke. It turned out that I was
> also import 'gluon' from web2py, which in turn,
> somewhere, imported the regular python formatter.py
> with which I was not familiar.
So today, I created a file called 'formatter.py',
and my program broke. It turned out that I was
also import 'gluon' from web2py, which in turn,
somewhere, imported the regular python formatter.py
with which I was not familiar.
So the question is: Does one simply always have
to be knowledgeable
On Wednesday, June 12, 2013 5:10:05 PM UTC+1, rusi wrote:
> On Jun 12, 6:29 pm, jacopo wrote:
>
> > > 1. How you run -- 'launch' -- the code -- from py and from prod
>
> >
>
> > when I have to test I use "python any_script.py" but in production there
> > is a c++ program that is able to wrap
On Jun 12, 6:29 pm, jacopo wrote:
> > 1. How you run -- 'launch' -- the code -- from py and from prod
>
> when I have to test I use "python any_script.py" but in production there is
> a c++ program that is able to wrap and run python code (the technical details
> are a bit beyond my knowledge)
> 1. How you run -- 'launch' -- the code -- from py and from prod
when I have to test I use "python any_script.py" but in production there is a
c++ program that is able to wrap and run python code (the technical details are
a bit beyond my knowledge)
> 2. What error you get
when I run as "pyt
trol on how the
> module is launched.
You need to give more data:
1. How you run -- 'launch' -- the code -- from py and from prod
2. What error you get
3. Did you try bundling your modules into a package? What problem
happened?
If PYTHONPATH does not work for you you can look at pat
, 2013 6:14:43 PM UTC+1, rusi wrote:
> On Jun 11, 9:28 pm, jacopo wrote:
>
> > I am developing my code in the path:
>
> > /py/myscripts
>
> > /py/mylib
>
> > In order to "import mylib", I need to add /py/mylib to PYTHONPATH.
>
> >
>
:14:43 PM UTC+1, rusi wrote:
> On Jun 11, 9:28 pm, jacopo wrote:
>
> > I am developing my code in the path:
>
> > /py/myscripts
>
> > /py/mylib
>
> > In order to "import mylib", I need to add /py/mylib to PYTHONPATH.
>
> >
>
On Jun 11, 9:28 pm, jacopo wrote:
> I am developing my code in the path:
> /py/myscripts
> /py/mylib
> In order to "import mylib", I need to add /py/mylib to PYTHONPATH.
>
> Now I want to save a snapshot of the current code in the production
> directory, I will
I am developing my code in the path:
/py/myscripts
/py/mylib
In order to "import mylib", I need to add /py/mylib to PYTHONPATH.
Now I want to save a snapshot of the current code in the production directory,
I will copy all in:
/prod/myscripts
/prod/mylib
The problem now is that when
ibrary in directory L. Then I have in an
>> unrelated directory, the test software, which I need to use the library
>> version
>> from directory L.
>>
>> One approach is to set PYTHONPATH whenever I run this test software. Any
>> suggestion on a more foolproo
> version
> from directory L.
>
> One approach is to set PYTHONPATH whenever I run this test software. Any
> suggestion on a more foolproof approach?
>
Simply modify sys.path at the beginning of your test software. That's
where import searches.
--
DaveA
--
http://mail.python.org/mailman/listinfo/python-list
I'm testing some software I'm building against an alternative version of a
library. So I have an alternative library in directory L. Then I have in an
unrelated directory, the test software, which I need to use the library version
from directory L.
One approach is to set PYTHONPAT
En Sun, 29 May 2011 18:49:28 -0300, ray escribió:
I am using Win7 on a tightly locked down desktop.
Is there an alternative to using PythonPath?
What are the trade-offs?
Usually there is no need to define the PYTHONPATH variable; I never use it.
There is a per-user site-packages directory
On May 30, 2:49 am, ray wrote:
> I am using Win7 on a tightly locked down desktop.
>
> Is there an alternative to using PythonPath?
>
> What are the trade-offs?
>
> Thanks,
> ray
Externally:
1. PYTHONPATH
2. .pth files
http://bob.pythonmac.org/archives/2005/02/06/us
On 29-5-2011 23:49, ray wrote:
> I am using Win7 on a tightly locked down desktop.
>
> Is there an alternative to using PythonPath?
>
What do you mean by "using PythonPath"?
What doesn't work that you want to have an alternative for?
Irmen
--
http://mail.python.
I am using Win7 on a tightly locked down desktop.
Is there an alternative to using PythonPath?
What are the trade-offs?
Thanks,
ray
--
http://mail.python.org/mailman/listinfo/python-list
On 19/04/2011 2:15 AM, python-list-requ...@python.org wrote:
Subject:
Re: PYTHONPATH
From:
MRAB
Date:
Mon, 18 Apr 2011 16:31:31 +0100
To:
python-list@python.org
On 18/04/2011 05:37, harrismh777 wrote:
[snip]
In retrospect, in many ways this is why I am relatively patient with the
Python3
On 18/04/2011 05:37, harrismh777 wrote:
[snip]
In retrospect, in many ways this is why I am relatively patient with the
Python3 development direction. While I think its non-compatibility may
hurt in the short term, the long term goal of stream-lining the language
will make for a much better Pytho
Steven D'Aprano wrote:
In my opinion, a better explanation for the
difficulty faced by Windows users is that this is a side-effect of
Windows starting life as a single-user operating system.
Yes, that is my opinion as well.
Windows for better or worse is plagued by "cruft" that dates back to t
On Sun, 17 Apr 2011 01:14:54 -0500, harrismh777 wrote:
> Its just technically difficult to
> setup easily configured concurrent environments on the Windows platform,
> primarily due to the way the platform was designed--- closed and
> proprietary--- with little to no community input.
I believe th
jmfauth wrote:
I belong to those who are very happy with the Python
installations on Windows platform . . .
I do not see any mess here.
Sorry, I was speaking of a technical mess, not a user's mess.
What I was alluding to specifically is explained very well in PEP 394.
The technical reasoning
other Python versions or
> porting that application (*) to another Python version. And
> that on all Windows versions (Win2K, XP, Vista, Win7) modulo
> the underlaying os-libs compatibility, but that's the same
> problem on all os, especially for the GUI libs.
>
> I'm usi
-libs compatibility, but that's the same
problem on all os, especially for the GUI libs.
I'm using Python since ver 1.5.6 and I never set any
PYTHONPATH environment variable.
A final word about sys.path. This is is my mind the
most clever idea of Python. I have the feeling, no
offense
On Saturday 16 April 2011 14:16:59 harrismh777 wrote:
> Algis Kabaila wrote:
> > Is PYTHONPATH a system variable that sets the
> > path for several sessions and if so, where in the system is
> > it? Do I need to create one for setting python path for
> > several session
Algis Kabaila wrote:
Is PYTHONPATH a system variable that sets the
path for several sessions and if so, where in the system is it?
Do I need to create one for setting python path for several
sessions?
It can be, and there are lots of ways to accomplish what you want, some
of which depends on
o add directories to
> the module search path:
> http://docs.python.org/library/site.html
>
> Cheers,
> Chris
From Gabriel Genellina:
>
> escribió:
> > An elementary question that is bugging me, regarding
>
> PYTHONPATH is an environment variable, you set i
En Fri, 15 Apr 2011 05:33:18 -0300, Algis Kabaila
escribió:
An elementary question that is bugging me, regarding sys.path
values.sys.path can be altered easily, but the changes last for
the current session only. I would like the changes to stay for
several sessions. Is PYTHONPATH a system
On Fri, Apr 15, 2011 at 1:33 AM, Algis Kabaila wrote:
> Hi,
>
> An elementary question that is bugging me, regarding sys.path
> values.sys.path can be altered easily, but the changes last for
> the current session only. I would like the changes to stay for
> several sessions
Hi,
An elementary question that is bugging me, regarding sys.path
values.sys.path can be altered easily, but the changes last for
the current session only. I would like the changes to stay for
several sessions. Is PYTHONPATH a system variable that sets the
path for several sessions and if so
On Sat, 2011-02-19 at 19:22 +0100, Andrea Crotti wrote:
> Il giorno 19/feb/2011, alle ore 18.25, Doug Epling ha scritto:
>
> > The best way I have found is to place that definition of your PYTHONPATH in
> > your .bash_profile in your home directory and ex
Il giorno 19/feb/2011, alle ore 18.25, Doug Epling ha scritto:
> The best way I have found is to place that definition of your PYTHONPATH in
> your .bash_profile in your home directory and export it from there.
>
> PYTHONPATH=/home/foo/prog/learning_python
>
>
The best way I have found is to place that definition of your PYTHONPATH
in your .bash_profile in your home directory and export it from there.
PYTHONPATH=/home/foo/prog/learning_python
export PYTHONPATH
This way your PYTHONPATH is picked up each time you log on. You
might
On 15.02.2011 19:12, Panupat Chongstitwattana wrote:
Panupat, please don't top-post, it messes the the natural order of
the discussion. Thanks.
I think the command line should look something along this line
export PYTHONPATH=$HOME/foo/prog/learning_python/:
with a colon at the end.
I think the command line should look something along this line
export PYTHONPATH=$HOME/foo/prog/learning_python/:
with a colon at the end.
On Wed, Feb 16, 2011 at 12:49 AM, Tim Hanson wrote:
> I am to the point in _Learning_Python_ where functions are introduced.
>
> I decided to e
I am to the point in _Learning_Python_ where functions are introduced.
I decided to experiment by putting a function into a file and importing it
into Idle. Of course, Idle couldn't find it, so I executed the following
command in Bash:
PYTHONPATH=/home/foo/prog/learning_python
e
by why Python 3.1 acts up when I set the environment variable
> PYTHONPATH. It certainly caused no problem with the 2.X series.
Most likely, H:\Python contains a module with a name that conflicts with
the standard library. Starting IDLE tries to import that module - but
not from the standard librar
iable
PYTHONPATH. It certainly caused no problem with the 2.X series.
--
http://mail.python.org/mailman/listinfo/python-list
I run Python under Windows XP SP3, and for the longest time, I have
installed it on my C: drive under C:\PythonXX (XX = 20, 21., 26),
and maintained all my Python files on our network in a directory
called H:\Python that I point to by creating an environment variable
called PYTHONPATH. I
On Tue, Mar 16, 2010 at 4:56 AM, Barak, Ron wrote:
> Barak, Ron would like to recall the message, "How to add a library path to
> pythonpath ?".
Good luck with that. :)
- Chris
--
http://mail.python.org/mailman/listinfo/python-list
Barak, Ron would like to recall the message, "How to add a library path to
pythonpath ?".
--
http://mail.python.org/mailman/listinfo/python-list
> -Original Message-
> From: Mark Hammond [mailto:skippy.hamm...@gmail.com]
> Sent: Wednesday, March 17, 2010 2:08 AM
> To: Barak, Ron
> Cc: Pablo Recio Quijano; python-list@python.org
> Subject: Re: How to add a library path to pythonpath ?
>
> On 17/03/2010 1
1 - 100 of 277 matches
Mail list logo
