On Oct 27, 2009, at 10:32 AM, Steve Steiner (listsin) wrote:
> Is this something that can be handled by just running the tests with
> the right switch so we can see everything that passes without the
> switch but doesn't with?
>
> Is there a "new-style" switch or just -3?
Download:
http://twisted
On Oct 27, 2009, at 8:17 AM, exar...@twistedmatrix.com wrote:
>> At that point there will be two sets of users, the 3.x's that
>> use only new-style classes and the 2.x's for which Twisted classes
>> may be either old or new. It would probably be better to have
>> switched to new-style before th
On 08:38 am, k.kelly.gor...@gmail.com wrote:
>On Sun, Oct 25, 2009 at 1:50 AM, wrote:
>>On 02:39 pm, k.kelly.gor...@gmail.com wrote:
>>>On Thu Oct 8 20:08:12 EDT 2009, Glyph Lefkowitz
>>> wrote:
If old-style classes can be evolved into new-style classes while
somehow following this policy
On Sun, Oct 25, 2009 at 1:50 AM, wrote:
> On 02:39 pm, k.kelly.gor...@gmail.com wrote:
>> On Thu Oct 8 20:08:12 EDT 2009, Glyph Lefkowitz
>> wrote:
>>> If old-style classes can be evolved into new-style classes while
>>> somehow following this policy, that would be great.
>> I have some POC co
On Sun, Oct 25, 2009 at 4:38 PM, Glyph Lefkowitz
wrote:
> On Oct 24, 2009, at 10:50 AM, exar...@twistedmatrix.com wrote:
>>
>> I think that we should consider requests to make specific classes new-
>> style (and grant them when doing so won't cause compatibility problems),
>> make all new classes
On Sun, Oct 25, 2009 at 5:32 PM, Glyph Lefkowitz
wrote:
> On Oct 25, 2009, at 1:50 AM, James Y Knight wrote:
>
>> On Oct 25, 2009, at 1:38 AM, Glyph Lefkowitz wrote:
>>> # in your application
>>> class Application(object, Library): pass
>>
>> Maybe the answer "why not" is obvious and I should alre
On Oct 25, 2009, at 1:50 AM, James Y Knight wrote:
On Oct 25, 2009, at 1:38 AM, Glyph Lefkowitz wrote:
What do you do? Well, the obvious upgrade path here is to make a
class which (A) inherits from "Library" to get Twisted
functionality and (B) inherits from "object" to get new-style-
ness
On Oct 25, 2009, at 1:38 AM, Glyph Lefkowitz wrote:
What do you do? Well, the obvious upgrade path here is to make a
class which (A) inherits from "Library" to get Twisted functionality
and (B) inherits from "object" to get new-style-ness. So you go
ahead and write:
# in your application
On Oct 24, 2009, at 10:50 AM, exar...@twistedmatrix.com wrote:
I think that we should consider requests to make specific classes new-
style (and grant them when doing so won't cause compatibility
problems),
make all new classes new-style, but otherwise leave this alone until
3.x
is widely a
On 02:39 pm, k.kelly.gor...@gmail.com wrote:
>On Thu Oct 8 20:08:12 EDT 2009, Glyph Lefkowitz twistedmatrix.com> wrote:
>>On Thu, Oct 8, 2009 at 7:59 PM, Mark Visser
>>wrote:
>>
>> > I've been bitten a couple times by twisted's use of old-style
>>classes.
>> > Now that Jython is finally off the
On Thu Oct 8 20:08:12 EDT 2009, Glyph Lefkowitz wrote:
> On Thu, Oct 8, 2009 at 7:59 PM, Mark Visser wrote:
>
> > I've been bitten a couple times by twisted's use of old-style classes.
> > Now that Jython is finally off the 2.2 branch, is there any real reason
> > to stay backwards compatible?
>
On Fri, Oct 09, 2009 at 03:45:02AM -, exar...@twistedmatrix.com wrote:
> However, if I were to make up a plan for porting Twisted to Python 3.x,
> then the first part of that plan would be to fix all of the failing
> tests reported here:
>
> http://buildbot.twistedmatrix.com/builders/python-
On 01:03 am, ma...@lumierevfx.com wrote:
>
>>For Python 3.x, oldstyle classes don't exist, so that'll happen
>>automatically during the conversion.
>Aha! Let me rephrase that, then:
>
>Is there a project underway to port Twisted to Python 3.x?
It would be misleading to characterize any part of Twi
On Thu, 2009-10-08 at 21:03 -0400, Mark Visser wrote:
> Is there a project underway to port Twisted to Python 3.x?
Not at the moment. Supporting both 2.x and 3.x is harder than it should
be, and all of Twisted's users (and almost all Python users) use 2.x.
-Itamar
_
Mark, you might find this link helpful:
http://stackoverflow.com/questions/172306/how-are-you-planning-on-handling-the-migration-to-python-3/214601#214601
Seems to me that the answer is no, there isn't a serious effort underway to
port to Python 3, and there probably won't be for a while. My gues
On Oct 8, 2009, at 9:03 PM, Mark Visser wrote:
>
>> For Python 3.x, oldstyle classes don't exist, so that'll happen
>> automatically during the conversion.
>>
> Aha! Let me rephrase that, then:
>
> Is there a project underway to port Twisted to Python 3.x?
Yes, it's called Twisted.
S
___
> For Python 3.x, oldstyle classes don't exist, so that'll happen
> automatically during the conversion.
>
Aha! Let me rephrase that, then:
Is there a project underway to port Twisted to Python 3.x?
cheers,
-Mark
--
Mark Visser, Software Director
Lumière VFX
Email: ma...@lumierevfx.com
Ph
On Oct 8, 2009, at 7:59 PM, Mark Visser wrote:
> I've been bitten a couple times by twisted's use of old-style classes.
> Now that Jython is finally off the 2.2 branch, is there any real
> reason
> to stay backwards compatible?
I don't see any reason to make this change for twisted running on th
On Thu, Oct 8, 2009 at 7:59 PM, Mark Visser wrote:
> Is there a project underway to modernize twisted?
>
Yes. The project is called "twisted" :). Personally I find that it is very
"modern".
I've been bitten a couple times by twisted's use of old-style classes.
> Now that Jython is finally off
Is there a project underway to modernize twisted?
I've been bitten a couple times by twisted's use of old-style classes.
Now that Jython is finally off the 2.2 branch, is there any real reason
to stay backwards compatible?
cheers,
-Mark
--
Mark Visser, Software Director
Lumière VFX
Email: ma.
20 matches
Mail list logo
