reconsider pipenv
from #90 (closed).
pipenv feedback after a month:
- wait a second, why is latest pipenv from 1y+ ago, 683 commits, yet no release? what's the schedule? check it for yourself. latest is 2018.11.26
- git depedency support sucks, especially when those git deps are a part of a package (now that we splitted off elixire functionality into 3 separate libraries, it hits hard)
- no support to signal multiple python support (and never will, considering the answers to the issues of people asking for that support)
- building the lockfile can be massively slow (and also timeout for some reason) for issues that weren't supposed to be there (see point 1,
hail
was an existing pypi package, pipenv chose it, instead of ourhail
in thesetup.py
of a depedency. i had to bump up the timeout, this isn't a good solution...?) - setting "*" as the default version for a given package is a bad idea, users must be able to manually check out versions in the file, instead of leaving everything automatic, or else you get a surprise update
options:
- try poetry (i gave up on it for violet due to having too many issues, i wanted it to be installeable by pipenv, but i guess not, went with setup.py instead, as well as others)
- go back to requirements.txt + venv (to be honest, this might be the best one, since well, it worked...)