Skip to content
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

Merged
merged 2 commits into from
Jan 11, 2022

Conversation

danielwilms
Copy link
Contributor

Until now dependencies were defined in two separate files
(requirements.txt and Pipfile). As decided in #114 we'll
move to Pipfile.

  • removed requirements.txt to avoid confusion
  • removed section from README.md
  • changed buildcheck.yml to use pipenv

Fixes: #114

Signed-off-by: Daniel Wilms Daniel.DW.Wilms@bmw.de

Copy link
Contributor

@barbieri barbieri left a 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

.github/workflows/buildcheck.yml Outdated Show resolved Hide resolved
.github/workflows/buildcheck.yml Show resolved Hide resolved
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>
@danielwilms
Copy link
Contributor Author

@barbieri, I changed the python version in a separate commit, but in the same PR. Please have a look, if now everything is resolved.

Pipfile Show resolved Hide 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>
Copy link
Collaborator

@SebastianSchildt SebastianSchildt left a 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 👍

@danielwilms
Copy link
Contributor Author

meeting 11/01/2022: approved to be merged @erikbosch

@erikbosch erikbosch merged commit 2ffa9d2 into COVESA:master Jan 11, 2022
danielwilms added a commit to danielwilms/vehicle_signal_specification that referenced this pull request Jan 12, 2022
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>
danielwilms added a commit to danielwilms/vehicle_signal_specification that referenced this pull request Jan 12, 2022
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>
danielwilms added a commit to danielwilms/vehicle_signal_specification that referenced this pull request Jan 12, 2022
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>
danielwilms added a commit to COVESA/vehicle_signal_specification that referenced this pull request Jan 18, 2022
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Move to Pipfile
4 participants