Skip to content

Updating pipenv specific files#415

Closed
sujaypatil96 wants to merge 5 commits intomainfrom
spatil/pipfile-lock-update
Closed

Updating pipenv specific files#415
sujaypatil96 wants to merge 5 commits intomainfrom
spatil/pipfile-lock-update

Conversation

@sujaypatil96
Copy link
Member

This PR seeks address issue #76. The following points are the highlight of the PR:

  • Update instructions so that pipenv is used only by package developer or contributors to install the package locally for testing purposes
  • Regular users should stick to using pip to install the package from PyPI as detailed in the docs
  • Create requirements.txt and requirements-dev.txt. These files have been generated using pipenv and not pip

@sujaypatil96 sujaypatil96 requested a review from cmungall October 18, 2021 07:47
@sujaypatil96 sujaypatil96 added the devops poetry (now uv), setuptools, actions, etc. label Oct 18, 2021
@sujaypatil96 sujaypatil96 added this to the 2021-12-01 milestone Oct 18, 2021
@sujaypatil96 sujaypatil96 linked an issue Oct 18, 2021 that may be closed by this pull request
Copy link
Member

@cmungall cmungall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let me check I understand - does this have the effect of locking versions for every application that uses linkml? That isn't desirable. E.g. we will block people from using click 7.1.3 or jinja 3.0.3 etc

@sujaypatil96 sujaypatil96 marked this pull request as draft October 18, 2021 22:38
@sujaypatil96
Copy link
Member Author

I can see in the requirements.txt and requirements-dev.txt files that where it says in the comments that the requirements files have been automatically generated using pipenv.

The commands that freeze out the requirements using pipenv are as follows:

$ pipenv lock --requirements > requirements.txt
$ pipenv lock --requirements --dev-only > requirements.txt

The requirements files that are in this PR have been generated using the above commands. If we don't want to use them, I'm happy to remove them.

@cmungall cmungall closed this Nov 12, 2021
@sujaypatil96 sujaypatil96 deleted the spatil/pipfile-lock-update branch December 2, 2021 08:33
iQuxLE pushed a commit that referenced this pull request Aug 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

devops poetry (now uv), setuptools, actions, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Pipfile.lock needs updating

2 participants