Replies: 3 comments 3 replies
-
Indeed. This could be handle in a project specific env.json file instead. I prefer a json file instead of project.properties because i am not sure if it handles well multi values. I will also look how vscode deal with this. |
Beta Was this translation helpful? Give feedback.
-
JSON files are good but when opened in NB completely unreadable, everything is on one line. It would be useful to have an equivalent of such presentation as in |
Beta Was this translation helpful? Give feedback.
-
Today I was testing a new small project in NB 19 and netbeansPython 1.5. The import problem in unit tests still occurs. Is it already possible to set the correct PYTHONPATH somewhere? |
Beta Was this translation helpful? Give feedback.
-
After standard project generation, I added the func1 function to the main.py file.
I then generated a standard test unit file. After these operations, the unit tests worked.
Next, I wanted to test the func1 function. I added the following code:
from main import func1
Unfortunately, this operation fails because the PYTHONPATH environment variable
contains the
/.../Project/tests
directory but not the/.../Project/
directory.I solved this problem by adding the appropriate PYTHONPATH variable in the global
configuration
NetBeans/Options/Python/Environment Variables
but this is nota good solution.
Can this be set somewhere just for a specific project? Maybe in the
nbproject/project.properties
file?Beta Was this translation helpful? Give feedback.
All reactions