> On Feb 12, 2015, at 18:40, Chris Angelico wrote:
>
> On Fri, Feb 13, 2015 at 12:46 PM, MRAB wrote:
> class BaseInt:
>> ... def __init__(self, value):
>> ... self._value = value
>> ... def __add__(self, other):
>> ... return type(self)(self._value + other)
>
>> O
it down a notch.
>
> On Tue Dec 16 2014 at 1:48:59 PM Mark Roberts wrote:
>
>> On Tue, Dec 16, 2014 at 2:45 AM, Antoine Pitrou
>> wrote:
>>>
>>> Iterating accross a dictionary doesn't need compatibility shims. It's
>>> dead simple in all P
On Tue, Dec 16, 2014 at 2:45 AM, Antoine Pitrou wrote:
>
> Iterating accross a dictionary doesn't need compatibility shims. It's
> dead simple in all Python versions:
>
> $ python2
> Python 2.7.8 (default, Oct 20 2014, 15:05:19)
> [GCC 4.9.1] on linux2
> Type "help", "copyright", "credits" or "lic
On Mon, Dec 15, 2014 at 11:30 AM, Chris Barker
wrote:
> Are you primarily writing packages for others to use? if so, then yes. But
> I wonder how many people are in that camp? Don't most of us spend most of
> our time writing our own purpose-built code?
>
> That might be a nice thing to see in a
the Python3 zealots are giving it credit for. Please
don't claim it's "easy" to move over just because merely most of the top 20
libraries have been moved over. :-/
-Mark
On Thu, Dec 11, 2014 at 12:14 PM, Dan Stromberg wrote:
> On Thu, Dec 11, 2014 at 11:35 AM, Mark Roberts
I disagree. I know there's a huge focus on The Big Libraries (and wholesale
migration is all but impossible without them), but the long tail of
libraries is still incredibly important. It's like saying that migrating
the top 10 Perl libraries to Perl 6 would allow people to completely ignore
all of
I find it handy to use named tuple as my database mapping type. It allows you
to perform this behavior seamlessly.
-Mark
> On Jul 13, 2014, at 7:04, "Jason R. Coombs" wrote:
>
> I repeatedly run into situations where a frozendict would be useful, and
> every time I do, I go searching and fin
That's fantastic! Great job - that's a lot of work :)
-Mark
> On Jun 20, 2014, at 13:32, Philip Jenvey wrote:
>
> =
> PyPy3 2.3.1 - Fulcrum
> =
>
> We're pleased to announce the first stable release of PyPy3. PyPy3
> targets Python 3 (3.2.5) compatibilit
On Thu, May 29, 2014 at 9:30 AM, Terry Reedy wrote:
> On 5/28/2014 6:26 PM, Glyph Lefkowitz wrote:
>
> I hope it's
>> not controversial to say that most new Python code is still being
>> written against Python 2.7 today;
>>
>
> Given that Python 3 downloads now outnumber Python 2 downloads, I th
Hmm,
I have not viewed the patch in question, but I'm curious why we wouldn't want
to include such a patch if it were transparent to the user (Python based or
otherwise). Especially if it increased performance without sacrificing
maintainability or elegance. Further considering the common usa
10 matches
Mail list logo
