Jason R. Coombs
Jason R. Coombs
Have a look at https://github.com/jaraco/skeleton/issues/48#issuecomment-808551034 for reasons why the plugin is useful to me over a simple executable.
I have a similar issue. I've worked around the issue by using [pytest-enabler](https://pypi.org/project/pytest-enabler/). See https://github.com/jaraco/skeleton/blob/aae281a9ff6c9a1fa9daad82c79457e8770a1c7e/pyproject.toml#L16-L17. This plugin allows `pytest-flake8` to be enabled when the plugin is enabled, but not when...
I would recommend against Appveyor and Microsoft Azure. I've used all three and Github Actions is the most mature, cross-compatible, and straightforward to support.
Adding `# type: ignore` after the class definition of the `Referenceable` subclass seems to suppress the error.
Dupe of #17
See pypa/setuptools#1688 for the discussions on supporting pyproject.toml.
In this proposal, the most minimal `bump2version` config would be `null` - that is, since the version is declared and stored and used by `metadata.version` and `bump2version` bumps that canonical...
This is related to peritus/bumpversion#198.
Any comments? Would a PR be accepted for this feature as proposed (supporting metadata.version as the default current version)?
I've done some initial investigation on this proposal, and I realize right away that it's not straightforward... because it's not just the metadata.version that needs to be read, but also...