Feature #1260
Windows: installer should create PYTHONPATH environment variable in system scope and not in user scope
| Status: | Archived | Start date: | 15 Dec 2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | pospelov | % Done: | 0% | |
| Category: | - | |||
| Target version: | Sprint 30 |
Description
For the moment PYTHONPATH variable is created in user scope. If BornAgain installed from administrator, and used by normal user, the PYTHONPATH variable doesn't exist and Python is not able to locate bornagain module.
History
#1 Updated by pospelov almost 5 years ago
- Assignee set to pospelov
#2 Updated by pospelov almost 5 years ago
- Status changed from Sprint to Resolved
Made Windows installer to define PYTONPATH on system level. Hardcoded behavior. It is too complicated to make this feature selectable (local user, global user) because of NSIS. Waiting for Qt installer framework to make everything properly.
#3 Updated by pospelov over 4 years ago
- Status changed from Resolved to Archived