On 17. 11. 21 23:47, Barry Warsaw wrote:
Hello Mark, Matthew, Pradeep, Vincent, and Guido,
The Python Steering Council discussed the latest version of PEP 646 (Variadic
Generics) at our last meeting, and have unanimously decided to accept the PEP.
Congratulations!
We want to specifically
First note:
Python itself does not enforce that annotations be type objects. So for
your system, you are free to use (a,b) if you like. (As long as a and b are
defined.
Of course, then your code wouldn’t work with static type checkers.
But the trick is that annotations are Python, and (a,b) is
Am 18.01.22 um 22:57 schrieb Victor Stinner:
At the end of my first email, I also suggest thinking about
incompatible changes differently, try to make affected projects
compatible in advance. The problem are not the changes themselves, but
how they are introduced in Python, and more globally how
Fantastic, Petr! Thanks for letting us know - and thank you once again for
your patience with our last-minute changes! We'll go ahead and mark the PEP
as accepted, and merge our CPython implementation soon.
On Wed, 19 Jan 2022 at 08:34, Petr Viktorin wrote:
> On 17. 11. 21 23:47, Barry Warsaw
On Wed, Jan 19, 2022 at 11:58 AM Sebastian Rittau wrote:
>
> Am 18.01.22 um 22:57 schrieb Victor Stinner:
> > At the end of my first email, I also suggest thinking about
> > incompatible changes differently, try to make affected projects
> > compatible in advance. The problem are not the changes
> On 18 Jan 2022, at 19:59, Pablo Galindo Salgado wrote:
>
> We considered using colours and other markers such as bold text, but that
> opens a considerable can of worms with detecting in all systems and
> configurations if that can be done. I have been told that some of these
> situations
On Mon, Jan 17, 2022 at 7:02 AM Jelle Zijlstra
wrote:
>
>
> El lun, 17 ene 2022 a las 6:25, Petr Viktorin ()
> escribió:
>
>> On Wed, Nov 17, 2021 at 8:31 AM Pradeep Kumar Srinivasan
>> wrote:
>> >
>> > This PEP [1] introduces a simple and intuitive way to annotate methods
>> and classmethods
> On 19 Jan 2022, at 21:19, Ethan Furman wrote:
>
> On 1/19/22 1:10 PM, Barry Scott wrote:
> > On 18 Jan 2022, at 19:59, Pablo Galindo Salgado wrote:
>
> >> We considered using colours and other markers such as bold text, but that
> >> opens a considerable can of worms with
> >> detecting
> On 19 Jan 2022, at 21:19, Ethan Furman wrote:
>
> An environment variable would solve this, yes? The default would be using
> the underlining carets, but an env var could switch that to using color
> instead.
Oh and if you use colours then you please give me the ability to set the
On 1/19/22 1:10 PM, Barry Scott wrote:
> On 18 Jan 2022, at 19:59, Pablo Galindo Salgado wrote:
>> We considered using colours and other markers such as bold text, but that
opens a considerable can of worms with
>> detecting in all systems and configurations if that can be done. I have been
On 1/19/2022 5:01 PM, Barry Scott wrote:
Oh and if you use colours then you please give me the ability to set the
colours for each usage.
IDLE has that for Error Text, along with other colors.
I have custom colour settings for a lots of unix too ls so that I get
contrast etc.
The defaults
>
> It would not be nice if the traceback module API started providing
> text with embedded escape sequences without a way to turn then off in the
> API.
>
I think fobj.isatty() would give the traceback module a good idea whether
it's writing to a display device or not. There are a number of
12 matches
Mail list logo
