Installer should create .pth files for Python installation(s)
Reported by Christopher Stawarz | April 20th, 2010 @ 06:46 PM | in 0.4.5 (closed)
To relieve the user of the burden of setting PYTHONPATH (or equivalent) manually, the installer should create a mworks.pth file in all supported Python installations. The contents of the file would just be:
/Library/Application Support/MWorks/Scripting/Python
The installation directory would vary with Python distribution. Some examples:
- system 2.6: /Library/Python/2.6/site-packages
- python.org 2.6: /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages
- EPD 6.1: /Library/Frameworks/Python.framework/Versions/6.1/lib/python2.6/site-packages
See Modifying Python’s Search Path for an explanation of .pth files.
Comments and changes to this ticket
-
Christopher Stawarz July 7th, 2010 @ 03:37 PM
- Assigned user set to “Christopher Stawarz”
- Milestone set to “0.4.5”
- State changed from “new” to “resolved”
- Milestone order changed from “0” to “0”
Implemented in mw_core commit b6316669bbdc5772b45f22b63b384ea3d1b813d5 for the system Python 2.6. We can worry about other Pythons when/if we support them.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
MWorks accessory libraries, build system, etc.
Christopher Stawarz