#59912 closed defect (fixed)
python38 @3.8.1_0: IDLE.app And Python Launcher.app Installed In "/opt/local/Applications/Python 3.8" Instead Of "/Applications/MacPorts/Python 3.8"
Reported by: | Quibi (Quibizo) | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.2 |
Keywords: | Cc: | tobypeterson, reneeotten (Renee Otten), EFdev, jmroot (Joshua Root) | |
Port: | python38 |
Description
The application bundles IDLE.app and Python Launcher.app for Python 3.8 are installed in "/opt/local/Applications/Python 3.8" not in "/Applications/MacPorts/Python 3.8". as bundles for other Python versions (for instance, such as, "/Applications/MacPorts/Python 3.7").
After installing Python 3.8, I have noticed that IDLE and Python Launcher for this version are not in macOS Application folder but in a sub-folder in /opt/local. I have manually moved them to the Application folder.
I checked my macports configuration file macports.conf but found that applications_dir is properly set:
applications_dir /Applications/MacPorts
I am not sure if I should check other configurations or settings that can cause this defect.
I am running macOs Mojave 10.14.6
Thank you.
Change History (5)
comment:1 Changed 5 years ago by kencu (Ken)
comment:2 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | jmroot added |
---|---|
Priority: | Low → Normal |
Joshua, do you want to maintain python38 as well, since you already maintain the other python3* ports?
comment:3 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | set to ryandesign |
---|---|
Status: | new → accepted |
However, I see what the problem is here and should be able to fix it shortly.
comment:4 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
comment:5 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
In cfb13a1880b90631596bfed118a1726664e8f986/macports-ports (dar, master, py38-reproject, revert-6945-rust-1.43.0, wireshark):
You are exactly correct. Something is messed up: