Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

85%
+10 −0
Q&A Different behavior with relative imports when using flask vs py

I don't have a py command on my system; for purposes of this answer I assume it's an alias to the python executable. Running a script from a file is not quite the same as importing it. A script giv...

posted 3y ago by ajv‭  ·  edited 3y ago by ajv‭

Answer
#2: Post edited by user avatar ajv‭ · 2020-08-11T01:44:22Z (over 3 years ago)
  • I don't have a `py` command on my system; for purposes of this answer I assume it's an alias to the python executable.
  • Running a script from a file is not quite the same as importing it. A script given on the command line doesn't know it's a package (`__package__` is not set). That's why relative imports don't work.
  • What you probably want is to run it by module path, not filename. Assuming your top-level project directory is named `yourapp`:
  • ```
  • python3 -m yourapp.app
  • ```
  • Run this from somewhere that `yourapp` is importable. Unless you've done something odd with PYTHONPATH, the parent of your top-level project directory should work.
  • (even better would be to make a setup.py and use it to pip-install the package; then your working directory won't matter. But you specified no structural changes, so.)
  • I don't have a `py` command on my system; for purposes of this answer I assume it's an alias to the python executable.
  • Running a script from a file is not quite the same as importing it. A script given on the command line doesn't know it's a package (`__package__` is not set). That's why relative imports don't work.
  • What you probably want is to run it by module path, not filename. Assuming your top-level project directory is named `yourapp`:
  • ```
  • python3 -m yourapp.app
  • ```
  • Run this from somewhere that `yourapp` is importable. Unless you've done something odd with PYTHONPATH, the parent of your top-level project directory should work. You can check importability from the current directory with `python3 -c 'import yourapp'` or similar.
  • (even better would be to make a setup.py and use it to pip-install the package; then your working directory won't matter. But you specified no structural changes, so.)
#1: Initial revision by user avatar ajv‭ · 2020-08-11T01:40:20Z (over 3 years ago)
I don't have a `py` command on my system; for purposes of this answer I assume it's an alias to the python executable.

Running a script from a file is not quite the same as importing it. A script given on the command line doesn't know it's a package (`__package__` is not set). That's why relative imports don't work.

What you probably want is to run it by module path, not filename. Assuming your top-level project directory is named `yourapp`:

```
python3 -m yourapp.app
```

Run this from somewhere that `yourapp` is importable. Unless you've done something odd with PYTHONPATH, the parent of your top-level project directory should work.

(even better would be to make a setup.py and use it to pip-install the package; then your working directory won't matter. But you specified no structural changes, so.)