+1 -- thanks so much for acting as our scribe again!
On Wed, Jun 6, 2018 at 5:47 PM, Eric Snow
wrote:
> Thanks for doing this Jake.
>
> -eric
>
> On Wed, Jun 6, 2018 at 3:56 PM, Jake Edge wrote:
> >
> > Hola python-dev,
> >
> > I have been remiss in posting about my coverage from this year's
That sounds right to me. We will then have had two versions where this was
the case:
- 3.6 where order preserving was implemented in CPython but in the language
spec
- 3.7 where it was also added to the language spec
On Fri, Jun 8, 2018 at 11:05 AM, Michael Selik wrote:
> Am I correct in saying
> Is this a bug or a feature?
The bug was me being so excited about the new construct (I pushed in
someone else's work, can't recall who now, maybe Fredrik Lundh?) that
I didn't consider that leaking the loop variable out of the list
comprehension was a bad idea. Think of the Py3 behavior as one
Am I correct in saying that the consensus is +1 for inclusion in v3.8?
The last point in the thread was INADA Naoki researching various
implementations and deciding that it's OK to include this feature in 3.8.
As I understand it, Guido was in agreement with INADA's advice to wait for
On 06/06/2018 03:51 PM, Nick Coghlan wrote:
> On 6 June 2018 at 15:31, Rob Cliffe via Python-Dev mailto:python-dev@python.org>> wrote:
> ...
> *In other words, it looks as if in Python 3.6.5, the compiled list
comprehension**
> **can "see" a pre-existing global variable but not a local
On Fri, Jun 8, 2018 at 9:24 AM Ronald Oussoren wrote:
[..]
> Wouldn’t it be enough to visit just the the newly tracked object in
> PyObject_GC_Track with a visitor function that does something minimal to
> verify that the object value is sane, for example by checking
>
ACTIVITY SUMMARY (2018-06-01 - 2018-06-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:
open6691 ( +8)
closed 38869 (+66)
total 45560 (+74)
Open issues
> On 8 Jun 2018, at 12:36, Serhiy Storchaka wrote:
>
> 08.06.18 11:31, Victor Stinner пише:
>> Do you suggest to trigger a fake "GC collection" which would just
>> visit all objects with a no-op visit callback? I like the idea!
>>
>> Yeah, that would help to detect objects in an inconsistent
On Thu, Jun 07, 2018 at 06:02:40PM +0100, MRAB wrote:
> The Python community _is_ meant to be inclusive, and we should support
> the addition of ginger emoijs. :-)
https://www.youtube.com/watch?v=KVN_0qvuhhw
--
Steve
___
Python-Dev mailing list
08.06.18 11:31, Victor Stinner пише:
Do you suggest to trigger a fake "GC collection" which would just
visit all objects with a no-op visit callback? I like the idea!
Yeah, that would help to detect objects in an inconsistent state and
reuse the existing implemented visit methods of all types.
2018-06-08 10:17 GMT+02:00 Serhiy Storchaka :
> Reducing GC threshold can hide other bugs that will be reproducible only in
> the release mode (because of earlier releasing of resources or changed order
> of destroying objects).
>
> What is the cost of traversing all objects? Would it be too high
2018-06-04 18:31 GMT+02:00 Victor Stinner :
> Quick update a few days later.
> (...)
> Except Windows 7 which has issues with test_asyncio and
> multiprocessing tests because this buildbot is slow, it seems like
> most CIs are now stable.
The bug wasn't specific to this buildbot, it was a very
08.06.18 10:48, Victor Stinner пише:
Yury Selivanov pushed his implementation of the PEP 567 -- Context
Variables at January 23, 2018. Yesterday, 4 months after the commit
and only 3 weeks before 3.7.0 final release, a crash has been found in
the implementation:
2018-06-07 4:45 GMT+02:00 Mariatta Wijaya :
> Are there APIs we can use to check the status of builbots?
Buildbots offer different ways to send notifications: emails and IRC
bot for example.
If you want to *poll* for recent builds, I don't know. I would suggest
to use notifications (push) rather
Hi,
Yury Selivanov pushed his implementation of the PEP 567 -- Context
Variables at January 23, 2018. Yesterday, 4 months after the commit
and only 3 weeks before 3.7.0 final release, a crash has been found in
the implementation:
https://bugs.python.org/issue33803
(it's now fixed, don't worry
15 matches
Mail list logo
