tractor

tractor copied to clipboard

Not sure why I'm surprised; every time I try to release something moderately "bleeding edge" pypi stuff never works. This one may have been a newb mistake though: ``` ERROR:...

goodboy

WIP to start moving internals to new `match:` syntax in 3.10+ --- ### high level reorg - rename `._actor.py` -> `_runtime.py`

goodboy

Ctx result consumption

3

Better handling of contex teardowns where IPC msgs might still be in transit that need to be discarded as well a more explicit tolerance for IPC transport failures when determining...

goodboy

Static msg types using `msgspec`

1

WIP typed msg layer using `msgspec`. Relates to: - https://github.com/goodboy/tractor/issues/196 - #294 Further motivation for the approach being taken is hashed out somewhat in https://github.com/jcrist/msgspec/issues/140 still needs lootttsa work..

goodboy

Discovered and **heavily worked around** in #165 as well as well documented in #113. The `test_debugger.py` suite currently is [marked up with a `@has_nested_actors`](https://github.com/goodboy/tractor/pull/165/files#diff-81c725c5c517d5d3927004cfafe30e5e0eb48fba9288aaf93065fec72c797dfdR67) for the test scripts which do...

goodboy

As per some work I've been doing with `QT` in pikers/piker#52 (particularly to do with using `quamash`) I would like to see what can be whipped up for interacting with...

goodboy

REPL-driven, multi-process-native debugger features

1

In `tractor` every actor is both a (potential) *client* and *server*. Concocting a "native" feeling "remote debugger" shouldn't be that bad (they thought naively..), right? I did a little digging...

goodboy

Fancy remote debugging (aka tab completion and editor controls)

2

As part of the journey in #129 I discovered that no-one seems to have solved the problem of getting the *fancy features* of a modern Python debugger working in remote...

goodboy

Handling `breakpoint()` usage from sync code

1

With the introduction of our multi-process debugger system in #126 via `await tractor.breakpoint()`, we probably need to consider how a user can call the standard `breakpoint()` from sync code in...

goodboy

Does the debugger work on Windows? Yes, yes it does, but how do we test it?

2

This turned up in working the CI for #129. Turns out `pexpect` (and thus [sensibly `pytest`](https://github.com/pytest-dev/pytest/blob/master/src/_pytest/pytester.py#L1449)) [doesn't support `spawn()` on Windows](https://pexpect.readthedocs.io/en/stable/overview.html#pexpect-on-windows) so we have no way to know with the...

goodboy