-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUILD] Move from requirements.txt
to Pipfile
#131
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, left some improvement suggestions
Until now dependencies were defined in two separate files (requirements.txt and Pipfile). As decided in COVESA#114 we'll move to `Pipfile`. * removed `requirements.txt` to avoid confusion * removed section from `README.md` * changed `buildcheck.yml` to use `pipenv` Fixes: COVESA#114 Signed-off-by: Daniel Wilms <Daniel.DW.Wilms@bmw.de>
ff3f156
to
d9db3d6
Compare
@barbieri, I changed the python version in a separate commit, but in the same PR. Please have a look, if now everything is resolved. |
Moved to the latest security release, as porposed by @barbieri. * Updated Pipfile, and resulting changes in Pipfile.lock * Updated buildscript * Updated README.md Signed-off-by: Daniel Wilms <Daniel.DW.Wilms@bmw.de>
55f0dcd
to
275f931
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. And much nicer to run the same in CI we expect users to run 👍
meeting 11/01/2022: approved to be merged @erikbosch |
We changed in vss-tools from `requirements.txt` to `Pipfile` and in order to update the submodule we have to do the change here in VSS as well. Updated `buildcheck.yaml`: * changed to pyenv instead of python action * Use `Pipfile` instead of `requirements.txt` Related to: COVESA/vss-tools#131 Signed-off-by: Daniel Wilms <Daniel.DW.Wilms@bmw.de>
We changed in vss-tools from `requirements.txt` to `Pipfile` and in order to update the submodule we have to do the change here in VSS as well. Updated `buildcheck.yaml`: * changed to pyenv instead of python action * Use `Pipfile` instead of `requirements.txt` Related to: COVESA/vss-tools#131 Signed-off-by: Daniel Wilms <Daniel.DW.Wilms@bmw.de>
We changed in vss-tools from `requirements.txt` to `Pipfile` and in order to update the submodule we have to do the change here in VSS as well. Updated `buildcheck.yaml`: * changed to pyenv instead of python action * Use `Pipfile` instead of `requirements.txt` Related to: COVESA/vss-tools#131 Signed-off-by: Daniel Wilms <Daniel.DW.Wilms@bmw.de>
We changed in vss-tools from `requirements.txt` to `Pipfile` and in order to update the submodule we have to do the change here in VSS as well. Updated `buildcheck.yaml`: * changed to pyenv instead of python action * Use `Pipfile` instead of `requirements.txt` Related to: COVESA/vss-tools#131 Signed-off-by: Daniel Wilms <Daniel.DW.Wilms@bmw.de>
Until now dependencies were defined in two separate files
(requirements.txt and Pipfile). As decided in #114 we'll
move to
Pipfile
.requirements.txt
to avoid confusionREADME.md
buildcheck.yml
to usepipenv
Fixes: #114
Signed-off-by: Daniel Wilms Daniel.DW.Wilms@bmw.de