The only real advantage is a simpler signature and more easily explained use
(assuming the person you're explaining it to is familiar with metaclasses, so
most of the hard explaining has been done).
I'm still not sure that this isn't simply a bug in super. If the superclass's
metaclass provides
On 8 Jul, 2013, at 17:19, Steve Dower wrote:
> The only real advantage is a simpler signature and more easily explained use
> (assuming the person you're explaining it to is familiar with metaclasses, so
> most of the hard explaining has been done).
The signature is as complex as it is to be
Since it's relevant: my recollection us that the current use of angle
brackets in inspect.Signature is just the default use of them for "there is
no canonical representation of this, but leaving them out would be
misleading" (I haven't checked if the PEP says that explicitly).
I previously forgot
> From: Ronald Oussoren [mailto:[email protected]]
> Sent: Monday, July 8, 2013 0858
>
> On 8 Jul, 2013, at 17:19, Steve Dower wrote:
>
> > The only real advantage is a simpler signature and more easily explained
> use (assuming the person you're explaining it to is familiar with metaclasses
Hi,
The PEP 445 (Add new APIs to customize Python memory allocators) has
been accepted, I commited its implementation. So it's time to have fun
with this API.
I developed a small Python module (150 lines of C code) to inject
memory allocation failures:
https://pypi.python.org/pypi/pyfailmalloc
T
2013/7/9 Victor Stinner :
> I developed a small Python module (150 lines of C code) to inject
> memory allocation failures:
> https://pypi.python.org/pypi/pyfailmalloc
Bitbucket was down, so I was unable to give the link to its source
code. The server is back, here is the C code:
https://bitbucket
