On Sep 27, 2011 5:56 PM, wrote:
>
>
> assertNotRaises doesn't make anything possible that isn't possible now. It
probably doesn't even make anything easier - but if it does, it's so obscure
(and I've read and written thousands of tests for all kinds of libraries
over the years) that it doesn't mer
I as well think the construct should support other types as it sounds an
awful lot like the missing for(;;) loop construct.
Concerning the api, if we use spread(start, step, count) we don't rely on a
division method even though the caller probably does. Just mentioning
another option.
--
Could you elaborate on what would be wrong if function definitions ended
only after an explicitly less indented line? The only problem that comes to
mind is global scope "if" statements that wouldn't execute when expected (we
actually might need to terminate them with a dedented "pass").
On Sep 24,
I agree that it should and it doesn't. I also recall that not having empty
lines between function/class definitions can cause indentation errors when
pasting to the console on my windows machine.
--Yuval
On Sep 23, 2011 7:26 PM, "anatoly techtonik" wrote:
> Currently if you work in console and de
+2 for promoting naming consistency and putting metadata where it's supposed
to be.
--Yuval
On Sep 15, 2011 9:23 AM, "Éric Araujo" wrote:
> Le 13/09/2011 18:34, Michael Foord a écrit :
>> On 13/09/2011 16:57, Éric Araujo wrote:
>>> (IIRC PyPI will require us to play games to have both
>>> 2.x and
On Fri, Nov 13, 2009 at 9:35 AM, Kevin Teague wrote:
>
> It's also worth noting that there are three issues with respect to standard
> library packaging which are all orthologous:
>
> * Packaging for metadata: The standard library could be packaged so that
> there is consistent metadata about the
