Use Pythonic?

[pwalsh]

Description

Pythonic is a mature library with a range of utility functions around managing Python processes, setting vars for Python environments, etc.

Tasks

• Check if Pipenv's way of managing things can leverage Pythonic
• Identify specific functions to rebase on Pythonic functionality

[pwalsh]

Pythonic is a great library. However, with the way Pipenv is design to work, users mostly have Pipenv installed as a system binary, and use it to manage Python environments. This means we can't really gain anything by using Pythonic, as Pipenv is in a different scope to the Python being used.

I then considered which commands that we support here are executed with the active Python environment, and the two commands are run and open.

run is run via the pipenv executable anyway, so there is no clear need/advantage to use Pythonic.

open has been implemented in emacs lisp, ported from Pipenv's Python code, so that files are opened in the current Emacs session. While this could be done with Pythonic, again the benefit is not clear at this stage of development.

Happy to revisit this, but, recording my thinking here for now, and closing the issue.