Yes, I think so. We should probably spend some time on getting ruff/black/whatever into the system sooner then.
Thanks > On Jun 5, 2025, at 8:32 AM, Nick Dimiduk <ndimi...@apache.org> wrote: > > I'm in favor of meeting the community where they're going. I assume > that means that the community will work out the migration path from > pylint to the applicable new tools. As long as we provide a release > with overlap of old and new, that should be enough for users to make a > seamless migration, right? > > Thanks, > Nick > > On Thu, Jun 5, 2025 at 5:03 PM Allen Wittenauer <a...@apache.org> wrote: >> >> >> Hey gang. >> >> Our version of pylint is getting long in the tooth and is starting to >> suffer from compabitlity issues with newer version fo Python. One of the >> nice things about the version we are running is that it does support some >> code formatting things. The newer versions remove that capability. As a >> result, upgrading our version of pylint is going to cause feature loss. >> >> The other semi-related thing is that the Python community has started >> to move towards black for formatting and ruff as a replacement for general >> pylint stuff. So we could “fix” the pylint issue by replacing it wholesale >> with two different tools. >> >> Anyone have any thoughts about what we should do here? Python 3.13 >> is still very much in early adopter phase but it will pick up. We should be >> ready for it. >> >> Thanks. >>
