enthought / enthought/comtypes

Modernising the dev tooling

Open
#480 16 comments 2 reactions 0 assignees View on GitHub
coding style help wanted shared_info tests
Dominant language
Python
Stars
345
Forks
105
PR merge metrics
No merged PRs in 30d

Description

Hello `comtypes`ers,

As `comtypes` is currently experiencing a new lease of life (thanks particularly to the efforts of @junkmd), I wanted to gauge the level of interest from contributors in adding in new tooling to support the development process. There is now such a rich ecosystem of packaging tools including things like `tox`/`nox` for isolating and automating test builds, formatters like `black` (that can be run with `pre-commit`), linters like `pylint` or `ruff`, `setuptools_scm` for version management, and `towncrier` for generating the changelog.

While I am not suggesting the immediate or wholesale adoption of all these options, I think that incorporating some of these tools could make the development process easier for new contributors to get started with, and probably simplify things for everybody. However, I realise that this would also require a certain amount of work, and also some discussion to try and achieve consensus on what tools to use, and that may not appeal to everyone involved. So I decided to open this issue to see whether I get enthusiastic support, naked hostility, or studied indifference. Let me know what you all think...

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.