On 9 May 2017 at 13:44, Nick Coghlan wrote:
> On 8 May 2017 at 15:34, Nick Coghlan wrote:
>> On 7 May 2017 at 15:22, INADA Naoki wrote:
>>> ## Background
>>>
>>> Locale coercion in current PEP 538 has some downsides:
>>>
>>> * If user set `LANG=C LC_DATE=ja_JP.UTF-8`, locale coercion may
>>> o
2017-05-04 19:51 GMT+02:00 Raymond Hettinger :
> Yes. It is perfectly reasonable to backport improvements to the tooling as
> long as it doesn't break anyone's existing build process.
I pushed my change to 2.7, 3.5, 3.6 and master (3.7) branches: "make"
doesn't try to regenerate generated files
Hi folks,
Enough changes have accumulated in PEP 538 since the start of the
previous thread that it seems sensible to me to start a new thread
specifically covering the current design (which aims to address all
the concerns raised in the previous thread).
I haven't requoted the PEP in full since
On Tue, May 9, 2017 at 5:20 AM, Victor Stinner wrote:
> This change broke the Coverage job on Travis CI, because sysconfig.py
> uses get_config_var('AST_H_DIR') to build sysconfig.get_python_inc():
> http://bugs.python.org/issue30273
>
> sysconfig was modified in 2012. "Include" was replaced with
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 responded that Python was not in the habit of mentioning third-party
libraries in the docs.
However, I thought I would doub
There's a PR to the peps proposal here:
https://github.com/python/peps/pull/242
The full text of the current proposal is below. The motivation for this is
that for complex decorators, even if the type checker can figure out what's
going on (by taking the signature of the decorator into account), i
There's a proposal to change one detail of PEP 484. It currently says:
An optional type is also automatically assumed when the default value is
None, for example::
def handle_employee(e: Employee = None): ...
This is equivalent to::
def handle_employee(e: Optional[Employee] = None) -> None:
On 09/05/2017 18:05, 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 responded that Python was not in the
habit of mentioning third-party libraries in
On 05/09/2017 10:28 AM, Guido van Rossum wrote:
> There's a proposal to change one detail of PEP 484. It currently says:
>
> An optional type is also automatically assumed when the default value is
> |None|, for example::
>
> |def handle_employee(e: Employee = None): ... |
>
> Th
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
Thanks for all,
Abdur-Rahmaan Janhangeer
Vacoas,
Mauritius
https://abdurrahmaanjanhangeer.wordpress.com/
__
On Tue, 9 May 2017 at 10:59 Mark Lawrence via Python-Dev <
python-dev@python.org> wrote:
> On 09/05/2017 18:05, 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
On Tue, 9 May 2017 at 11:11 Carl Meyer wrote:
> On 05/09/2017 10:28 AM, Guido van Rossum wrote:
> > There's a proposal to change one detail of PEP 484. It currently says:
> >
> > An optional type is also automatically assumed when the default
> value is
> > |None|, for example::
> >
> >
The idea seems reasonable to me when viewing type hints as a form of
documentation as it helps remind people how they are expected to call the
final function.
One worry I do have, though, is Callable doesn't support keyword-only
parameters, so declared_type won't work in all cases without Callable
Stay tuned for the pep that allows callable to take keyword args.
> On May 9, 2017, at 3:59 PM, Brett Cannon wrote:
>
> The idea seems reasonable to me when viewing type hints as a form of
> documentation as it helps remind people how they are expected to call the
> final function.
>
> One w
On 10 May 2017 at 08:51, Brett Cannon wrote:
> On Tue, 9 May 2017 at 11:11 Carl Meyer wrote:
>> It might be nice to have a less verbose syntax for Optional, but that
>> can be a separate discussion.
>
> You should be able to do that today with `from typing import Optional as Eh`
> or whatever you
On Tue, May 9, 2017 at 7:37 PM, Nick Coghlan wrote:
> On 10 May 2017 at 08:51, Brett Cannon wrote:
> > On Tue, 9 May 2017 at 11:11 Carl Meyer wrote:
> >> It might be nice to have a less verbose syntax for Optional, but that
> >> can be a separate discussion.
> >
> > You should be able to do tha
On 9 May 2017 at 21:57, Nick Coghlan wrote:
> The essential related changes to the reference implementation can be seen
> here:
>
> * Always set "surrogateescape" for coercion target locales,
> independently of whether or not coercion occurred:
> https://github.com/ncoghlan/cpython/commit/188e780
17 matches
Mail list logo
