-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Jun 19, 2008, at 4:43 AM, Paul Moore wrote:
Martin usually fills these in pretty quickly. I think the current
situation works fine for the betas but we'll make sure the final
release (and candidates) are better coordinated.
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSFpIpnE jvBPtnXfVAQJyWQ P9FSH8Ipg93UDM3 nmH3UtN+i61YGsQ Pd0O
ypHlnz4yHpxeRkJ m1zkppHHI0hKMou 6JOeUf05QCnPzrA dsG/mkuv5aoBrBt3dDd
UncHLoQOvXEhGrr PzexmHKv3ehxUXP QOzkiWBWVv9e69G YH4e4HcqV6s2Ya2 733T
zC/EyOgkyMg=
=5wM5
-----END PGP SIGNATURE-----
Hash: SHA1
On Jun 19, 2008, at 4:43 AM, Paul Moore wrote:
On 19/06/2008, Barry Warsaw <barry@python.o rgwrote:
>
Any ETA for Windows builds? The web pages still point to the alphas.
(I'd like to see the Windows builds more closely integrated with the
releases now we're in beta stage...)
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>>
>On behalf of the Python development team and the Python community,
>I am
>happy to announce the first beta releases of Python 2.6 and Python
>3.0.
>Hash: SHA1
>>
>On behalf of the Python development team and the Python community,
>I am
>happy to announce the first beta releases of Python 2.6 and Python
>3.0.
Any ETA for Windows builds? The web pages still point to the alphas.
(I'd like to see the Windows builds more closely integrated with the
releases now we're in beta stage...)
situation works fine for the betas but we'll make sure the final
release (and candidates) are better coordinated.
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSFpIpnE jvBPtnXfVAQJyWQ P9FSH8Ipg93UDM3 nmH3UtN+i61YGsQ Pd0O
ypHlnz4yHpxeRkJ m1zkppHHI0hKMou 6JOeUf05QCnPzrA dsG/mkuv5aoBrBt3dDd
UncHLoQOvXEhGrr PzexmHKv3ehxUXP QOzkiWBWVv9e69G YH4e4HcqV6s2Ya2 733T
zC/EyOgkyMg=
=5wM5
-----END PGP SIGNATURE-----