[Python-Dev] Re: python-ideas and python-dev migrated to Mailman 3/HyperKitty

Thanks for getting these upgraded. IMHO, being able to copy URLs from list message footers as references in e.g. issues will be a great boost in productivity. On Friday, June 7, 2019, Stephen J. Turnbull < turnbull.stephen...@u.tsukuba.ac.jp> wrote: > Barry Warsaw writes: > > On Jun 6, 2019, at

[Python-Dev] Re: python-ideas and python-dev migrated to Mailman 3/HyperKitty

On Fri, Jun 7, 2019 at 4:30 PM Stephen J. Turnbull wrote: > They could, however be made more friendly than they currently are. > There's no reason (in principle, of course it requires changing code > and the DNS) why your message, currently given the Archived-At URL > > https://mail.python.org/arc

[Python-Dev] Re: obmalloc (was Have a big machine and spare time? Here's a possible Python bug.)

On 2019-06-06, Tim Peters wrote: > The doubly linked lists in gc primarily support efficient > _partitioning_ of objects for gc's purposes (a union of disjoint sets, > with constant-time moving of an object from one set to another, and > constant-time union of disjoint sets). "All objects" is almo

[Python-Dev] Re: python-ideas and python-dev migrated to Mailman 3/HyperKitty

Barry Warsaw writes: > On Jun 6, 2019, at 09:15, David Mertz wrote: > > > > The old URL is definitely a lot friendlier, even apart from the length. > > Unfortunately, the old URLs aren’t really permanent. True. That could be addressed in theory, but it would be fragile (ie, vulnerable to

[Python-Dev] Re: obmalloc (was Have a big machine and spare time? Here's a possible Python bug.)

On 2019-06-06, Tim Peters wrote: > Like now: if the size were passed in, obmalloc could test the size > instead of doing the `address_in_range()` dance(*). But if it's ever > possible that the size won't be passed in, all the machinery > supporting `address_in_range()` still needs to be there, an

[Python-Dev] PEP 596 proposes doubling the release cadence

PEP body and discussion link: https://discuss.python.org/t/pep-596-python-3-9-release-schedule-doubling-the-release-cadence/1828 - Ł signature.asc Description: Message signed with OpenPGP ___ Python-Dev mailing list -- python-dev@python.org To unsubscr

[Python-Dev] Re: obmalloc (was Have a big machine and spare time? Here's a possible Python bug.)

On Thu, 6 Jun 2019 17:26:17 -0500 Tim Peters wrote: > > The doubly linked lists in gc primarily support efficient > _partitioning_ of objects for gc's purposes (a union of disjoint sets, > with constant-time moving of an object from one set to another, and > constant-time union of disjoint sets).

[Python-Dev] Re: obmalloc (was Have a big machine and spare time? Here's a possible Python bug.)

[Tim] >> But I don't know what you mean by "access memory in random order to >> iterate over known objects". obmalloc never needs to iterate over >> known objects - indeed, it contains no code capable of doing that.. >> Our cyclic gc does, but that's independent of obmalloc. [Antoine] > It's not.

[Python-Dev] Re: obmalloc (was Have a big machine and spare time? Here's a possible Python bug.)

On Thu, 6 Jun 2019 16:03:03 -0500 Tim Peters wrote: > But I don't know what you mean by "access memory in random order to > iterate over known objects". obmalloc never needs to iterate over > known objects - indeed, it contains no code capable of doing that.. > Our cyclic gc does, but that's inde

[Python-Dev] Re: PEP 594: update 1

On 06.06.19 21:27, Brett Cannon wrote: > > > On Thu, Jun 6, 2019 at 12:25 AM Christian Tismer > wrote: > > On 05.06.19 02:21, Victor Stinner wrote: > > So what is happening for this PEP since Python 3.8 beta1 has been > > released? Is it too late for Pyt

[Python-Dev] Re: obmalloc (was Have a big machine and spare time? Here's a possible Python bug.)

[Antoine Pitrou ] > But my response was under the assumption that we would want obmalloc to > deal with all allocations. I didn't know that. I personally have no interest in that: if we want an all-purpose allocator, there are several already to choose from. There's no reason to imagine we coul

[Python-Dev] Re: PEP 594: update 1

On Thu, Jun 6, 2019 at 12:25 AM Christian Tismer wrote: > On 05.06.19 02:21, Victor Stinner wrote: > > So what is happening for this PEP since Python 3.8 beta1 has been > > released? Is it too late for Python 3.8 or not? > > > > It seems like most people are confused by the intent of the PEP. IMH

[Python-Dev] Re: obmalloc (was Have a big machine and spare time? Here's a possible Python bug.)

On Thu, 6 Jun 2019 13:57:37 -0500 Tim Peters wrote: > [Antoine Pitrou ] > > The interesting thing here is that in many situations, the size is > > known up front when deallocating - it is simply not communicated to the > > deallocator because the traditional free() API takes a sole pointer, > > no

[Python-Dev] Re: obmalloc (was Have a big machine and spare time? Here's a possible Python bug.)

[Antoine Pitrou ] > The interesting thing here is that in many situations, the size is > known up front when deallocating - it is simply not communicated to the > deallocator because the traditional free() API takes a sole pointer, > not a size. But CPython could communicate that size easily if we

[Python-Dev] Re: python-ideas and python-dev migrated to Mailman 3/HyperKitty

On Jun 6, 2019, at 09:15, David Mertz wrote: > > The old URL is definitely a lot friendlier, even apart from the length. Unfortunately, the old URLs aren’t really permanent. Hypermail calculated them sequentially and if you rebuild the archive from the source-of-truth mbox files, there’s no w

[Python-Dev] Re: python-ideas and python-dev migrated to Mailman 3/HyperKitty

The old URL is definitely a lot friendlier, even apart from the length. I know at a glance the month and list where the thread occurred, which is perhaps the most important metadata. In the new link I only know what mailing list it happened on, and nothing else meaningful. On Thu, Jun 6, 2019, 8:2

[Python-Dev] Re: PEP 594: update 1

On 04Jun2019 1721, Victor Stinner wrote: So what is happening for this PEP since Python 3.8 beta1 has been released? Is it too late for Python 3.8 or not? It seems like most people are confused by the intent of the PEP. IMHO it would be better to rewrite "Remove packages from the stdlib" as "Mov

[Python-Dev] Re: python-ideas and python-dev migrated to Mailman 3/HyperKitty

Le jeu. 6 juin 2019 à 14:18, Steven D'Aprano a écrit : > i.e. 25-40% longer. Is there a shorter permalink form available, like > goo.gl, bitly, youtu.be etc use? That would be awesome if we could use > them instead. I really dislike URL shorteners. From my point of view, URL shorteners are the o

[Python-Dev] Re: python-ideas and python-dev migrated to Mailman 3/HyperKitty

On Wed, Jun 05, 2019 at 11:08:13AM +0200, Victor Stinner wrote: > Enhancements: > * More reliable "permalink" URLs to emails This is excellent... but the old pipermail URLs were typically something like 70-80 characters, which means they fit nicely into emails (and comments in source code). H

[Python-Dev] Re: PEP 594: update 1

On 05.06.19 02:21, Victor Stinner wrote: > So what is happening for this PEP since Python 3.8 beta1 has been > released? Is it too late for Python 3.8 or not? > > It seems like most people are confused by the intent of the PEP. IMHO > it would be better to rewrite "Remove packages from the stdlib"