Skip to content
This repository has been archived by the owner on Sep 17, 2018. It is now read-only.

Python 2 to 3 Porting Plans #312

Open
JnyJny opened this issue Aug 18, 2018 · 3 comments
Open

Python 2 to 3 Porting Plans #312

JnyJny opened this issue Aug 18, 2018 · 3 comments

Comments

@JnyJny
Copy link

JnyJny commented Aug 18, 2018

Does this project have a plan for migrating to Python 3? Python 2 will be EOL in a little over a year, see https://pythonclock.org for the exact time left.

@ascott1
Copy link
Member

ascott1 commented Aug 20, 2018

Hi @JnyJny, we are migrating away from the use of this parser. As such, it is unlikely that we'll be transitioning to Python 3 for this project.

You may want to inquire at the forked project https://github.com/eregs/regulations-parser, which may have an ongoing support/implementation plan.

@JnyJny
Copy link
Author

JnyJny commented Aug 20, 2018

Thanks for getting back to me, I stumbled on the eregs project soon after opening this issue. What new parser are you migrating too? Thanks for the good work, btw.

@ascott1
Copy link
Member

ascott1 commented Aug 20, 2018

The parser we are migrating to is part of our cfgov-refresh project. A few important notes:

  • It is also currently Python 2
  • This extracts less informataion from the eCFR XML
  • Its is tightly coupled to the models of our application
  • It parses to a human readable Markdown-like format

I hope that proves useful!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants