On 05/10/2017 05:50 PM, Steven D'Aprano wrote:
On Tue, May 09, 2017 at 10:05:43AM -0700, Ethan Furman wrote:
A comment on a recent SO answer [1] wondered why my aenum library wasn't
mentioned in the docs to help guide people that needed/wanted more advanced
Enum options to it.
I know that th
On Tue, May 09, 2017 at 11:54:26PM +0400, Abdur-Rahmaan Janhangeer wrote:
> I'm really new to the mailing list. Can someone just summarise the
> preceding message in 5 to 10 lines like what it is, what type is it or when
> does it happen
It is an update to PEP 484, adding support for type-checking
On Tue, May 09, 2017 at 10:05:43AM -0700, Ethan Furman wrote:
> A comment on a recent SO answer [1] wondered why my aenum library wasn't
> mentioned in the docs to help guide people that needed/wanted more advanced
> Enum options to it.
I know that the std lib is where good modules go to die :-
On 05/10/2017 07:53 AM, Ethan Furman wrote:
Why is python-list the place to send behavioral bugs to? It's been my
experience that folks there will (rightly) ask
the individual to file a bug on the tracker.
Thank you for the abundance of answers. I am now totally on-board with such "bug
rep
On 10/05/2017 15:53, Ethan Furman wrote:
Not sure where to ask about this, so I'm asking here.
In the on-line docs, at the very bottom of a page, in fine print, is a
link: _Find a bug?_ Following that link leads to a short page with some
advice on how to handle it. Under the second heading [
On 5/10/2017 10:59 AM, Chris Angelico wrote:
On Thu, May 11, 2017 at 12:53 AM, Ethan Furman wrote:
Why is python-list the place to send behavioral bugs to?
Where else? The people who would follow that advice are generally not
registered on bpo and have no interest in the hassle of becoming
Presumably so newbies can get help on common issues that aren't bugs, or
guidance on how to file a good bug report. Or search the tracker for
duplicates, or to upgrade to a newer version.
On May 10, 2017 7:58 AM, "Ethan Furman" wrote:
> Not sure where to ask about this, so I'm asking here.
>
> I
On Thu, May 11, 2017 at 12:53 AM, Ethan Furman wrote:
> Why is python-list the place to send behavioral bugs to? It's been my
> experience that folks there will (rightly) ask the individual to file a bug
> on the tracker.
>
How many bug tracker entries do you want to see about mutable default
ar
Not sure where to ask about this, so I'm asking here.
In the on-line docs, at the very bottom of a page, in fine print, is a link: _Find a bug?_ Following that link leads to
a short page with some advice on how to handle it. Under the second heading [1] is this paragraph:
If you’re short on
Being the one who left the comment, I'm all for adding it.
The reason I wondered why it was not there was because I was aware you are
the author of both so, I believe, the con of it being a 3rd party library
is minimized. I've also seen plenty of people asking around for more
advanced usages of En
I think you're right that the redefinition style is easier to read for
complicated stuff... It also seems more complicated in a way I can't put my
finger on.
The overload precedent helps.
Currently leaning towards Jukka being right, vague worries about extra
complication be damned.
Readabi
Even if Callable types will soon support keyword arguments, the syntax for
Callables will look quite different from function definitions and this
inconsistency may hurt readability, at least for more complex signatures.
We could work around this by using the def syntax for the declared type of
a de
There is a discrepancy now between PEP 484 and PEP 526:
def f(x: int = None): ... # OK
x: int = None # Error
I think the two rules should be "in sync", in view of this I agree with the
proposal.
Concerning verbosity and a long name Optional there are many reasonable
workarounds.
One is alrea
13 matches
Mail list logo
