You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Converted project from using pipenv to poetry (#98)
* Added pyyaml package to Pipfile
Encountered an issue using `pipenv` after installing the
packages associated with the project for a missing package.
* Converted from pipenv to poetry
The Dockerfiles have also been modified using the recommended
install directions from the Poetry docs versus using pip to install
poetry.
* Updated Makefile for builds
* Traced remaining references to pipenv in project
Updated workflows in project to use Poetry. Changed portions of
documentation to reflect change to poetry.
* Updated workflows to use poetry post-install
While poetry was successfully installing during the build, it was
not loaded into the current environment's `PATH`s so this adds the
command to load `poetry` into the active environment.
* Updated linter to use modules imported via poetry
`pipenv` with the `--system` argument was allowing for the packages
to be installed at the system level versus in a virtualenv which
resulted in `isort` throwing an error that the command did not exist.
The workflow has been modified to invoke poetry to utilize `isort` and
`black`.
Additionally, the `setup.py` and `setup.cfg` files have been re-added
back into this branch for compatibility.
* Changed poetry to export requirements.txt for builds
Using `pip` to install packages from poetry during build steps versus
trying to use the venv since the venv is not being used post-install
of packages through `poetry`
* Linter modified cloudendure.py formatting
* Fixed version and author information
Added the appropriate `authors` and `version` to the
`pyproject.toml` file for the project.
* Versioned to 0.2.0
Bumped the version to `0.2.0` with the assumption that moving from
`pipenv` to `poetry` is an impactful change to the project but
not a breaking change to how the `cloudendure` module functions.
The above context is driven using [Semantic Versioning](https://semver.org/).
* Fixed poetry build and other recommendations applied
- Cleaned up `setup.py` and `setup.cfg`
- This was cruft left for mid-troubleshoot to resolve testing
- Updated `Makefile` to use `poetry build` and `poetry publish`
for project builds
- Updated `API_README.md` in `docs` to reflect the change to the
`poetry` from `pipenv`
* Ported items from original config to toml file
- Added `include`s for:
- `CHANGELOG.md`
- `CODE_OF_CONDUCT.md`
- `REFERENCE.md`
- `SECURITY.md`
- Cleaned up error in `tool.poetry.dependencies` attempting
to reference the project itself
- `console scripts` have been ported for `cloudendure` and `ce`
commands
- `tool.isort` and `tool.yapf` sections from the original `setup.cfg`
have been ported to the toml file
* Added trailing comma to list in toml file
* Preparation for moving to poetry from pipenv
0 commit comments