|
|
|
|
|
by kerkeslager
4083 days ago
|
|
Paul, I already emailed you but I'm responding here because I have a feeling your response will be useful to other people interested in helping: could you give some direction for people like me who know Python 2 and/or 3 and want to help, but don't know the first thing about the structure of Debian packages or how they are developed? For example: I'm looking at ./main/f/flask-wtf/flask-wtf_0.10.2-1.json and I'm not even sure what I'm looking at. The contents of that file are: {"has_python3_module": false, "canidate": true, "trove_python3": true, "has_python2_module": true}
What's all that mean?On my machine `apt-cache search flask-wtf` finds a package called `python-flaskext-wtf`. Digging deeper with `apt-cache showpkg` I find the homepage http://packages.python.org/Flask-WTF/, which in turn gets me to the code https://github.com/lepture/flask-wtf. I haven't updated the code to Python 3, but let's assume for a second that I have: now what? How do I tie this all together? Do I just send you a patch for this code? Is this even the right code? If you point me in the right direction I'll be happy to write up a tutorial to help other folks contribute. And as a side note: I really like Hy. |
|
has_python2_module: is a python2 package
has_python3_module: is a python3 package
trove_python3: Is is declared as python3 ready in Pypi ?
canidate: Python 3 module already there and Python 3 compatible on Pypi
I published it as a csv to better understand the situation: https://github.com/mdamien/mdamien.github.io/blob/master/sta...