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.

Sign up for GitHub

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

Jump to bottom

Migrate project to a pyproject.toml based package setup #128

Closed
12 tasks done
Nicoretti opened this issue Apr 7, 2022 · 0 comments · Fixed by #145
Closed
12 tasks done

Migrate project to a pyproject.toml based package setup #128

Nicoretti opened this issue Apr 7, 2022 · 0 comments · Fixed by #145
Assignees
@Nicoretti
Labels
feature Product feature

Comments

@Nicoretti
Copy link
Member

Nicoretti commented Apr 7, 2022 •
edited
Loading

Why

Currently the project packaging, configuration and dependencies are managed using a mix of input sources.
E.g. dependencies are defined in setup.py and in various requirements files (requirements.txt etc.).
Modern python projects use a common "project-file" which takes care about lots of things which have been
done by multiple inputs like (MANIFEST.in, setup.cfg, setup.py, requirements.txt, ...).

Switching to pyproject.toml therefore will simplify maintenance and release efforts of the package.

For further details see also:

Tasks

  • Add pyproject.toml
    • Add requirements
    • Add dev requirements
    • Add extra requirements
    • Add test requirements
  • Add poetry.lock
  • Move configuration(s) into pyproject.toml
    • setup.cfg
    • MANIFEST.in
  • Remove .ptup.yaml
  • Add support for Dependabot
  • Change GH-Action to build and deploy using poetry
@Nicoretti Nicoretti added the feature Product feature label Apr 7, 2022
@Nicoretti Nicoretti self-assigned this May 25, 2022
@Nicoretti Nicoretti mentioned this issue May 30, 2022
Merged
Nicoretti added a commit that referenced this issue Jul 14, 2022
@Nicoretti
Migrate project to pyproject.toml based package setup
ccb6983 
Fixes #128
Fixes #135 

* Add pyproject.toml
* Add poetry lock file
* Add dependencies to pyproject.toml
* Add dependabot updater to repository
* Add pyupgrade commit hook to workspace
* Remove deprecated and unused configuration entries
* Add extension points required for sqlalchemy plugin(s)
* Add version sync support for project.toml based version
* Add version check to ci/verifier action
* Update CI workflow to use poetry
* Update base python version to 3.8
* Update changelog
* Remove condaforge reference in README
   - Conda forge won't be maintained anymore.
* Deleted deprecated and unused files
* Use python built in mock library
* Bump version to 3.0.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Nicoretti Nicoretti

Labels
feature Product feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

#128 migrate project to pyrpoject toml based package setup exasol/sqlalchemy-exasol
1 participant
@Nicoretti