[Twisted-Python] TypeError: Class advice impossible in Python3
Itamar Is there some sort of upper bound on when PB would be available for Python3.3? I am hoping to use it for a Python3 project. Any proposals to switch from PB to Foolscap in the upcoming releases of Twisted?
On 03:15 am, abhishekbhat@hotmail.com wrote:
Itamar Is there some sort of upper bound on when PB would be available for Python3.3? I am hoping to use it for a Python3 project.
As with any development, it will happen when people do it. :) Twisted development is almost entirely on a volunteer basis, and people mostly work on what they personally want to work on. If you're wondering who's currently working on porting PB to Python 3, I don't think anyone is.
Any proposals to switch from PB to Foolscap in the upcoming releases of Twisted?
No. Foolscap is not backwards compatible with PB, so there won't be a switch from one to the other. Fortunately, there's nothing that prevents you from ignoring PB and instead using Foolscap in any of your Twisted-based projects. Jean-Paul
On Jan 12, 2013, at 7:29 PM, exarkun@twistedmatrix.com wrote:
On 03:15 am, abhishekbhat@hotmail.com wrote:
Itamar Is there some sort of upper bound on when PB would be available for Python3.3? I am hoping to use it for a Python3 project.
As with any development, it will happen when people do it. :) Twisted development is almost entirely on a volunteer basis, and people mostly work on what they personally want to work on.
If you're wondering who's currently working on porting PB to Python 3, I don't think anyone is.
Hi Abhishek, _You_ could always contribute a port of PB to Python 3. PB is itself a pretty self-contained module with not many dependencies outside of what's already been ported. Porting it to Python 3 should be relatively straightforward, and the existing python 3 ports should provide a good example of how to do it. -glyph
Hi! Sorry for off-topic. What is the motivation behind creation of Foolscap (newpb)? What does it solve that can't be solved by old PB? Thank you On 13 January 2013 07:48, Glyph <glyph@twistedmatrix.com> wrote:
On Jan 12, 2013, at 7:29 PM, exarkun@twistedmatrix.com wrote:
On 03:15 am, abhishekbhat@hotmail.com wrote:
Itamar Is there some sort of upper bound on when PB would be available for Python3.3? I am hoping to use it for a Python3 project.
As with any development, it will happen when people do it. :) Twisted development is almost entirely on a volunteer basis, and people mostly work on what they personally want to work on.
If you're wondering who's currently working on porting PB to Python 3, I don't think anyone is.
Hi Abhishek,
_You_ could always contribute a port of PB to Python 3. PB is itself a pretty self-contained module with not many dependencies outside of what's already been ported. Porting it to Python 3 should be relatively straightforward, and the existing python 3 ports should provide a good example of how to do it.
-glyph
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
-- with regards, Maxim
The Foolscap website describes the principal features (as differences to PB): http://foolscap.lothar.com/trac/wiki/FoolscapFeatures On Mon, Jan 14, 2013 at 9:53 AM, Maxim Lacrima <lacrima.maxim@gmail.com>wrote:
Hi!
Sorry for off-topic.
What is the motivation behind creation of Foolscap (newpb)? What does it solve that can't be solved by old PB?
Thank you
On 13 January 2013 07:48, Glyph <glyph@twistedmatrix.com> wrote:
On Jan 12, 2013, at 7:29 PM, exarkun@twistedmatrix.com wrote:
On 03:15 am, abhishekbhat@hotmail.com wrote:
Itamar Is there some sort of upper bound on when PB would be available for Python3.3? I am hoping to use it for a Python3 project.
As with any development, it will happen when people do it. :) Twisted development is almost entirely on a volunteer basis, and people mostly work on what they personally want to work on.
If you're wondering who's currently working on porting PB to Python 3, I don't think anyone is.
Hi Abhishek,
_You_ could always contribute a port of PB to Python 3. PB is itself a pretty self-contained module with not many dependencies outside of what's already been ported. Porting it to Python 3 should be relatively straightforward, and the existing python 3 ports should provide a good example of how to do it.
-glyph
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
-- with regards, Maxim
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
-- cheers lvh
On 14 January 2013 15:40, Laurens Van Houtven <_@lvh.cc> wrote:
The Foolscap website describes the principal features (as differences to PB):
Thank you! -- with regards, Maxim
participants (5)
-
ABHISHEK BHAT -
exarkun＠twistedmatrix.com -
Glyph -
Laurens Van Houtven -
Maxim Lacrima