Hi all,
Current pdb and bdb didn't have the ability to create a watchpoint for variable.
Such in gdb, it have a series of watchpoint function*:
* watch : break when expression value changed
* rwatch : break when read value from expression
* awatch: breka when read or write value to
Hm... Curiously, I've heard a few people at PyCon mention they thought
subinterpreters were broken and not useful (and they share the GIL anyways)
and should be taken out. So we should at least have clarity on which
direction we want to take...
On Wed, May 24, 2017 at 6:01 PM, Eric Snow
CC'ing PyPy-dev...
On Wed, May 24, 2017 at 6:01 PM, Eric Snow wrote:
> Although I haven't been able to achieve the pace that I originally
> wanted, I have been able to work on my multi-core Python idea
> little-by-little. Most notably, some of the blockers have been
Although I haven't been able to achieve the pace that I originally
wanted, I have been able to work on my multi-core Python idea
little-by-little. Most notably, some of the blockers have been
resolved at the recent PyCon sprints and I'm ready to move onto the
next step: exposing multiple
On 05/24/2017 02:41 AM, Steven D'Aprano wrote:
On Wed, May 24, 2017 at 12:18:16AM +0300, Serhiy Storchaka wrote:
It seems to me that the purpose of this proposition is not performance,
but the possibility to use __fspath__ in str or bytes subclasses.
Currently defining __fspath__ in str or