Opened 3 years ago
Last modified 9 months ago
#8660 assigned defect
Use equivalent of realpath(sys.executable) in launcher
| Reported by: | Zach Pearson | Owned by: | Greg Couch |
|---|---|---|---|
| Priority: | moderate | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Notify when closed: | Platform: | all | |
| Project: | ChimeraX |
Description
Many areas of ChimeraX code depend on accurately knowing where the executable lives, but on some platforms what actually gets called to start ChimeraX can be a symbolic link to the executable, which throws that code off. Rather than putting os.path.realpath(...) everywhere, an alternative is to set argv[0] to the executable's real path in the launcher.
Change History (5)
comment:1 by , 3 years ago
| Component: | Unassigned → Core |
|---|
comment:2 by , 2 years ago
| Milestone: | 1.7 → 1.8 |
|---|
comment:3 by , 19 months ago
comment:4 by , 17 months ago
| Milestone: | 1.8 |
|---|
comment:5 by , 9 months ago
We're using realpath in Python instead now (see src/bundles/core/src/{python_utils.py,utils.py,\_\_main\_\_.py}) so this can probably be closed.
Note:
See TracTickets
for help on using tickets.
This seems like a good idea, but it can confuse users when the path used to run ChimeraX is different from its actual path.