On 09/11/2016 01:55 AM, Victor Stinner wrote:
2016-09-10 3:49 GMT-04:00 Ethan Furman wrote:
With __definition_order__ Enum can display the actual creation order of enum
members and methods, while relying on Enum.__dict__.keys() presents a
jumbled mess with many attributes the user never wrote
On 09/12/2016 09:27 AM, Gregory P. Smith wrote:
For the regular dict (non kwargs or namespace __dict__) use case I would
actually like to /see disorder preserved during iteration/.
If we don't, we will eventually to find ourselves in a similar state we were in
pre hash-randomization:
Does a
On 09/15/2016 08:02 AM, Raymond Hettinger wrote:
Eric is correct on this one. The consecutive hashes make a huge difference for
Python 3.5. While there is a table full table scan, the check for NULL
entries becomes a predictable branch when all the keys are in consecutive
positions. Ther
On 10/20/2016 03:56 AM, Victor Stinner wrote:
Last months, I worked a lot on benchmarks. I ran benchmarks, analyzed
results in depth (up to the hardware and kernel drivers!), I wrote new
tools and enhanced existing tools.
Thank you!
--
~Ethan~
___
P
On 12/16/2016 11:24 AM, Guido van Rossum wrote:
I am beginning to think that `from __future__ import unicode_literals` does
more harm than good. I don't recall exactly why we introduced it, but with
the restoration of u"" literals in Python 3.3 we have a much better story
for writing straddli
On 12/26/2016 08:46 PM, Glenn Linderman wrote:
So either Google (my email host) noticed that I got 3 of the same message,
and suppressed two of them, or the python-dev mail server that hosts the
mailing lists merged the expanded destinations with duplicate suppression.
I'm inclined to think t
On 01/09/2017 03:42 AM, Steve Holden wrote:
When I asked him why he suggested
a) this would improve encapsulation, and
b) the practice was supported in the stdlib.
Further investigation reveals that some modules (e.g. argparse, crypt,
difflib, random) do use this technique, but it is far fro
Question: I need to add a threaded test to the enum test module [1] -- is
there anything extra I
need to worry about besides the test itself? Setting or resetting or using a
tool library, etc?
--
~Ethan~
[1] The test to be added:
def test_unique_composite(self):
# override __eq
On 01/22/2017 11:48 AM, Serhiy Storchaka wrote:
On 25.10.16 12:37, Serhiy Storchaka wrote:
Classes that doesn't define the __format__ method for custom PEP 3101
formatting inherits it from parents.
Originally the object.__format__ method was designed as [1]:
def __format__(self, format_spe
On 01/22/2017 12:02 PM, Ethan Furman wrote:
Question: I need to add a threaded test to the enum test module [1] -- is
there anything extra I
need to worry about besides the test itself? Setting or resetting or using a
tool library, etc?
Thanks everyone.
@support.reap_threads and skipping
On 02/28/2017 09:42 PM, Nick Coghlan wrote:
So would folks be OK with my asking the author of the PR for
https://bugs.python.org/issue29679 (adding
asynccontextmanager) to rewrite the patch to add it as
asyncio.contextlib.asyncontextmanager (with a cross-reference
from the synchronous contextl
There are a few modules that have had their constants redefined as Enums, such
as signal, which has revealed a minor nit:
>>> pp(list(signal.Signals))
[,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
]
The resulting enumeration is neither in alpha no
I strongly prefer numeric order for signals.
--Guido (mobile)
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.c
On 03/03/2017 02:35 AM, Guyzmo wrote:
On Thu, Mar 02, 2017 at 04:13:17PM -0800, Ethan Furman wrote:
The resulting enumeration is neither in alpha nor value order. While this
has no bearing on programmatic usage I would like these Enums to be ordered,
preferably by value.
Would anyone prefer
On 03/07/2017 09:41 AM, Brett Cannon wrote:
I don't think a common practice has bubbled up yet for when there's both
synchronous and asynchronous versions of an API
(closest I have seen is appending an "a" to the async version but that just
looks like a spelling mistake to me most of
the time)
Just want to drop a note and say THANK YOU to everyone for the work in
improving Python to the 3 branch.
And if you're curious as to why: I just spent three hours trying to figure out why my comparisons were succeeding when
they should be raising exceptions -- and then remembered that in 2.x t
Apparently the Windows installer mentions asking for help on Python List.
If accessing Python List directly via email it is necessary to subscribe first -- perhaps that could be mentioned?
Bonus Python Points for mentioning the other methods that do not require subscribing. :)
Rejection text
On 05/01/2017 08:47 PM, Jason Maldonis wrote:
If this should be asked in learn python I apologize -- please just tell me
without answering.
If you could re-ask this question over on Python List I'd love to discuss which errors you are seeing from
__getattribute__ (beside AttributeError, of c
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
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
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
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
On 05/27/2017 11:46 PM, INADA Naoki wrote:
Now I approve the PEP 538.
Thank you, Nick and Inada-san!
--
~Ethan~
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.
if (PyErr_WarnFormat(PyExc_DeprecationWarning, 1,
"invalid escape sequence '\\%c'",
*first_invalid_escape) < 0) {
Py_DECREF(result);
return NULL;
}
What other core developers think about this?
On 06/06/2017 05:30 PM, Barry Warsaw wrote:
On Jun 05, 2017, at 08:19 AM, Ethan Furman wrote:
I would format that as:
if (PyErr_WarnFormat(
PyExc_DeprecationWarning,
1,
"invalid escape sequence
On 06/12/2017 05:24 AM, Nick Coghlan wrote:
I suspect the eventual outcome is going to be dropping that particular
warning (since it's been problematic for Fedora's 3.6 backport as
well, and the problems are due to the warning itself, *not* the locale
coercion), but I'd prefer to keep the notifi
On 07/17/2017 02:26 PM, Barry Warsaw wrote:
namedtuple is great and clever, but it’s also a bit clunky. It has a weird
> signature and requires a made up type name. It’s also rather unPythonic if
> you want to support default arguments when creating namedtuple instances.
> Maybe as you say, a
On 07/17/2017 02:31 PM, Brett Cannon wrote:
I vaguely remember some years ago someone proposing a patch that used
metaclasses to avoid using exec() (I think it was
to benefit PyPy or one of the JIT-backed interpreters). Would that work to
remove the need for exec() while keeping the
code in pu
On 07/17/2017 03:27 PM, Greg Ewing wrote:
Barry Warsaw wrote:
namedtuple is great and clever, but it’s also a bit clunky. It has a weird
signature and requires a made up type name.
Maybe a metaclass could be used to make something
like this possible:
class Foo(NamedTuple, fields = 'x,
On 07/17/2017 04:45 PM, Guido van Rossum wrote:
Raymond agreed to reopen the issue. Everyone who's eager to redesign
namedtuple, please go to python-ideas.
Python Ideas thread started.
--
~Ethan~
___
Python-Dev mailing list
Python-Dev@python.org
ht
CPython in particular
and
> the perception of Python’s applicability to many problems. I think we’re
better
> off trying to identify and address such problems than ignoring or minimizing
them.
Ethan Furman:
Speed is not the only factor, and certainly shouldn't be the first concer
On 07/18/2017 08:12 AM, Guido van Rossum wrote:
There are some weighty things being said in this subthread that shouldn't be
hidden under the heading of improving
NamedTuple. For continued discussion of our development philosophy let's open a
new thread. (I have an opinion but I
expect I'm not
On 07/18/2017 09:16 AM, Antoine Pitrou wrote:
On Tue, 18 Jul 2017 09:08:08 -0700
Ethan Furman wrote:
Nick Coughlan:
-
It is "Nick Coghlan" not "Coughlan".
Argh. Sorry, Nick, and thank you, Antoine!
As another example of this: while trading the global
On 08/19/2017 01:40 AM, Antoine Pitrou wrote:
On Fri, 18 Aug 2017 16:33:27 -0400 Yury Selivanov wrote:
There are a few open questions left, namely the terminology
and design of ContextKey API. On the former topic, I'm quite
happy with the latest version: Execution Context, Logical
Context, an
On 08/19/2017 10:41 PM, Nick Coghlan wrote:
On 20 August 2017 at 10:21, Guido van Rossum wrote:
The way we came to "logical context" was via "logical thread (of control)",
which is distinct from OS thread. But I think we might need to search for
another term...
Right. Framing it in pragmatic
On 08/21/2017 04:43 AM, Antoine Pitrou wrote:
On Mon, 21 Aug 2017 01:45:05 -0400
"Jim J. Jewett" wrote:
Building on Brett's suggestion:
FrameContext: used in/writable by one frame
It's not frame-specific, it's actually shared by an arbitrary number of
frames (by default, all frames in a
On 08/23/2017 11:27 AM, Yury Selivanov wrote:
Out of what was proposed so far to replace Logical Context:
[...]
I don't think that replacing LogicalContext with any name in this list
will make any improvement.
How about ExecutionContext and ContextVars ?
We are already used to different lev
On 08/23/2017 12:17 PM, Yury Selivanov wrote:
How about ExecutionContext and ContextVars ?
We are already used to different levels of variables: global, local, non-local,
class. I think having variables tied to a Context, and having search flow back
to previous Contexts, would be easy to un
On 08/24/2017 06:52 AM, Barry Warsaw wrote:
To me, the functionality proposed in PEP 550 feels more like a "scope"
than a "context". Unlike a lexical scope, it can't be inferred from the
layout of the source code. It's more of a dynamic "execution scope" and
the stacking of "local execution sc
All in all, I like it. Nice job.
On 08/25/2017 03:32 PM, Yury Selivanov wrote:
A *context variable* is an object representing a value in the
execution context. A new context variable is created by calling
the ``new_context_var()`` function. A context variable object has
two methods:
* ``loo
On 08/26/2017 09:25 AM, Yury Selivanov wrote:
On Fri, Aug 25, 2017 at 10:19 PM, Ethan Furman wrote:
A *context variable* is an object representing a value in the
execution context. A new context variable is created by calling
the ``new_context_var()`` function. A context variable object has
On 08/26/2017 12:12 PM, David Mertz wrote:
I'm convinced by the new section explaining why a single value is better than a
namespace. Nonetheless, it would feel
more "Pythonic" to me to create a property `ContextVariable.val` whose getter
and setter was `.lookup()` and `.set()`
(or maybe `._lo
On 08/27/2017 11:02 AM, Chris Jerdonek wrote:
Hi Jim, it seems like each time you reply you change the subject line and start
a new thread. Very few others are doing
this (e.g. Yury when releasing a new version). Would it be possible for you to
preserve the threading like others?
I must admi
On 08/28/2017 04:19 AM, Stefan Krah wrote:
What about this?
async def bar():
setcontext(Context(prec=1))
for i in range(10):
await asyncio.sleep(1)
yield i
async def foo():
async for i in bar():
# ctx.prec=1?
print(Decimal(100) / 3)
If I und
On 08/28/2017 09:12 AM, Yury Selivanov wrote:
If we forget about dynamic scoping (I don't know why it's being brought up all
the
time, TBH; nobody uses it, almost no language implements it)
Probably because it's not lexical scoping, and possibly because it's possible for a function to be runn
On 10/23/21 8:01 PM, edivmanci...@gmail.com wrote:
> I'm starting now to program with kwant and I'm having problems like:
Sorry, you've reached the wrong list -- this one is for the development of
Python itself.
For general help using Python, subscribe to
python-l...@python.org
which you
: Ethan Furman
Discussions-To: python-dev@python.org
Status: Draft
Type: Informational
Content-Type: text/x-rst
Created: 23-Feb-2013
Python-Version: 3.11
Post-History: 20-Jul-2021, 02-Nov-2021
Resolution:
Abstract
Update the ``repr()``, ``str()``, and ``format()`` of the various Enum
ar).encode('ascii').
The rendered version is at https://www.python.org/dev/peps/pep-0467/
Happy reading!
PEP: 467
Title: Minor API improvements for binary sequences
Version: $Revision$
Last-Modified: $Date$
Author: Nick Coghlan , Ethan Furman
Status: Draft
Type: Standards Track
Cont
On 11/4/21 12:21 PM, Brett Cannon wrote:
> What notification? (I fully admit I may not have gotten one due to some team
I'm in, but I have
> no such notification if it happened recently.)
I've received 20-30 in the last three or four days. I'm not concerned about
it, just providing a data poi
On 11/8/21 4:45 AM, Victor Stinner wrote:
> Is it implement "like" ascii(obj).encode("ascii") but with minor
> changes? What changes?
It works like `str()`, but you get ascii-encoded bytes (or an exception if
that's not possible).
The difference with the built-in ascii is the absence of extra
When is an empty container contained by a non-empty container?
For example:
{} in {1:'a', 'b':2] <-- TypeError because of hashability
set() in {1, 2, 'a', 'b'} <-- ditto
[] in ['a', 'b', 1, 2] <-- False
'' in 'a1b2' <-- True
SomeFlag.nothing in SomeFlag.something <-- ???
Personally,
Let's use a concrete example: `re.RegexFlag`
```
Help on function match in module re:
match(pattern, string, flags=0)
Try to apply the pattern at the start of the string, returning
a Match object, or None if no match was found.
```
In use we have:
result = re.match('present', 'who
gs are iterable -- `list(F1) == [F1]; list(F1 | F2) == [F1, F2]`
- iterating over a Flag only returns the "pure" (aka single-bit) flags, even if
multi-flag instances
have been created (at least, they will in 3.11)
On 11/8/21 8:32 PM, Guido van Rossum wrote:
> On Mon, Nov 8, 2021
On 11/8/21 3:09 PM, Steven D'Aprano wrote:
> On Mon, Nov 08, 2021 at 01:43:03PM -0800, Ethan Furman wrote:
>> SomeFlag.nothing in SomeFlag.something <-- ???
>
> I don't think that consistency with other containers is particularly
> relevant here. More useful
On 11/9/21 9:02 AM, Guido van Rossum wrote:
> On Mon, Nov 8, 2021 at 10:29 PM Ethan Furman wrote:
>> The way I see it, the following should hold
>>
>> empty_flag = RegexFlag(0)
>> any_case = RegexFlag.IGNORECASE
>> any_case_o
On 11/11/21 11:53 AM, Matt del Valle wrote:
> Okay, so from the replies so far it looks like this is very quickly going
into the 'never gonna happen'
> dumpster, so in the interests of salvaging *something* out of it:
[...]
> I just dislike having to settle for 'it's what we've got'. With thes
Woops, wrong list -- please disregard.
--
~Ethan~
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https:/
Sorry for the spam -- one of us must have clicked on the wrong button. :-/
--
~Ethan~
Moderator
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/pyth
On 11/26/21 1:13 AM, Paul Moore wrote:
> On Fri, 26 Nov 2021 at 05:14, Guido van Rossum wrote:
>>
>> My memory is also hazy, but I'm quite sure that *in my mind* annotations were
>> intended as a compromise between conflicting proposals for *typing*. We
didn't
>> have agreement on the syntax or s
I ran into an issue today with `str()` not behaving as I thought it should.
Given the following test script, what should happen?
-- 8< --
class Blah(object):
def __str__(self):
return 'blah'
class Huh(int, Blah):
pass
class Hah(Blah, int):
pass
On 12/12/21 10:43 PM, Vioshim wrote:
> Anyways, at the moment that I write this message in python3.10.1, It happens that when making a class with the
dataclasses module, this class can't actually be used in Multiple inheritance for Enum purposes, this is mostly to avoid
code repetition by havin
On 12/13/21 3:34 PM, Steven D'Aprano wrote:
> I think this may be what you are looking for:
[...]
Beat me to it. :-)
--
~Ethan~
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://
Hello!
The python-dev list is for developing the next version of Python. For help
using Python, please send your question to
python-l...@python.org
Thanks, and good luck!
--
~Ethan~
___
Python-Dev mailing list -- python-dev@python.org
To unsubscr
On 1/8/22 5:46 PM, Steven D'Aprano wrote:
> [...] if you hate type annotations because they are unreadable, then you
> hate Python because Python is unreadable.
Not so. A simple list comprehension is (usually) quite readable, while a triply-nested list comprehension all on one
line is not.
S
On 1/18/22 10:43 AM, Mats Wichmann wrote:
> A thought - how about omitting the underline line if the
> to-be-underlined part would be the whole line?
I would also like that change -- when the underlining is a portion of the whole it's quite useful, but when it's the
whole line it's a lot of ext
On 1/18/22 11:59 AM, 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 are
> quite tric
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
tol
On 1/29/22 3:14 AM, Lrupert via Python-Dev wrote:
> As someone who is watching the python/cpython repository, I'm very used to
see lots of traffic. But
> lately there have been a surge of spammy PRs which are about the same,
generally very trivial subject
> but individually fixing each occurren
On 1/31/22 8:47 AM, Lrupert via Python-Dev wrote:
> This gives a bad impression to others about their intentions (constant
contribution of trivial
> / low quality stuff with little-to-no-gain to achieve a higher number of
commits, since it is
> a visible metric).
Two of us have already comment
On 2/4/22 6:23 AM, Stefan Behnel wrote:
> One recent example is the new error locations in tracebacks, where PEP 657
explicitly lists
> the new "co_positions" field in code objects as an implementation detail of
CPython. If we
> want to implement this in Cython, then there is no other way than
On 2/6/22 6:08 AM, Victor Stinner wrote:
> I propose to deprecate the urllib module in Python 3.11. It would emit
> a DeprecationWarning which warn users, so users should consider better
> alternatives like urllib3 or httpx: well known modules, better
> maintained, more secure, support HTTP/2 (ht
On 2/9/22 6:59 AM, Barney Gale wrote:
> Over the last couple of years I've been tidying up the pathlib internals,
with a view
> towards adding an AbstractPath class to the hierarchy. Users would be able to
subclass
> AbstractPath to implement other kinds of filesystems: s3, google cloud
storag
On 2/9/22 8:40 AM, Pablo Galindo Salgado wrote:
> Petr Viktorin wrote:
>> Should there be a getter/setter for co_positions?
>
> We consider the representation of co_postions private, so we don't want (for
now) to ad
> getters/setters.
Isn't the whole point of getters/setters is to allow public
On 2/10/22 1:45 PM, Brett Cannon wrote:
> Protocols would let folks rely on a common Path object API w/o having to
require the object
> come from pathlib itself or explicitly subclass something (which I admit
would be rare, but
> there's no reason to artificially constrain this either). Now may
https://arstechnica.com/information-technology/2022/03/linux-has-been-bitten-by-its-most-high-severity-vulnerability-in-years/
--
~Ethan~
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
ht
On 3/13/22 14:49, joao.p.f.batista...@gmail.com wrote:
> Currently:
> l = [] # new empty list
> t = () # new empty tuple
> s = set() # new empty set (no clean and consistent way of initializing regarding the
others) <<<
> d = {} # new empty dictionary
>
> Possible solution:
> s = {} # new empty
[apologies for the late post, just found this in my drafts folder]
On 2/7/22 12:49 AM, Stéfane Fermigier wrote:
3. Overall, I think the days where "battery included" was a positive argument
are over
I strongly disagree. Being able to download something and immediately get something to work
In the following bit of code:
while s := input.read(MAXBINSIZE):
while len(s) < MAXBINSIZE and ns := input.read(MAXBINSIZE-len(s)):
s += ns
line = binascii.b2a_base64(s)
output.write(line)
I'm getting this error on the second line:
cannot use assignm
[woops]
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@p
On 4/4/22 10:52, Coyot Linden (Glenn Glazer) wrote:
> On 4/4/22 Guido wondered:
>> How did we get from a specific issue with docstrings and the unittest
package's test
>> reporting to multi-line comments?
>
> Apologies, as I said earlier, I meant to write multiline /string/, not
multiline /comm
On 4/7/22 07:31, Petr Viktorin wrote:
On 07. 04. 22 15:59, Victor Stinner wrote:
Would it be possible to announce new PEPs on python-dev please?
Currently, all PEPs should be announced on python-dev, but not necessarily right after they're published. They should be
announced before submitti
On 7/15/22 08:37, Petr Viktorin wrote:
> And that's exactly why I consume Discourse in mailing list mode, with
client-side
> filtering in Thunderbird.
How do you handle threading? I follow each (sub)thread through to it's end, as it keeps a logical flow, but Discourse
has everything linear wh
On 7/20/22 17:35, Cameron Simpson wrote:
> On 18Jul2022 16:53, Joannah Nanjekye wrote:
>> My original stand on preferring email stands though due to stable
>> standards.
>
> Several of us use the email mode in Discourse. It works quite well. For
> me, both python-dev and the PDO posts land in my
On 12/9/22 09:20, Barry Warsaw wrote:
> The whole shift away from email leaves me calmer and better engaged.
There are definitely advantages to the different methods of staying engaged, and which is the best fit definitely
depends on the individual.
It seems to me the best possible outcome of
Gah. Already dealt with.
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives
My apologies for the accidentally accepted spam.
If you reply to that original message, please remove the link before sending.
Thanks. ;-)
--
~Ethan~
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le..
On 3/29/23 13:23, Brett Cannon wrote:
Wow, we are now getting Canadian-specific spam!
Since the volume on this mailing list is so low, should we change everyone to be moderated to start and then remove that
after they have posted appropriately? Or did this get through by accident?
Accident.
On 09/26/2019 09:28 AM, Brett Cannon wrote:
Steve Dower wrote:
The biggest thing that will change is that all our CI systems will stop
testing 2.7, and there's a good chance we'll lock (or delete?) the 2.7
branch from our repo.
A final tag of the branch will be made and then the branch will
On 10/25/2019 07:25 AM, Victor Stinner wrote:
I just posted a new PEP for comments, please reply there, rather than by email:
https://discuss.python.org/t/rfc-pep-608-coordinated-python-release/2539
PEP 608: Coordinated Python release
https://www.python.org/dev/peps/pep-0608/
Abstract:
Block
On 10/30/2019 02:53 AM, Steve Holden wrote:
If using a dictionary but still requiring attribute access, techniques such as
those used at https://github.com/holdenweb/hw can be used to simply client code.
Unless I'm missing something, that doesn't have the memory improvement that
namedtuples
On 11/04/2019 03:42 AM, Edward K. Ream wrote:
On Sun, Nov 3, 2019 at 7:23 PM Edward K. Ream wrote:
Let's be clear, there is no reason for python libraries to include every little
code gem. However, I have two motivations adding the gem to the tokenize module:
This is all irrelevant if you h
On 11/27/2019 10:38 AM, Brett Cannon wrote:
What do people think of the idea of requiring all deprecations specifying a
version that the feature will be removed in (which under our annual release
cadence would be at least the third release from the start of the deprecation,
hence the deprecat
On 12/03/2019 09:16 AM, Serhiy Storchaka wrote:
The 'u" string literal prefix was removed in 3.0 and reintroduced in 3.3 to help writing
the code compatible with Python 2 and 3 [1]. After the dead of Python 2.7 we will remove some
deprecated features kept for compatibility with 2.7. When we ar
On 12/03/2019 09:31 AM, Guido van Rossum wrote:
I think it’s too soon to worry about this. I don’t see a reason to harass
people who maintain code based that were just recently migrated.
I'm happy to go with this, since my libraries still do the 2/3 straddle.
Do we want to set a date/version
On 12/04/2019 04:21 AM, Victor Stinner wrote:
IMHO we need a metric to measure the risk of an incompatible change:
estimate the percentage of broken Python applications. For example,
run the test suite of the PyPI top 100 projects with the incompatible
change and see how many fails. That's the r
On 12/06/2019 03:19 PM, Gregory P. Smith wrote:
I'd prefer it if we stayed on topic here...
I find discussion of other computing limits, and how and why they failed (and
the hassles of working around them), very relevant.
--
~Ethan~
___
Python-Dev
I am totally against arbitrary limits in the CPython reference implementation
and in the language as a whole.
--
~Ethan~
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.pyt
ido van Rossum]
I don't think __missing__ should be called by get() -- get() already has a
way to deal with missing keys, and making it use two different mechanisms
would be weird (e.g. if get() calls __missing__, is the default value ever
used?).
[Ethan Furman]
It could be if __missing__ refused to
On 01/23/2020 03:36 PM, Barry Warsaw wrote:
On Jan 23, 2020, at 14:03, Victor Stinner wrote:
It's not only about specific changes, but more a discussion about a
general policy to decide if a deprecated feature should stay until
3.10, or if it's ok to remove it in 3.9.
Given that we’ve change
On 01/23/2020 07:02 PM, Robert Collins wrote:
On Fri, 24 Jan 2020 at 14:46, Ethan Furman mailto:et...@stoneleaf.us>> wrote:
On 01/23/2020 03:36 PM, Barry Warsaw wrote:
> On Jan 23, 2020, at 14:03, Victor Stinner wrote:
>> It's not only about specific
1201 - 1300 of 1590 matches
Mail list logo
