Closed qidanrui closed 2 years ago
It's pretty sad around here:
This was a really great library and one that my organization depended on for parsing attorney addresses. Unfortunately, unless it's maintained somehow, we'll have to drop support for the feature, which is a bummer.
Is there any way we can get this moving again? @fgregg, maybe you have some ideas? I'd offer to take over the package at FLP, but we don't really have the expertise.
I think all it really needs is a fix to the crfsuite thing and a few tweaks to anywhere it mentions python 2.7, and it'd be ready to roll.
hi @mlissner , i like and have appreciated our personal interactions , so your message that this project is disappointing you hurt my feelings. the package has worked for years with python 3. if it has stopped recently, that would be good to know, but your message has been very demotivating
Sorry, I don't mean to lay out all these problems and insult the good work here, but at the same time, it does look like the project is abandoned. There are a number of bugs, PRs, and forks related to python 3, and there hasn't been a commit here for four years aside from a readme tweak.
I'd love to get this fixed up again, but it's not an area where I have expertise. Usually that's what I do when something I rely on breaks or needs a tweak, but I can't do that here, I don't think.
What's a better way forward if the project is still maintained?
If you don't like this state of the project, you are always welcome to fork the project. If that does not work for you, Court Listener can sign a contract with DataMade to get some of your high priority issues addressed.
That might work. I'll get in touch via email.
3,10 works now
The usaddress library only supports Python 2.7, which is because the
probableparsing
library only support Python 2.7 (https://pypi.org/project/probableparsing/). Remove this library or incorporate the code ofprobableparsing
will solve this problem and make usaddress support Python 3.x.