I think this particular mess was caused by the hiding of
“DeprecationWarning”s by default: If you don’t see any warnings cropping up
in your production code, you don’t know you have to fix something.
Some languages handle it like this:
1. Silent deprecation warning (deprecated in docs and/or h
Hi Guido,
As far as I can see, the general consensus seems to be to turn them back on
in general: The last person to argue against it was Paul Moore, and he
since said:
“OK, I overstated [that you’re ‘hosed’ by DeprecationWarnings appearing].
Apologies. My recollection is of a lot more end user c
Nick Coghlan schrieb am Di., 7. Nov. 2017 um 14:57 Uhr:
> Users of applications written in Python are not python-dev's users:
> they're the users of those applications, and hence the quality of that
> experience is up to the developers of those applications. […]
>
Thank you, that’s exactly what
Sorry, I still don’t understand how any of this is a problem.
1. If you’re an application developer, google “python disable
DeprecationWarning” and paste the code you found, so your users don’t see
the warnings.
2. If you’re a library developer, and a library you depend on raises
De
Hi! Just this minute I ran across a case where I’d want DeprecationWarnings
on by default
(We want to rename a property in an API I’m co-developing. I has mainly
scientists as target audience, so end users, not developers)
Gustavo Carneiro schrieb am Mo., 6. Nov. 2017 um
15:19 Uhr:
> Big +1 to
Paul Moore schrieb am Sa., 10. Dez. 2016 um 11:38 Uhr:
> Someone has raised an issue against the project at
> https://github.com/naftaliharris/python2.8/issues/47 We should
> probably see what the project owner's response to that is.
>
That would be me, hi.
I really hope this is resolved in a c
Brett Cannon schrieb am Mi., 17. Aug. 2016 um 19:15 Uhr:
> Please don't cross-post as it means anyone replying to your email will now
> split the conversation as not everyone will be subscribed to all of the
> mailing lists you sent this to. I have stripped out all but python-dev for
> my reply.
hi, i already posted in python-ideas, but i got no replies, so i’ll post
here:
in essence i think interpreting escape sequences in f-literals is a *very*
bad idea, mainly because i think it’s fundamental that syntax highlighters
can highlight code as code.
so they should highlight the code parts
hi devs,
just an idea that popped up in my mind: re.findall() returns a list of
tuples, where every entry of each tuple represents a match group.
since match groups can be named, we are able to use named tuples instead of
plain tuples here, in the same fashion as namedtuple’s rename works:
misssin
