[python-committers] [Python-Dev] RELEASED Python 3.0 final
Jesse Noller
jnoller at gmail.com
Sat Dec 6 23:45:16 CET 2008
More information about the python-committers mailing list
Sat Dec 6 23:45:16 CET 2008
- Previous message: [python-committers] [Python-Dev] RELEASED Python 3.0 final
- Next message: [python-committers] [Python-Dev] RELEASED Python 3.0 final
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Dec 6, 2008 at 5:26 PM, Brett Cannon <brett at python.org> wrote: > On Fri, Dec 5, 2008 at 23:35, Ronald Oussoren <ronaldoussoren at mac.com> wrote: >> >> On 6 Dec, 2008, at 0:52, Brett Cannon wrote: >> >>> On Fri, Dec 5, 2008 at 15:40, "Martin v. Löwis" <martin at v.loewis.de> >>> wrote: >>>>> >>>>> How does that sounds? >>>> >>>> Sounds good! Are we also going to produce OSX binaries on a regular >>>> basis? >>>> >>>> Specifically, who is working on binaries for 3.0 and 2.6.1? Ronald? >>>> (the 2.6.1 release page claims that they are signed with Benjamin's >>>> key, but no binary is even available. Before this gets fixed, I >>>> think we need to agree on who is going to produce the binaries, and >>>> using what schedule.) >>>> >>> >>> What we probably should do is outline the steps in PEP 101 for >>> building the various binaries. For instance I could cut OS X releases >>> but I just don't know the exact steps are. >> >> For 2.5.x I used to following procedure. >> >> Requirements: >> >> * An Intel Mac running 10.4.x >> > > That requirement right there take me out for being able to to do the binary. > > -Brett I could do binaries for 10.5 and forward. I've got a few macs at my disposal
- Previous message: [python-committers] [Python-Dev] RELEASED Python 3.0 final
- Next message: [python-committers] [Python-Dev] RELEASED Python 3.0 final
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list