I was thinking more of the convenience when working with make files. I have a workaround but it sure would be nice if it were cleaner. ...and now I have two. ;-) > The nuisance item at the top of my list is.... a site-packages link. > > In the same way as we have links in Python.framework for Headers and > Resources to their equivalents in the 'current' version, I'd like to > see a link to the 'current' site-packages. This would provide a > simple programmatic way to get there without first having to determine > which is the current version and construct the path accordingly. > > Specialized, and perhaps further down the list is Orange, a machine > learning/data mining library. http://magix.fri.uni-lj.si/orange/ (disclaimer: never used Orange, don't really know much about it) OrangeWidgets is dependent on PyQt.. I don't know if you need that for it to be useful though, but PyQt definitely does not exist for Qt/Mac yet. As far as locating site-packages programmatically goes.. [crack:~] bob% python -c "import distutils.sysconfig;print distutils.sysconfig.get_python_lib()" /Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site- packages -bob
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4