On Tue, Nov 14, 2017, 04:06 Stephan Houben, wrote:
> Hi Brett,
>
> The current documentation *cannot* be fixed, since
> fixing it would entail adding an initial two-page essay
> on "how to start Python on various platforms/systems"
> (it is really NOT as simple as
On Fri, Nov 17, 2017 at 3:15 AM Nick Coghlan wrote:
> On 17 November 2017 at 15:52, Steven D'Aprano wrote:
> > There's a lot of benefit to having a relatively simple, understandable
> > algorithm for determining the MRO, as opposed to some sort of
On Thu, Nov 16, 2017 at 1:11 AM Greg Ewing
wrote:
> Steven D'Aprano wrote:
> > These are not equivalent:
> >
> > B < S, E
> > B < E, S
>
> Not in general, but in many cases they will be, e.g. if
> E and S have no method names in common. I think the OP is
> implying
I find this refactored code intriguing. While I would not suggest changes
to the itertools recipes,
it is a pleasant exercise to think of alternative recipes with an itertools
way.
There are a few third-party libraries dedicated to itertools recipes. For
example, more-itertools
has an
I put the actual space characters here so you can see them
in a non-proportional font (which I assume most Python programmer use).
https://gist.github.com/stephanh42/7c1c122154fd3f26d864233a40d8
The control characters aren't rendered at all (Vim renders them as ^\ ^] ^^
^_,
respectively).
I don't think that we need more than space (U+0020) and Unix newline
(U+000A) ;-)
Victor
2017-11-16 11:23 GMT+01:00 Serhiy Storchaka :
> Currently the re module ignores only 6 ASCII whitespaces in the re.VERBOSE
> mode:
>
> U+0009 CHARACTER TABULATION
> U+000A LINE
On 17/11/2017 09:13, Paul Moore wrote:
> On 17 November 2017 at 01:57, Nick Coghlan wrote:
>> On 17 November 2017 at 05:15, Chris Barker wrote:
>>>
>>> On Wed, Nov 15, 2017 at 11:07 AM, Steve Dower
>>> wrote:
If you
On 17 November 2017 at 01:57, Nick Coghlan wrote:
> On 17 November 2017 at 05:15, Chris Barker wrote:
>>
>> On Wed, Nov 15, 2017 at 11:07 AM, Steve Dower
>> wrote:
>>>
>>> If you write such a PEP, please also research and write
On Fri, Nov 17, 2017 at 10:14 AM, Nick Coghlan wrote:
> On 17 November 2017 at 15:52, Steven D'Aprano wrote:
> > There's a lot of benefit to having a relatively simple, understandable
> > algorithm for determining the MRO, as opposed to some sort of
17.11.17 00:09, MRAB пише:
On 2017-11-16 21:44, Serhiy Storchaka wrote:
16.11.17 19:38, Guido van Rossum пише:
Who would benefit from changing this? Let's not change things just
because we can, or because Perl 6 does it.
I don't know. I know the disadvantages of making this change, and I ask
On 17 November 2017 at 15:52, Steven D'Aprano wrote:
> There's a lot of benefit to having a relatively simple, understandable
> algorithm for determining the MRO, as opposed to some sort of adaptive
> rule that will try to reorder classes according to potentially clashing
>
11 matches
Mail list logo