Python 2.5 and py-crypto...

[Blair Zajac]

Jyrki Wahlstedt wrote:
> 
> On 22.2.2007, at 5.07, Blair Zajac wrote:
> 
>> Randall Wood wrote:
>>> On 21 Feb 2007, at 20:43, Landon Fuller wrote:
>>>>
>>>> On Feb 21, 2007, at 15:43, Weissmann Markus wrote:
>>>>
>>>>> Hi Douglas,
>>>>>
>>>>> the soon-to-be-released version 1.4 of port will come with a python 
>>>>> 2.5 "port group". This will allow us to quickly produce all the 
>>>>> python vastness for python 2.5, too.
>>>>> This might be a chance for newcomers to start coding Portfiles: 
>>>>> Basically you will have to replace the "GroupCode" line and the 
>>>>> name from the python 2.4 module Portfile to get a Python 2.5 one. 
>>>>> People with the release candidate of 1.4 installed can already hack 
>>>>> away here (just don't put that code into the repository yet - as 
>>>>> long as 1.4 is not released)
>>>>
>>>> I'm nonplussed by the massive code duplication that will occur for 
>>>> py25 portfiles -- these will almost invariably be direct copies of 
>>>> the py24 portfiles.
>>>> I'm not sure of the best solution -- perhaps python portgroup can 
>>>> either point to 24 or 25?
>>>>
>>> I'm  nonplussed (even upset) about broken python applications because 
>>> suddenly some py-* ports (read py-wxPython (there may be others--I 
>>> just don't know)) depend on python25 while other py-* ports depend on 
>>> python24.
>>
>> Ditto.  I am disappointed how the py-wxpython Port has been handled.  
>> I based a professional product on the 2.6 version 9 months ago which 
>> has shipped and worked great, and when we went to upgrade to HEAD, it 
>> doesn't build.
>>
> Me, too. Basically the problem is that wxPython and wxWidgets are 
> currently out of sync. That is very unfortunate, and that is still the 
> case. NB! Markus changed the said port to depend on python 2.4, but that 
> doesn't help much, because wxWidgets is already at 2.8.0 (devel is at 
> 2.8.2-rc1). We could have a port for wxWidgets 2.6(.3). I wrote that 
> already, but I have not committed that yet (does someone want this?).

Yes, that would be useful to have wxWidgets26 and a py-wxpython26 so we 
have a working build.

> BTW, py-wxpython should build fine (I built it with 2.5, and I guess 
> Markus built it with 2.4).

Last I tried py-wxpython was broken, even though wxWidgets-devel did 
build.  I should try again.

Regards,
Blair