Someone would have to check, but presumably the CRT on Windows is converting
the natively thread-local locale into a process-wide locale for POSIX
compatibility, which means it can probably be easily bypassed without having to
use specific overloads.
Top-posted from my Windows phone
From: Nath
Nick suggests:
>>> print(f"In European format x is {x:,.2f}, in Indian format it
is {x:,2,3.2f}")
This looks very good and general. I only know of the "European" and South
Asian conventions in widespread use, but we could give other grouping
conventions using that little syntax and it definit
On Sat, Jan 27, 2018, 23:36 Pau Freixes, wrote:
> > At a technical level, the biggest problems relate to the way we
> > manipulate frame objects at runtime, including the fact that we expose
> > those frames programmatically for the benefit of debuggers and other
> > tools.
>
> Shoudnt be somethi
attrs' seems to also not allow mandatory attributes to follow optional one:
In [14]: @attr.s
...: class Baz:
...: a = attr.ib(default=attr.Factory(list))
...: b = attr.ib()
...:
---
ValueError
I think that settles it -- there's no reason to try to implement this.
On Mon, Jan 29, 2018 at 10:51 AM, George Leslie-Waksman
wrote:
> attrs' seems to also not allow mandatory attributes to follow optional one:
>
> In [14]: @attr.s
> ...: class Baz:
> ...: a = attr.ib(default=attr.F
Given I started this thread from a perspective of this is a feature that I
would like because I need it, it feels a little dismissive to take attrs
not having the feature to mean "there's no reason to try to implement this."
On Mon, Jan 29, 2018 at 11:05 AM Guido van Rossum wrote:
> I think that
That's fair. Let me then qualify my statement with "in the initial
release". The initial release has enough functionality to deal with without
considering your rather esoteric use case. (And I consider it esoteric
because attrs has apparently never seen the need to solve it either.) We
can reconsid
On Fri, Jan 26, 2018 at 5:27 PM, Steven D'Aprano
wrote:
> tcl/tk and Javascript only support UCS-2 (16 bit) Unicode strings.
> Dealing with the Supplementary Unicode Planes have the same problems
> that older "narrow" builds of Python sufferred from: single code points
> were counted as len(2) in
Just to add another perspective, I find many "performance" problems in
the real world can often be attributed to factors other than the raw
speed of the CPython interpreter. Yes, I'd love it if the interpreter
were faster, but in my experience a lot of other things dominate. At
least they do prov
On 30 January 2018 at 01:43, David Mertz wrote:
> Nick suggests:
> >>> print(f"In European format x is {x:,.2f}, in Indian format it
> is {x:,2,3.2f}")
>
> This looks very good and general. I only know of the "European" and South
> Asian conventions in widespread use, but we could give other
On 30 January 2018 at 06:54, Chris Barker wrote:
> On Fri, Jan 26, 2018 at 5:27 PM, Steven D'Aprano
> wrote:
>>
>> tcl/tk and Javascript only support UCS-2 (16 bit) Unicode strings.
>> Dealing with the Supplementary Unicode Planes have the same problems
>> that older "narrow" builds of Python suf
On 30 January 2018 at 14:24, Barry Warsaw wrote:
> This is often undervalued, but shouldn't be! Moore's Law doesn't apply
> to humans, and you can't effectively or cost efficiently scale up by
> throwing more bodies at a project. Python is one of the best languages
> (and ecosystems!) that make
12 matches
Mail list logo
