nexb / dparse2 Goto Github PK

Hi @pombredanne

It's Justin here from PyUp.io. We're on a big push to update our open source libraries, and keep them maintained and improved. This includes dparse, which other libraries like Safety CLI rely on.

I understand the reasons you forked dparse when you did to keep on maintenance and update certain new features. We'll be pushing changes to dparse in the next few weeks and plan on keeping it maintained and improved over time.

I am wondering what the best course of action is regarding dparse2 and dparse. Shall we keep them separate projects, or would it make sense to merge dparse2 back into dparse? I did also notice that you are a collaborator on dparse itself too. I have no agenda here other than wondering what is best to reduce workload and duplicate work.

I look forward to hearing back and seeing how we at PyUp can help here!
Best,
Justin

Involved in aboutcode-org/python-inspector#109, failing test needs a release of dparse2