This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mdk
Recipients AlexWaygood, erlendaasland, georg.brandl, lukasz.langa, mdk, ned.deily, pablogsal, rhettinger, vstinner, willingc
Date 2022-01-25.08:38:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1643099913.38.0.273706408742.issue42238@roundup.psfhosted.org>
In-reply-to
Content
I slowly started to work on rstlint in its own tree because working in a single file felt inconfortable.

The more I advanced in this direction the more it made sense to me:

- I first added tests, I may have been able to do so in the cpython tree though.
- It would ease the publication of it to pypi.org so it can be used by other projects.
- It may ease contributions (some non-core-devs could be given rights to the repo, which make sense as it's not really Python related but more Sphinx related).

It currently looks like this: https://github.com/JulienPalard/sphinxlint but should obviously be moved to github.com/python/ if we adopt this direction.

So what do you think? (cc Georg as the main author of the script)

If so I'd also like to rename the thing, it's currently named `rstlint`, but it's more a `sphinxlint` as Sphinx has adds a lot to rst and existing rst linters does not handle Sphinx well.
History
Date User Action Args
2022-01-25 08:38:33mdksetrecipients: + mdk, georg.brandl, rhettinger, vstinner, ned.deily, lukasz.langa, willingc, pablogsal, erlendaasland, AlexWaygood
2022-01-25 08:38:33mdksetmessageid: <1643099913.38.0.273706408742.issue42238@roundup.psfhosted.org>
2022-01-25 08:38:33mdklinkissue42238 messages
2022-01-25 08:38:33mdkcreate