[Fink-devel] Framework Python build, again
Last March there was a discussion[1] that generated a fair amount of interest, about creating a Framework build of Python. As far as I can tell nothing ever came of it but I wanted to check and see if anyone has done any work towards this goal. The reason I ask is because I'm trying to package the Enthought Tool Suite[2]. Although I have been able to make some progress building with a wxGTK version of wxPython, life would be much easier if I could package the wxMac version and use it instead. Happy New Year, [1] http://www.nabble.com/Framework-Python-build-to9323515.html [2] http://code.enthought.com/ -- Jed Frechette University of New Mexico Lidar Lab www.unm.edu/~lidar - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel
Re: [Fink-devel] Framework Python build
On 3/7/07, Peter O'Gorman [EMAIL PROTECTED] wrote: On Mar 7, 2007, at 3:55 PM, Blair Zajac wrote: Peter O'Gorman wrote: On Mar 6, 2007, at 8:58 AM, Blair Zajac wrote: 1) Would the Python maintainers be willing to take patches for a framework install? I'd make a new package and ensure that it does not have any conflicting files with any fink python packages. There then does not need to be any interaction with the current python maintainers. Although Apple puts symlinks from the framework back into /usr/lib etc, it is not necessary for fink to do so. This will allow you to customize the python framework build as necessary for your PyQt apps. And presumably we can have this new Python still reference Python modules for the non-Framework build, as this would be ideal??? If not, then we could add a new Type: Type: Type: python (2.4 2.4-framework 2.5 2.5-framework) The maintainer can choose what paths to search etc. But, if I were the maintainer, I'd do both. Have a specific path for your framework python that is searched before the other fink paths. Then you can have modules that require macpython in your 2.5- framework type and still leverage the normal 2.5 modules. Modules in the framework dir will be found first, so you can actually have the cake and eat it too. Peter, In that case, would you want python2.4-framework to provide a virtual python2.4? -- - Charles Lepple - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Framework Python build
On Mar 7, 2007, at 11:04 PM, Charles Lepple wrote: On 3/7/07, Peter O'Gorman [EMAIL PROTECTED] wrote: On Mar 7, 2007, at 3:55 PM, Blair Zajac wrote: Peter O'Gorman wrote: On Mar 6, 2007, at 8:58 AM, Blair Zajac wrote: 1) Would the Python maintainers be willing to take patches for a framework install? I'd make a new package and ensure that it does not have any conflicting files with any fink python packages. There then does not need to be any interaction with the current python maintainers. Although Apple puts symlinks from the framework back into /usr/lib etc, it is not necessary for fink to do so. This will allow you to customize the python framework build as necessary for your PyQt apps. And presumably we can have this new Python still reference Python modules for the non-Framework build, as this would be ideal??? If not, then we could add a new Type: Type: Type: python (2.4 2.4-framework 2.5 2.5-framework) The maintainer can choose what paths to search etc. But, if I were the maintainer, I'd do both. Have a specific path for your framework python that is searched before the other fink paths. Then you can have modules that require macpython in your 2.5- framework type and still leverage the normal 2.5 modules. Modules in the framework dir will be found first, so you can actually have the cake and eat it too. Peter, In that case, would you want python2.4-framework to provide a virtual python2.4? No, I don't think that would be a good idea. Yes, I know that means requiring users to have 2 fink python2.4 etc installed if they want to use Blair's PyQt apps. I'l let other people pipe up though, I'm just saying what I believe I would do in Blair's position. Peter - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Framework Python build
Peter O'Gorman wrote: On Mar 7, 2007, at 3:55 PM, Blair Zajac wrote: Peter O'Gorman wrote: On Mar 6, 2007, at 8:58 AM, Blair Zajac wrote: 1) Would the Python maintainers be willing to take patches for a framework install? I'd make a new package and ensure that it does not have any conflicting files with any fink python packages. There then does not need to be any interaction with the current python maintainers. Although Apple puts symlinks from the framework back into /usr/lib etc, it is not necessary for fink to do so. This will allow you to customize the python framework build as necessary for your PyQt apps. And presumably we can have this new Python still reference Python modules for the non-Framework build, as this would be ideal??? If not, then we could add a new Type: Type: Type: python (2.4 2.4-framework 2.5 2.5-framework) The maintainer can choose what paths to search etc. But, if I were the maintainer, I'd do both. Have a specific path for your framework python that is searched before the other fink paths. Then you can have modules that require macpython in your 2.5-framework type and still leverage the normal 2.5 modules. Modules in the framework dir will be found first, so you can actually have the cake and eat it too. Peter Good idea. The only other thing then would be to have a python2.5-bin and a python2.5-framework-bin that provides the symlinks for python to python2.5 or python2.5-framework binaries. Blair - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Framework Python build
Blair Zajac wrote: We have a large number of PyQt apps on Linux for a special effect studio. We use PyQt apps to manage a large render farm for special effects, examining artwork, playing back renders at high resolutions, and other apps for lighting and compositing, etc. More of our users are using Mac's and want the same tools on their Mac desktops, so we're starting to build the infrastructure to support them. Currently I'm using MacPorts since it provides a framework Python and Qt for Mac. However, I'm finding the distribution of MacPorts packages to other hosts painful because it puts files in other places besides /opt/local and there is no easy way to dist out new packages to systems. My current solution to disting out new packages to clients is ugly: deactivate all ports so that everything only lives in /opt/local, rsync any changes into /opt/local, then reactivate the ports. Painful and during the upgrade, nothing that relies upon /opt/local will work. I could do this better, but in the end, the package management isn't as nice as dpkg and apt-get. So I want to use switch to Fink for apt-get and use an entire Fink tree. However, Python is not a Framework build. We can't use a X11 build since the performance for playback of renders is not good enough and the users are artists, not developers who would mind using X11. We need the native playback speed at 24 frames per second. Reading some of the other comments on framework Python in the mailing list, one comment was that .apps and frameworks are meant to be relocatable. I'm not interested in building applications where we can just relocate the entire Python tree. We have a complicated set of Python modules with our own versioning system, so my vision is that /sw/bin/aqua-python will always be provided and all our custom module will live in a known location. Any applications can have their Contents/MacOS/Appname be a shell script that just execs the framework python. I should also mention that all our Python code is written to Python 2.4, so we can't use the system's 2.3 Python. Also with 2.5 out, we'd like to move to that for the increased performance. So several questions: 1) Would the Python maintainers be willing to take patches for a framework install? 2) Should this be done on the original python2?.info, or a separate Python package be built, maybe that just installs the files that are new on top of the python2?.info file. Ideally, the Framework install would leverage the non-Framework install. 3) Would it be possible to add the --enable-frameworks to the build? I presume this will break everything, otherwise it would have been done? Could we add symlinks from the framework build back to the non-framework build to support this? Any suggestions would help. I would like to see Fink grow the ability to run Aqua PyQt or PyWxWidgets apps. Regards, Blair Blair: Speaking as the fink python maintainer, ff the fink python package could be converted to a framework install without too much breakage, I'm all for that. I haven't thought about all the issues, but I think it's worth exploring. One that occurs to me right off the bat is what do we do with the Tkinter module - keep using the X11 version, use the aqua version, or try to have both? -Jeff -- Jeffrey S. Whitaker Phone : (303)497-6313 Meteorologist FAX: (303)497-6449 NOAA/OAR/PSD R/PSD1Email : [EMAIL PROTECTED] 325 BroadwayOffice : Skaggs Research Cntr 1D-124 Boulder, CO, USA 80303-3328 Web: http://tinyurl.com/5telg - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Framework Python build
On 7 Mar 2007, at 16:33, Jeff Whitaker wrote: Blair: Speaking as the fink python maintainer, ff the fink python package could be converted to a framework install without too much breakage, I'm all for that. I haven't thought about all the issues, but I think it's worth exploring. I am extremely interested in a framework python in fink, along with a wxpthon that doesn't need gtk and X11. This is the only reason that I am using MacPorts, and I would be very, very happy to be able to go back to only using fink. Some MacPorts stuff insists on linking to / sw libraries, even if /sw is not in the path, and that is causing me untold grief. The only way to safely upgrade MacPorts packages is to temporarily move /sw aside, and that breaks a lot of other software that I use regularly. Ugh. Kevin Horton Ottawa, Canada - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Framework Python build
Peter O'Gorman wrote: On Mar 6, 2007, at 8:58 AM, Blair Zajac wrote: We have a large number of PyQt apps on Linux for a special effect studio. We use PyQt apps to manage a large render farm for special effects, examining artwork, playing back renders at high resolutions, and other apps for lighting and compositing, etc. More of our users are using Mac's and want the same tools on their Mac desktops, so we're starting to build the infrastructure to support them. I should also mention that all our Python code is written to Python 2.4, so we can't use the system's 2.3 Python. Also with 2.5 out, we'd like to move to that for the increased performance. So several questions: 1) Would the Python maintainers be willing to take patches for a framework install? I'd make a new package and ensure that it does not have any conflicting files with any fink python packages. There then does not need to be any interaction with the current python maintainers. Although Apple puts symlinks from the framework back into /usr/lib etc, it is not necessary for fink to do so. This will allow you to customize the python framework build as necessary for your PyQt apps. And presumably we can have this new Python still reference Python modules for the non-Framework build, as this would be ideal??? If not, then we could add a new Type: Type: Type: python (2.4 2.4-framework 2.5 2.5-framework) Regards, Blair -- Blair Zajac, Ph.D. [EMAIL PROTECTED] Subversion training, consulting and support http://www.orcaware.com/svn/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
