I'm willing to help interested parties get up to speed with the python
rebuilding effort...it mostly just needs a lot of package rebuilding
currently...but I'm short on time to complete the project myself right now.
There is a project page tracking my work so you could just pick up where I
left off.

Moving to 2.7 would be good but requires somewhat more initial effort.
Given the issues Maciej had and my time availability, I opted to just made
2.6 healthier.

Thanks
-Ben
On Jan 8, 2013 1:46 PM, "Reaves, Timothy E" <[email protected]>
wrote:

> Thanks for the reply.
>
> Thats too bad; 2.7 introduced a few needed features, but, some of the
> libraries out there do not support 3.3 yet, so I can't migrate.  2.7
> compiles just fine for me, but my organization wants a package, so I'll
> just need to make the package for the installer.
>
>
>
>
> -----Original Message-----
> From: [email protected] on
> behalf of Maciej (Matchek) Blizinski
> Sent: Mon 1/7/2013 6:40 PM
> To: Questions and discussions
> Subject: Re: [csw-users] Python 2.7
>
> 2013/1/7 Reaves, Timothy E <[email protected]>:
> > I see where work for 2.7 support was done as far back as late 2011, but,
> I
> > see no actual release for it.  Anyone have any ideas when one will be
> made?
>
> I don't think there will be a 2.7 release. We'll probably skip all the
> intermediate versions and go straight to 3.3. I released the first
> version into unstable today.
>
> I'll be also looking into building a 64-bit version, but all my
> previous attempts failed[1].
>
> Maciej
>
> [1] http://lists.opencsw.org/pipermail/maintainers/2010-April/011834.html
> _______________________________________________
> users mailing list
> [email protected]
> https://lists.opencsw.org/mailman/listinfo/users
>
>
> _______________________________________________
> users mailing list
> [email protected]
> https://lists.opencsw.org/mailman/listinfo/users
>
_______________________________________________
users mailing list
[email protected]
https://lists.opencsw.org/mailman/listinfo/users

Reply via email to