You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 19, 2021. It is now read-only.
Currently this repository contains both requirements.txt and Pipfile.lock. Those two files are not kept in sync, which means that depending on how a user installs Paperless, they will have a different set of dependencies available than if they had installed using a different method.
To avoid confusion and ensure that our users always use the same set of dependencies, we should move to a single solution. Given the use of Pipenv within CI, removing requirements.txt seems like the sensible option.
(I mainly opened this issue to keep track of this topic myself. I'll work on migrating to Pipenv and will open a PR for this. If there are any opinions or concerns, please feel free to voice them -- either here or on the PR once it exists.)
The text was updated successfully, but these errors were encountered:
In b1e6160 Pipenv was added to
Paperless, adding a note to the changelog in
eec8f09 that a switch to just using
Pipenv was planned.
This commit performs this switch. Having two sources for which
dependencies should be installed (requirements.txt, Pipfile.lock) is
very suboptimal, and the files have diverged since they have been added.
This closesthe-paperless-project#661.
Currently this repository contains both
requirements.txt
andPipfile.lock
. Those two files are not kept in sync, which means that depending on how a user installs Paperless, they will have a different set of dependencies available than if they had installed using a different method.To avoid confusion and ensure that our users always use the same set of dependencies, we should move to a single solution. Given the use of Pipenv within CI, removing
requirements.txt
seems like the sensible option.(I mainly opened this issue to keep track of this topic myself. I'll work on migrating to Pipenv and will open a PR for this. If there are any opinions or concerns, please feel free to voice them -- either here or on the PR once it exists.)
The text was updated successfully, but these errors were encountered: