> On 14 Dec 2019, at 16:00, Prasad Rajassekaran
> wrote:
>
> 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 i
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 new fold
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 "import sys; print(sys.path)"
> ['',...
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. Thanks a lot!
No problem, gl
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:/home/me/projects/modulename
> >
On Tuesday, March 3, 2015 at 10:37:54 PM UTC-5, liuerfire Wang wrote:
> 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.
>
>
>
On Tuesday, March 3, 2015 at 10:37:54 PM UTC-5, liuerfire Wang wrote:
> 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.
>
>
>
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 -c "import sys; print(s
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/modulename
>
> It
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)"
['',... '/home/me', '/home/me/projects/modu
On Feb 28, 9:18 pm, per wrote:
> On Feb 28, 11:53 pm, per wrote:
>
>
>
> > On Feb 28, 11:24 pm, Carl Banks wrote:
>
> > > On Feb 28, 7:30 pm, per wrote:
>
> > > > hi all,
>
> > > > i recently installed a new version of a package using python setup.py
> > > > install --prefix=/my/homedir on a sy
On Feb 28, 11:53 pm, per wrote:
> On Feb 28, 11:24 pm, Carl Banks wrote:
>
>
>
> > On Feb 28, 7:30 pm, per wrote:
>
> > > hi all,
>
> > > i recently installed a new version of a package using python setup.py
> > > install --prefix=/my/homedir on a system where i don't have root
> > > access. the
On Feb 28, 11:24 pm, Carl Banks wrote:
> On Feb 28, 7:30 pm, per wrote:
>
> > hi all,
>
> > i recently installed a new version of a package using python setup.py
> > install --prefix=/my/homedir on a system where i don't have root
> > access. the old package still resides in /usr/lib/python2.5/si
On Feb 28, 7:30 pm, per wrote:
> hi all,
>
> i recently installed a new version of a package using python setup.py
> install --prefix=/my/homedir on a system where i don't have root
> access. the old package still resides in /usr/lib/python2.5/site-
> packages/ and i cannot erase it.
>
> i set my
hi all,
i recently installed a new version of a package using python setup.py
install --prefix=/my/homedir on a system where i don't have root
access. the old package still resides in /usr/lib/python2.5/site-
packages/ and i cannot erase it.
i set my python path as follows in ~/.cshrc
setenv PYT
On Sun, 5 Mar 2006 23:05:31 -0800 (PST)
anushya beauty <[EMAIL PROTECTED]> wrote:
> Anybody, please help me to set PYTHONPATH to import
> my modules?. Where is sy.path set?
>
> In some python groups site, to import the user modules,
> they explained to create one __init__.py fi
Hi, Anybody, please help me to set PYTHONPATH to import my modules?. Where is sy.path set?In some python groups site, to import the user modules, they explained to create one __init__.py file in my module directory (this file should include __all__ variable, which refer to the modules
On Fri, Dec 02, 2005 at 08:10:41PM -0500, Mike Meyer wrote:
> Inyeol Lee <[EMAIL PROTECTED]> writes:
> > On Fri, Dec 02, 2005 at 07:33:20PM -0500, Mike Meyer wrote:
> >> > The problem is that myscript.py and some modules that myscript.py
> >> > imports are not in the current directory, but in anoth
Inyeol Lee <[EMAIL PROTECTED]> writes:
> On Fri, Dec 02, 2005 at 07:33:20PM -0500, Mike Meyer wrote:
>> > The problem is that myscript.py and some modules that myscript.py
>> > imports are not in the current directory, but in another place in the
>> > filesystem, say, /path/to/stuff. If this was a
On Fri, Dec 02, 2005 at 07:33:20PM -0500, Mike Meyer wrote:
> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> > I have a Makefile target that uses a python script, like:
> >
> > %.abc: %.def
> > python myscript.py
> >
> > The problem is that myscript.py and some modules that myscript.py
>
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> I have a Makefile target that uses a python script, like:
>
> %.abc: %.def
> python myscript.py
>
> The problem is that myscript.py and some modules that myscript.py
> imports are not in the current directory, but in another place in the
> f
[EMAIL PROTECTED]
> I have a Makefile target that uses a python script, like:
> %.abc: %.def
> python myscript.py
> If this was a tcsh script, I would just do:
>setenv PYTHONPATH /path/to/stuff
>python myscript.py
> but this cannot be done from a Makefile.
Use:
%.abc:
I have a Makefile target that uses a python script, like:
%.abc: %.def
python myscript.py
The problem is that myscript.py and some modules that myscript.py
imports are not in the current directory, but in another place in the
filesystem, say, /path/to/stuff. If this was a tcsh script, I w
24 matches
Mail list logo
