Comments for Oakwinter.com :: Code http://oakwinter.com/code Fri, 12 Mar 2010 04:22:41 +0000 http://wordpress.org/?v=2.2 Comment on Porting setuptools to py3k by Blake Winton http://oakwinter.com/code/porting-setuptools-to-py3k/#comment-22224 Blake Winton Tue, 16 Oct 2007 19:26:30 +0000 http://oakwinter.com/code/porting-setuptools-to-py3k/#comment-22224 Couldn't you just create and add a CmpMixin, which defines all the comparison operators in terms of __cmp__? I suspect such a thing will be very popular in Python 3.0, so getting one out there today would be a good idea. ;) Later, Blake. Couldn’t you just create and add a CmpMixin, which defines all the comparison operators in terms of __cmp__?

I suspect such a thing will be very popular in Python 3.0, so getting one out there today would be a good idea. ;)

Later,
Blake.

]]> Comment on Motivation for rewriting unittest by John Lee http://oakwinter.com/code/motivation-for-rewriting-unittest/#comment-22176 John Lee Sun, 14 Oct 2007 14:47:39 +0000 http://oakwinter.com/code/motivation-for-rewriting-unittest/#comment-22176 nose 0.10 (recently released) has had a big plugin API redesign (maybe as a result of this blog post?) and now supports this particular use case (and others, of course). I've used it fairly sucessfully on a large project. Not everything is as easy as it could be, but that'll wait for the next world (or maybe nose 1.0 :-) nose 0.10 (recently released) has had a big plugin API redesign (maybe as a result of this blog post?) and now supports this particular use case (and others, of course).

I’ve used it fairly sucessfully on a large project. Not everything is as easy as it could be, but that’ll wait for the next world (or maybe nose 1.0 :-)

]]> Comment on Porting setuptools to py3k by Eduardo Padoan http://oakwinter.com/code/porting-setuptools-to-py3k/#comment-17373 Eduardo Padoan Mon, 23 Jul 2007 23:54:51 +0000 http://oakwinter.com/code/porting-setuptools-to-py3k/#comment-17373 Added a link to this post at: http://wiki.python.org/moin/FutureProofPython Added a link to this post at:
http://wiki.python.org/moin/FutureProofPython

]]> Comment on Introducing context_tools by Kumar McMillan http://oakwinter.com/code/introducing-context_tools/#comment-15137 Kumar McMillan Tue, 26 Jun 2007 15:41:56 +0000 http://oakwinter.com/code/introducing-context_tools/#comment-15137 Hmm, very cool ideas. I posted a more in-depth response here: http://farmdev.com/thoughts/26/context_tools-bridging-the-gap-between-test-methods-and-test-classes-/ Hmm, very cool ideas. I posted a more in-depth response here: http://farmdev.com/thoughts/26/context_tools-bridging-the-gap-between-test-methods-and-test-classes-/

]]> Comment on One step closer… by Brett http://oakwinter.com/code/one-step-closer/#comment-14978 Brett Sun, 24 Jun 2007 20:20:59 +0000 http://oakwinter.com/code/one-step-closer/#comment-14978 Wah. I miss going to Google to work on Google while hanging out with some Googlers while eating some Google on Google, all while using electricity from Google. God I need to graduate. Wah. I miss going to Google to work on Google while hanging out with some Googlers while eating some Google on Google, all while using electricity from Google.

God I need to graduate.

]]> Comment on On Python 3000 whinging by Adam Hupp http://oakwinter.com/code/on-python-3000-whinging/#comment-14896 Adam Hupp Sat, 23 Jun 2007 22:46:45 +0000 http://oakwinter.com/code/on-python-3000-whinging/#comment-14896 > As I asked in response to Martijn’s first > article, have the Jython, IronPython or PyPy > developers even committed to providing > compatibility with Python 3.0? Python 3.0 support is on the Jython roadmap: http://www.jython.org/Project/roadmap.html > As I asked in response to Martijn’s first
> article, have the Jython, IronPython or PyPy > developers even committed to providing
> compatibility with Python 3.0?

Python 3.0 support is on the Jython roadmap:

http://www.jython.org/Project/roadmap.html

]]> Comment on On Python 3000 whinging by Jeff Shell http://oakwinter.com/code/on-python-3000-whinging/#comment-14891 Jeff Shell Sat, 23 Jun 2007 18:25:20 +0000 http://oakwinter.com/code/on-python-3000-whinging/#comment-14891 The Python 3000 concept has been out there for years. 6-8 years, at least. Why are people afraid of it? It it because it has visual progress and plans, unlike Perl 6? If it stayed in the realm of "the mythical Python 3000" then it would be the greatest thing since barbecued pineapple. Python 3000, by my memory, has always been tauted as the version that would not take on backwards compatibility. Sometimes I think that's a worthy sacrifice. The road map has 2.x releases planned out for the next couple of years anyways. I welcome and look forward to Python 3000, even though I have no idea when I'll be able to take proper advantage of it (Zope 3, which I use heavily, has yet to be blessed to even *run* on Python 2.5). The Python 3000 concept has been out there for years. 6-8 years, at least. Why are people afraid of it? It it because it has visual progress and plans, unlike Perl 6? If it stayed in the realm of “the mythical Python 3000″ then it would be the greatest thing since barbecued pineapple.

Python 3000, by my memory, has always been tauted as the version that would not take on backwards compatibility. Sometimes I think that’s a worthy sacrifice. The road map has 2.x releases planned out for the next couple of years anyways.

I welcome and look forward to Python 3000, even though I have no idea when I’ll be able to take proper advantage of it (Zope 3, which I use heavily, has yet to be blessed to even *run* on Python 2.5).

]]> Comment on Subclassing modules in Python by Titus Brown http://oakwinter.com/code/subclassing-modules-in-python/#comment-14878 Titus Brown Sat, 23 Jun 2007 14:32:46 +0000 http://oakwinter.com/code/subclassing-modules-in-python/#comment-14878 I've been looking for ways to do this for a while, and never thought of this elegant trick. Nice! --titus p.s. no, I have no good reason for doing it. does that ever stop anyone? I’ve been looking for ways to do this for a while, and never thought of this elegant trick. Nice!

–titus
p.s. no, I have no good reason for doing it. does that ever stop anyone?

]]> Comment on On Python 3000 whinging by James T http://oakwinter.com/code/on-python-3000-whinging/#comment-14833 James T Sat, 23 Jun 2007 01:45:21 +0000 http://oakwinter.com/code/on-python-3000-whinging/#comment-14833 I am not as worried about moving from one version of Python to to the next as some people seem to be. I was recently working on a project with a code base of about 150,000 lines of Python code. We went from Python 2.2 to 2.3 to 2.4 with almost no glitches. The only time we had a code issue was when a developer used a 2.4 feature before everyone had upgraded from 2.3. We had hundreds of machines on both Windows and UNIX in many locations that we couln't force to upgrade every day. To me, bottom line,2.x are very compatible and I think that 2.6 will translate nicely into 3.x I am not as worried about moving from one version of Python to to the next as some people seem to be. I was recently working on a project with a code base of about 150,000 lines of Python code. We went from Python 2.2 to 2.3 to 2.4 with almost no glitches. The only time we had a code issue was when a developer used a 2.4 feature before everyone had upgraded from 2.3. We had hundreds of machines on both Windows and UNIX in many locations that we couln’t force to upgrade every day. To me, bottom line,2.x are very compatible and I think that 2.6 will translate nicely into 3.x

]]> Comment on On Python 3000 whinging by Paul Boddie http://oakwinter.com/code/on-python-3000-whinging/#comment-14826 Paul Boddie Sat, 23 Jun 2007 00:22:29 +0000 http://oakwinter.com/code/on-python-3000-whinging/#comment-14826 "There are four credible implementations of Python I know of (CPython, Jython, IronPython, PyPy), and we can’t ask each one of these efforts to please please won’t you embed a Python 2 runtime in your system?" As I asked in response to Martijn's first article, have the Jython, IronPython or PyPy developers even committed to providing compatibility with Python 3.0? Or are they holding off on what would be an even bigger trip through the undergrowth than usual? “There are four credible implementations of Python I know of (CPython, Jython, IronPython, PyPy), and we can’t ask each one of these efforts to please please won’t you embed a Python 2 runtime in your system?”

As I asked in response to Martijn’s first article, have the Jython, IronPython or PyPy developers even committed to providing compatibility with Python 3.0? Or are they holding off on what would be an even bigger trip through the undergrowth than usual?

]]>