Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

Remove mysqlclient from requirements #235

Closed
miterion opened this issue Apr 10, 2018 · 2 comments · Fixed by #277
Closed

Remove mysqlclient from requirements #235

miterion opened this issue Apr 10, 2018 · 2 comments · Fixed by #277
Assignees
@ckleemann
Labels
meta

Comments

@miterion
Copy link
Member

miterion commented Apr 10, 2018 •
edited

Currently there is a dependency called mysqlclient in the requirements. It is not needed for local development and should be put in a specialised requirements file.
@miterion miterion added the meta label Apr 10, 2018
@ckleemann
Copy link
Contributor

Actually we need to split the requirement.txt file. There is a base set of packages which is always required. Then there is a set of development packages e.g. coverage and a set of production requirements e.g. mysqlclient.

@miterion
Copy link
Member Author

miterion commented Oct 3, 2018

Creating three requirements files (at least until pipenv supports production requirements) seems to be the best solution for now

ckleemann added a commit that referenced this issue Dec 30, 2018
@ckleemann
split requirements.txt for dev and prod #235
d9dfc52
ckleemann added a commit that referenced this issue Dec 30, 2018
@ckleemann
change update script to splitted requirements #235
94961e3
ckleemann added a commit that referenced this issue Dec 30, 2018
@ckleemann
change .travis settings for splitted requirements #235
6ab8178
@ckleemann ckleemann mentioned this issue Dec 30, 2018
Merged
@ckleemann ckleemann self-assigned this Dec 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ckleemann ckleemann

Labels
meta
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Package split d120/pyophase
2 participants
@miterion @ckleemann