I’m posting this here after a suggestion from VorpalSmith on Reddit. I’m working on a package manager that attempts to address shortfalls with existing processes. The Github readme explains my reasoning for a new tool, and am looking for critique/spears/holes/design-flaws etc.
- Stores packages in
- Uses a custom API to store and query dependency info, since the PyPi warehouse info is inconsistent/unreliable.
- Installs multiple versions of a dependency via renaming, if otherwise unresolvable. Has some problems like if relative imports are in binaries, or if another package attempts to use one using this as a dependency. I think it’s still worth it, since there are many cases where Pipenv and Poetry will fail to resolve, where this approach works.
- Doesn’t run on Python, so isn’t sensitive to how it’s installed.
- Aims to be as easy-to-use as possible, ie the user should never have to consider environments / terminal state, features considered out-of-scope etc.
In particular: What do you think of the multiple-version approach? Alternative implementations? Traditionally, this has been treated as unfeasible. My thought is that it works in many cases, so allow it, even though it’s not perfect.