f doing this without slightly changing CPython.
Has anyone any idea on how to workaround this or the kind of change that
could be acceptable to mitigate the issue?
Thanks!
Cheers,
--
Julien Danjou
# Free Software hacker
# https://julien.danjou.info
___
Pyt
3
different memory allocator, it'd be great if there was some ability to
be sure that PyObject_Malloc pointer are actually PyObject, not
Py_GC_HEAD.
--
Julien Danjou
// Free Software hacker
// https://julien.danjou.info
___
Python-Dev mailing list
uot;
>
> FYI, the implementation usually resolves it by looking at whether
> obj's type object has the Py_TPFLAGS_HAVE_GC flag set.
Right, but that only works if you have the PyObject address.
If you all got is a pointer returned by PyObject_Malloc(), you don't
know if the PyObject
On Fri, Jan 15 2021, Antoine Pitrou wrote:
> Also note that PyObject_Malloc() may also be used to allocate
> non-objects, for example a bytearray's payload, IIRC.
Interesting. What's the rational for not using PyMem_Malloc() in such
cases?
--
Julien Danjou
# Free Softwar
evel for this,
preventing any kind of statistical analysis of the allocation patterns.
:(
--
Julien Danjou
# Free Software hacker
# https://julien.danjou.info
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-l
from a PyThreadState?
Cheers,
--
Julien Danjou
# Free Software hacker
# https://julien.danjou.info
___
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/p
ions have been moved to the internal API for example. The
> internal C API *can* be used, but you have to opt-in so you know that
> you get unstable APIs :-)
Alright! I didn't know that you could use private functions. I'm totally
in the debugger case so it's fine with me
kind of warning when doing backports could be worth it.
Cheers,
--
Julien Danjou
// Free Software Hacker
// https://julien.danjou.info
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
ht
Python
> caused the problem? Well, open a issue and try to provide as much
> information as possible ;-)
This happened in a custom module I wrote.
I've opened https://bugs.python.org/issue39599 with as many details as I
can right now. It's a bit fuzzy even for me how to repr
rged and get this bug
closed?
Cheers,
--
Julien Danjou
// ᐰhttp://julien.danjou.info
// 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD
// Trust no one.
signature.asc
Description: Digital signature
___
Python-Dev mailing list
Python-Dev@pyt
re-developement-too",
you are just pissing me off for not fixing a bug in your program with a 10
lines long patch written by someone else 3 years ago.
Something that should take 5 minutes, probably the time we both lost by
writing our respective emails. Or give commit access, I'll do it f
11 matches
Mail list logo
