On 11:15 am, _...@lvh.cc wrote:
>I hear tickets is how you get things done: http://tm.tl/5181
But not this. If we want *new* backwards compatibility stuff to be
private, then give it a private name. The old stuff is public though,
so it should be treated how we treat public stuff.
Jean-Paul
I hear tickets is how you get things done: http://tm.tl/5181
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
On Jul 5, 2011, at 8:32 AM, Laurens Van Houtven wrote:
> In doing twisted.positioning I find my self writing a bunch of code in ways I
> would ordinarily write it differently, because we have to support 2.4 still
> (when is that going away? Isn't the most recent RHEL 2.6 already?).
>
> Is there
On Tue, Jul 5, 2011 at 2:41 PM, Laurens Van Houtven <_...@lvh.cc> wrote:
> By "registration" I meant stuff where we could put reminders that some code
> can be cleaned up now.
>
> Perhaps that means "ticket", if there's some way to mark a ticket as being
> only relevant when we stop supporting $PY
On Tue, 2011-07-05 at 14:32 +0200, Laurens Van Houtven wrote:
> In doing twisted.positioning I find my self writing a bunch of code in
> ways I would ordinarily write it differently, because we have to
> support 2.4 still (when is that going away? Isn't the most recent RHEL
> 2.6 already?).
The p
On 01:41 pm, _...@lvh.cc wrote:
>By "registration" I meant stuff where we could put reminders that some
>code
>can be cleaned up now.
>
>Perhaps that means "ticket", if there's some way to mark a ticket as
>being
>only relevant when we stop supporting $PYTHON_VERSION_WHATEVER?
In the past we ha
By "registration" I meant stuff where we could put reminders that some code
can be cleaned up now.
Perhaps that means "ticket", if there's some way to mark a ticket as being
only relevant when we stop supporting $PYTHON_VERSION_WHATEVER?
cheers
lvh
___
On 12:32 pm, _...@lvh.cc wrote:
>Hi,
>
>
>In doing twisted.positioning I find my self writing a bunch of code in
>ways
>I would ordinarily write it differently, because we have to support 2.4
>still (when is that going away? Isn't the most recent RHEL 2.6
>already?).
>
>Is there some way to regis
Hi,
In doing twisted.positioning I find my self writing a bunch of code in ways
I would ordinarily write it differently, because we have to support 2.4
still (when is that going away? Isn't the most recent RHEL 2.6 already?).
Is there some way to register that so that as soon as we stop supporti
