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,
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
>
>
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
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
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
Hello,
I'm starting this thread to brainstorm for using vectorcall to speed up
creating instances of Python classes.
Currently the following happens when creating an instance of a Python
class X using X(.) and assuming that __new__ and __init__ are Python
functions and that the
On Jun 6, 2019, at 23:50, Wes Turner wrote:
>
> 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.
Just FYI, these URLs are a “standard" we proposed many years ago, with
ACTIVITY SUMMARY (2019-05-31 - 2019-06-07)
Python tracker at https://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open7007 (-21)
closed 41943 (+104)
total 48950 (+83)
Open issues
On 6/7/2019 6:41 AM, Jeroen Demeyer wrote:
Hello,
I'm starting this thread to brainstorm for using vectorcall to speed up
creating instances of Python classes.
Currently the following happens when creating an instance of a Python
class X using X(.) and assuming that __new__ and __init__
On Thu, Jun 6, 2019 at 6:19 AM Victor Stinner wrote:
> 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
Wes Turner wrote:
> 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.
This is possible to do using "$hyperkitty_url" in the message footer. You can
request the list owners to add that.
On Jun 7, 2019, at 18:03, Victor Stinner wrote:
> I am not sure that we are good at archiving.
I'm not sure what this has to do with mailing list URLs but ...
> Example with Subversion links in the bug tracker:
>
> https://bugs.python.org/issue2001#msg123254
>
> "Added the missing CSS file in
I am not sure that we are good at archiving. Example with Subversion links
in the bug tracker:
https://bugs.python.org/issue2001#msg123254
"Added the missing CSS file in r86971."
The revision link is:
https://hg.python.org/lookup/r86971
Which redirects to the following HTTP 404 (not found)
To be clearer, while knowing the size of allocated objects may be of
some use to some other allocators, "not really" for obmalloc. That
one does small objects by itself in a uniform way, and punts
everything else to the system malloc family. The _only_ thing it
wants to know on a free/realloc is
14 matches
Mail list logo
