You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be nice to expose the functionality of qweechat.weechat.parser to the world and allow others to use it in their own Python programs.
First, I'd recommend reviewing the code and updating it to work with Python 3, which I'm happy to do. I've got a working version exclusively for Python 3 locally, which I can tweak to make it compatible with Python 2.6+.
After that, it's just a matter of separating it out into a new repo (maybe named pyweerelay, pyweechat or python-weechat-relay), creating a PyPI package for it and adding that package as a dependency of qweechat.
The text was updated successfully, but these errors were encountered:
Yes, agreed to make a separate package. I'm currently working on a C library to decode the WeeChat relay protocol (to use in WeeChat itself, see weechat/weechat#369).
So having same package in python would be great, and I can work on that.
For the support of Python versions, I think 2.6 is really not needed (too old). We could maybe keep 2.7+, and of course fully support Python 3.x.
Great! Want me to clean up my Python 3 port? Not having to keep backwards compatibility with 2.6 will make things easier, since I'm not sure what's in 2.6's __future__ module and what's not.
It'd be nice to expose the functionality of
qweechat.weechat.parser
to the world and allow others to use it in their own Python programs.First, I'd recommend reviewing the code and updating it to work with Python 3, which I'm happy to do. I've got a working version exclusively for Python 3 locally, which I can tweak to make it compatible with Python 2.6+.
After that, it's just a matter of separating it out into a new repo (maybe named
pyweerelay
,pyweechat
orpython-weechat-relay
), creating a PyPI package for it and adding that package as a dependency of qweechat.The text was updated successfully, but these errors were encountered: