On Thu, 25 Apr 2019, dieter wrote:
The means that "test_act_de.py" has not extended "sys.path"
appropriately.
Dieter,
That's what I thought.
When Python starts a script ("gui/test_act_de.py" in your case), it
automatically extends "sys.path" with the folder containing the script
("gui" in y
Rich Shepard writes:
>> bustrac/
>>README.rst
>>bustrac.py*
>>controller/
>>classes/
> model.py
>>scripts/
>>gui/
> test_act_de.py
>
> test_act_de.py tries to import model.py from the classes package:
> from classes import model as m
>
> Running in bustrac
On Wed, 24 Apr 2019, Rich Shepard wrote:
The current project's directory structure is:
I changed package names so there are no duplicate names for packages and
modules.
bustrac/
README.rst
bustrac.py*
controller/
classes/
model.py
scripts/
gui/
test_act
On Wed, 24 Apr 2019, Rich Shepard wrote:
If I correctly understand the process, in bustrac.py I'll add import
sys.path sys.path.append(controller, model, scripts, views)
Never mind. I've installed virtualenv and will work within it.
Regards,
Rich
--
https://mail.python.org/mailman/listinfo/p
On Wed, 24 Apr 2019, dieter wrote:
With a "virtualenv", there is usually no need to tweak "sys.path" --
you simply install everything your project needs into the "virtualenv".
Dieter,
Okay. I just upgraded pip to 19.1 for python3 and virtualenv to version
16.5.0. Now I'll learn how to use it
On Wed, 24 Apr 2019, dieter wrote:
"sys.path" tweaks are typically employed with a "central" Python
installation, to have it look at non-standard places for module/packages
under specific circumstances.
Almost all python packages installed here are built using the
SlackBuilds.org scripts (I ru
Rich Shepard writes:
> On Tue, 23 Apr 2019, dieter wrote:
> ...
> One project is for my own use and I understand now that a virtualenv with
> its own sys.path appendices would work.
Those are two separate approaches:
With a "virtualenv", there is usually no need to tweak "sys.path" --
you simply
On Tue, 23 Apr 2019, dieter wrote:
I use "virtualenv" (for "VIRTUAL ENVironmet") to separate
projects.
Dieter,
I know about virtualenv and tried using them. Found conflicting information
and didn't know if I really needed them. I'll re-learn how to activate and
use them.
One project is for m
Rich Shepard writes:
> On Thu, 18 Apr 2019, dieter wrote:
> ...
>> 2. extend "sys.path" in your scripts to contain the "bustrac" folder
>> (before you try to import infrastructure modules/packages)
>
> I read the docs for sys and site and have insufficient experience with them
> to know how best t
On Thu, 18 Apr 2019, dieter wrote:
I see two options for you:
1. put your scripts directly into "bustrac" (rather than a subdirectory)
There are too many files; the directory is very cluttered.
2. extend "sys.path" in your scripts to contain the "bustrac" folder
(before you try to import in
On Thu, 18 Apr 2019, dieter wrote:
Python knows about 2 kinds of "regular" imports: absolute ones and
relative ones. "Absolute" imports are guided by "sys.path" -- in the
simple case, a sequence of folders containing modules and/or pacakges.
Relative imports are guided in a similar way by the cu
On Wed, 17 Apr 2019, Sayth Renshaw wrote:
Apologies I don't know the answer but went looking. This guide should
answer the question. Didn't know it was so difficult to be honest.
https://chrisyeh96.github.io/2017/08/08/definitive-guide-python-imports.html#example-directory-structure
Then there
Rich Shepard writes:
> What is the proper syntax to import the model class in the model/
> subdirectory into a tkinter view module, e.g., activities.py? The syntax,
> 'import model as m' fails because it is not in the same subdirectory as the
> importing module.
>
> The program directory tree is:
On Thursday, 18 April 2019 06:59:43 UTC+10, Rich Shepard wrote:
> What is the proper syntax to import the model class in the model/
> subdirectory into a tkinter view module, e.g., activities.py? The syntax,
> 'import model as m' fails because it is not in the same subdirectory as the
> importing
What is the proper syntax to import the model class in the model/
subdirectory into a tkinter view module, e.g., activities.py? The syntax,
'import model as m' fails because it is not in the same subdirectory as the
importing module.
The program directory tree is:
bustrac/
README.rst
bustr
15 matches
Mail list logo
