On Sat, 9 Jan 2021, 7:07 am Joseph Martinot-Lagarde,
wrote:
> Paul Sokolovsky wrote:
> > Hello,
> > On Tue, 5 Jan 2021 20:37:27 +1000
> > Nick Coghlan ncogh...@gmail.com wrote:
> > > object(host=as host, port=as port}:", but that
> > > couldn't ever be
> > > I'd like to point out the weirdness of
Hi,
In the Python stdlib, many heap types currently don't "properly"
(fully?) implement the GC protocol which can prevent to destroy these
types at Python exit. As a side effect, some other Python objects can
also remain alive, and so are not destroyed neither.
There is an on-going effect to dest
Someone reported a testsuite break on stuff I work on (scons) with
3.10a4, and it looks similar to this which appears in the changelog at
https://docs.python.org/3.10/whatsnew/changelog.html#changelog
bpo-23898: Fix inspect.classify_class_attrs() to support attributes with
overloaded __eq_
On 9/01/21 9:12 am, Chris Barker wrote:
(though I notice that if you create __slots__ in pure Python, its names
show up in dict anyway -- so clearly I'm confused...)
Descriptors for the slots get added to the *class* dict.
But that's not the dict that vars() looks at.
--
Greg
_
On Jan 8, 2021, at 14:38, Chris Barker via Python-Dev
wrote:
> Sorry if I'm out of the loop here, but with Apple's new chip coming out, we
> need new a build configuration (which I think has already been started, if
> not done).
>
> Perhaps we could take this opportunity to better modularize /
Paul Sokolovsky wrote:
> Hello,
> On Tue, 5 Jan 2021 20:37:27 +1000
> Nick Coghlan ncogh...@gmail.com wrote:
> > object(host=as host, port=as port}:", but that
> > couldn't ever be
> > I'd like to point out the weirdness of the "as" syntax when applied
> to
> positional arguments, e.g.:
> case [as
This was discussed a bit over on python-ideas recently, so a note from me,
and one from that thread:
Or for that matter, not the reason to provide
> object's internal storage via object's attribute: obj.__dict__.
>
Well, it IS an implementation detail that it's a dictionary, but having a
dunder t
On Wed, Dec 23, 2020 at 1:06 AM Steven D'Aprano wrote:
> We're not obligated to take heroic
> measures to integrate numpy arrays with unittest methods. If we can do
> so easily, sure, let's fix it.
>
> I think Ivan's suggestion that the assertSequenceEqual method fall back
> on element-by-element
Sorry if I'm out of the loop here, but with Apple's new chip coming out, we
need new a build configuration (which I think has already been started, if
not done).
Perhaps we could take this opportunity to better modularize / unify the
build setup?
As it was last I checked, you really had only two
ACTIVITY SUMMARY (2021-01-01 - 2021-01-08)
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:
open7549 ( -7)
closed 47055 (+71)
total 54604 (+64)
Open issues w
10 matches
Mail list logo
