Summary
Now that the engine has been overhauled on master, would you consider tagging and publishing a new release to PyPI?
Problem statement
The latest version on PyPI is still 0.6.7 (Nov 2022), so none of the recent master work — including the dependency modernization you've already done — is pip install-able. The README's pip install git+https://… works for end users, but a git URL can't be used as a dependency in another package's published metadata, so downstream projects still can't depend on findpapers from PyPI.
Proposed solution
A release cut from master (e.g. 0.6.8 / 0.7.0); the version string there is still 0.6.7. That alone would unblock downstream packaging — no code changes needed on your side beyond the version bump + publish.
Alternatives considered
I currently vendor a trimmed 0.6.7 inside my own tool to ship on PyPI, but that means my users miss your ongoing master improvements — I'd much rather track real releases.
Additional context
No rush — mostly wanted to flag the downstream-packaging angle and ask if a release is on the roadmap. Happy to test a pre-release/TestPyPI build or help with release prep if that's useful. Thanks for the continued work on this!
Summary
Now that the engine has been overhauled on master, would you consider tagging and publishing a new release to PyPI?
Problem statement
The latest version on PyPI is still 0.6.7 (Nov 2022), so none of the recent master work — including the dependency modernization you've already done — is pip install-able. The README's pip install git+https://… works for end users, but a git URL can't be used as a dependency in another package's published metadata, so downstream projects still can't depend on findpapers from PyPI.
Proposed solution
A release cut from master (e.g. 0.6.8 / 0.7.0); the version string there is still 0.6.7. That alone would unblock downstream packaging — no code changes needed on your side beyond the version bump + publish.
Alternatives considered
I currently vendor a trimmed 0.6.7 inside my own tool to ship on PyPI, but that means my users miss your ongoing master improvements — I'd much rather track real releases.
Additional context
No rush — mostly wanted to flag the downstream-packaging angle and ask if a release is on the roadmap. Happy to test a pre-release/TestPyPI build or help with release prep if that's useful. Thanks for the continued work on this!