ThatXliner

Maybe we can just delete https://github.com/hax/atom-elastic-tabstops/blob/956a0a3fd92e3d27364579c70db70c0aea5f119a/lib/elastic-tabstops.js#L105-L109

I guess they just removed those variables from the `__init__.py` and put it in the `__version__.py`. They might need to add an `__all__` variable to let the user get this...

@gruns The main code is in `furl.py`, right? So I just need to add `__all__ = ["furl", "__version__"]` unless some of the implementation are in the other files.

Same. Only `black==21.10b` worked

Remind me again, did our Poetry plugin use the `poetry poe task` style or `poetry task` or both? @nat-n

It seems to me that the plugin itself is breaking poetry. Just curious, what happens when you try to use Poe via Poetry plugin? Does it work?

Maybe we could use pexpect for spawning stuff. It’s used by Poetry for the `poetry shell` command[^1]. Here’s an example of pexpect: https://github.com/pexpect/pexpect/blob/master/examples/python.py [^1]: https://github.com/python-poetry/poetry/blob/4838c9fe9645c62353be569a96765c693f03f1a3/src/poetry/utils/shell.py#L71

> we can later add some config about how these are executed. It can be crossplatform alternative to parallel like a `backend` config on how to parallelize?

~~Seems good but why 3 or 4 as default for stderr?~~ On second thought, yeah: you want to see the errors quickly. I was thinking of those multi-line errors/warnings like...

I have successfully transpiled lark (via nuitka) into C *but* the `common.lark` and other metadata files had some trouble catching on the transpiliation.