➜

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 carljm
Recipients BTaskaya, Peter Ludemann, carljm, corona10, eric.snow, gregory.p.smith, gvanrossum
Date 2020-04-30.03:14:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1588216458.8.0.841444663406.issue40360@roundup.psfhosted.org>
In-reply-to
Content 
Right, although I think it still makes sense to link both LibCST and parso since they provide different levels of abstraction that would be suitable for different types of tools (e.g. I would rather write an auto-formatter on top of parso, because LibCST's careful parsing and assignment of whitespace would mostly just get in the way, but I'd rather write any kind of refactoring tooling on top of LibCST.)

Another tool that escaped my mind when writing the PR that should probably be linked also is Baron/RedBaron (https://github.com/PyCQA/redbaron); 457 stars makes it slightly more popular than LibCST (but it's also been around a lot longer.)
History
Date User Action Args
2020-04-30 03:14:18carljmsetrecipients: + carljm, gvanrossum, gregory.p.smith, eric.snow, corona10, BTaskaya, Peter Ludemann
2020-04-30 03:14:18carljmsetmessageid: <1588216458.8.0.841444663406.issue40360@roundup.psfhosted.org>
2020-04-30 03:14:18carljmlinkissue40360 messages
2020-04-30 03:14:18carljmcreate