A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2005-January/050720.html below:

[Python-Dev] 2.3.5 schedule, and something I'd like to get in

[Python-Dev] 2.3.5 schedule, and something I'd like to get inBob Ippolito bob at redivi.com
Thu Jan 6 00:14:19 CET 2005
On Jan 5, 2005, at 17:38, Martin v. Löwis wrote:

> Bob Ippolito wrote:
>> Nope.  The only way to link to a non-current framework version is to  
>> forego any linker searching and specify the dyld file directly, i.e.  
>> /Library/Frameworks/Python.framework/Versions/2.3/Python.  The gcc  
>> toolchain does not in any way whatsoever understand versioned  
>> frameworks, period.
>
> I see. I wish you had told me right from the beginning.

That is only part of the reason for these changes (concurrent Python  
2.3 and Python 2.4 in the same location), and is fringe enough that I  
wasn't even thinking of it at the time.

I just dug up some information I had written on this particular topic  
but never published, if you're interested:
http://bob.pythonmac.org/archives/2005/01/05/versioned-frameworks- 
considered-harmful/

-bob

More information about the Python-Dev mailing list

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