Just a brief note, I released Foolscap-0.6.4 tonight. This contains a
handful of small bugfixes and cleanups, gathered over the last 5 months.
The most significant change was that the "git-foolscap" tools were
cleaned up. These live in doc/examples/ , and let you configure remote
access to your G
Hello everyone,
as some of you may be aware, I was accepted as a Google Summer of Code
student, with the project of porting Twisted to Python 3 (or getting
as close as possible)[1]. Now, there are basically two strategies:
maintaining py2 code and using 2to3 when installing under py3, or
maintaini
On 06/19/2012 10:43 AM, Vladimir Perić wrote:
> 3) apply
>
> To quote Lennart Regebro, "The Python 2 builtin apply() has been
> removed in Python 3. It’s used to call a function, but since you can
> call the function directly it serves no purpose and has been
> deprecated since Python 2.3." I've re
On Jun 19, 2012, at 7:43 AM, Vladimir Perić wrote:
> there are basically two strategies:
> maintaining py2 code and using 2to3 when installing under py3, or
> maintaining a codebase which is compatible with both 2 and 3
Based on the experiences of other porters I have talked to, and heard speaki
On Tue, 19 Jun 2012 08:55:51 -0700
Glyph wrote:
>
> On Jun 19, 2012, at 7:43 AM, Vladimir Perić wrote:
>
> > there are basically two strategies:
> > maintaining py2 code and using 2to3 when installing under py3, or
> > maintaining a codebase which is compatible with both 2 and 3
>
> Based on th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/19/2012 07:15 PM, Antoine Pitrou wrote:
> On Tue, 19 Jun 2012 08:55:51 -0700 Glyph
> wrote:
>>
>> On Jun 19, 2012, at 7:43 AM, Vladimir Perić wrote:
>>
>>> there are basically two strategies: maintaining py2 code and
>>> using 2to3 when instal
> That said, there are
> syntax changes ('except...as...' being the big one) that make supporting
> 2.5->3 difficult, and only becomes reasonable at 2.6->3. So it may be
> necessary to get 2to3 involved for some fixers.
We've dropped support for 2.6 post-12.1. So that's not a problem. We can
do
Le Jun 19, 2012 à 10:50 AM, Itamar Turner-Trauring a
écrit :
> We've dropped support for 2.6 post-12.1. So that's not a problem. We can
> do these changes now in trunk.
I really hope you mean 2.5.___
Twisted-Python mailing list
Twisted-Python@twistedm
> Le Jun 19, 2012 à 10:50 AM, Itamar Turner-Trauring a
> écrit :
>
>> We've dropped support for 2.6 post-12.1. So that's not a problem. We can
>> do these changes now in trunk.
>
> I really hope you mean 2.5.
Sigh. Yes. Next release will be 2.6 and later.
___
On Wed, Jun 20, 2012 at 2:28 AM, Itamar Turner-Trauring wrote:
> > Le Jun 19, 2012 à 10:50 AM, Itamar Turner-Trauring
> a
> > écrit :
> >
> >> We've dropped support for 2.6 post-12.1. So that's not a problem. We can
> >> do these changes now in trunk.
> >
> > I really hope you mean 2.5.
>
> Sigh
On 06/19/2012 03:01 PM, gelin yan wrote:
>
> Sigh too, I am still using 2.6.6 & twisted 11.0; however I think it
> is not so difficult to migrate to 2.7.
>
Just to be clear, Python 2.6 is still supported as of 12.1 and will
continue to be supported (at the minimum for the next release and
proba
11 matches
Mail list logo
