Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • concrexit concrexit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 70
    • Issues 70
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • thalia
  • concrexitconcrexit
  • Merge requests
  • !879

Merged
Created Aug 01, 2018 by Thom Wiggers@twiggers📐Contributor7 of 7 tasks completed7/7 tasks

Use pipenv instead of requirements.txt

  • Overview 0
  • Commits 12
  • Changes 9

Closes #672 (closed), #631 (closed)

Short description

  • Use pipenv instead of requirements.txt
  • Easier usage of virtual envs
  • Easier handling of dev environments (pipenv install --dev)
  • Supersedes pipconflictchecker (thus closes #631 (closed))
  • Supersedes safety (integrated in pipenv check)

Todo

  • Fix tests
  • Delete requirements.txt
  • Update docs
  • Figure out how pipenv check handles python_version (https://github.com/pypa/pipenv/issues/2694)
  • Fix docker build
  • https://github.com/thaliawww/python-thalia/pull/1
  • https://github.com/thaliawww/python-thalia/pull/2

Caveats

  • This does get rid of the separate production-requirements.txt and thus may require installing more C libraries (argon2, postgresql) on development systems. On the other hand, production and development will be much closer.
Edited Aug 08, 2018 by Thom Wiggers
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: pipenv-instead-of-requirements