-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/03/2015 03:37 PM, Doug Hellmann wrote:
>
>
> On Tue, Mar 3, 2015, at 07:56 AM, Ihar Hrachyshka wrote: On
> 02/02/2015 05:15 PM, Jeremy Stanley wrote:
After a long wait and much testing, we've merged a change[1]
which moves the remaind
On Tue, Mar 3, 2015, at 07:56 AM, Ihar Hrachyshka wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 02/02/2015 05:15 PM, Jeremy Stanley wrote:
> > After a long wait and much testing, we've merged a change[1] which
> > moves the remainder of Python 3.3 based jobs to Python 3.4. Thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/02/2015 05:15 PM, Jeremy Stanley wrote:
> After a long wait and much testing, we've merged a change[1] which
> moves the remainder of Python 3.3 based jobs to Python 3.4. This
> is primarily in service of getting rid of the custom workers we
>
On 2015-02-03 08:15:39 -0500 (-0500), Victor Stinner wrote:
[...]
> Debian Testing (Jessie) and Unstable (Sid) provide Python 3.4.2.
[...]
Yep, I'm playing now with the possibility to run jobs on Debian
Jessie, but due to circumstances with the providers who donate
computing resource to us I'm fir
Hi,
It's good to move forward to Python 3.4 :-)
> [2] https://launchpad.net/bugs/1367907
This bug was introduced in Python 3.4.0 and fixed in Python 3.4.1. It's too bad
that Ubunbu Trusty didn't upgraded yet Python 3.4 to 3.4.1 (released 6 months
ago) or 3.4.2. Request to upgrade python 3.4 in
After a long wait and much testing, we've merged a change[1] which
moves the remainder of Python 3.3 based jobs to Python 3.4. This is
primarily in service of getting rid of the custom workers we
implemented to perform 3.3 testing more than a year ago, since we
can now run 3.4 tests on normal Ubunt
