-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package distribution #20
Comments
@alexei - Are there issues in particular that you want addressed? @bryanhelmig - Happy to own repo and maintain. |
We have some issues with messages sent from Live email accounts (I think) that do not get parsed at all. The original message is not quoted in any way (i.e. no >) albeit the headers are included so I guess that's the culprit. I think this DisruptiveLabs@6eac05f addresses that issue. Besides that, the package published on PyPI hasn't been updated for a while. |
Seems like we ought to at least bring in #19. Also, perhaps it is appropriate for a @kageurufu would you be open to maintaining? |
I'd be happy to maintain this if you want Also @alexei, our fork is currently on pypi as py-email_reply_parser. |
Awesome, I added you @kageurufu - let me know if you want me to push a new version to PyPi, we can look into some automated way to do that too. (Maybe via Travis? Not sure.) |
https://docs.travis-ci.com/user/deployment/pypi is an easy way to turn that on, I'll go ahead and close #19, branch our changes seperately from readme/setup.py changes, and create a new PR for that. |
Awesome! |
Guys, you are amazing! Thank you for the positive and quick response! |
v0.5.9 is now deployed on pypi, enjoy! |
Awesome, thanks! |
I gather this package is no longer maintained by it's original authors. I think every user would benefit if either Zapier transferred ownership to another developer or one of the contributors (e.g. @DisruptiveLabs) renamed their fork and published it on PyPI.
Thoughts?
The text was updated successfully, but these errors were encountered: