|PyMySQL is looking for a new maintainer||Pete Hunt||5/31/13 7:46 PM|
Hey all -
Time to stop kidding myself that I have enough time to maintain this. Since I stopped using Python at work I haven't really had the time to maintain this package, even though I keep thinking I'd get around to it. And with the release of React (http://facebook.github.io/react) this week it's only going to get harder to find time. I think it's best if I let someone else who's more active take the reins.
Anyone interested? Send me an email (floyd...@gmail.com)
|Re: PyMySQL is looking for a new maintainer||Marcel Rodrigues||8/1/13 7:35 AM|
I'm maintaining a fork of PyMySQL on Github (it's the lecram/PyMySQL repo) that aims to support Python versions 2.6, 2.7 & 3.3. This code base drops support for Python 2.4 & 2.5 but adds true support for 3.3 (it does not use 2to3). The reason for this is that I want to integrate PyMySQL on a project that is written for Python 3. The code on the main repo, petehunt/PyMySQL, is really broken for py3k. Of the total of 72 issues currently open, at least 13 are related to PyMySQL not being compatible with py3k.
As of now, lecram/PyMySQL passes the same tests as petehunt/PyMySQL does, except that it does so for Python 3.3 too. I'm using it on my project with no issues so far. However, there are some pull requests on petehunt/PyMySQL that could be applied to lecram/PyMySQL (with minor corrections to support py3k) and I don't know what's the correct way to merge those specific commits as they weren't submitted as pull requests to my repo.
In summary, this is the situation:
* petehunt/PyMySQL is abandoned but, being the official repo, has all the issues/pull requests that needs to be resolved/merged;
* lecram/PyMySQL is activelly maintained but doesn't support Python versions < 2.6 and, not being the official repo, is not benefiting from community contribution.
I vonlunteer to "take the reins" if everyone agrees to drop support for Python < 2.6 in the official package.
|Re: PyMySQL is looking for a new maintainer||summetj||8/1/13 7:40 AM|
I fully support Marcel taking the reins! (I'm using PyMySQL on a
python3 system...) Seeing as 2.7 is "Production" I don't have a problem
with dropping 2.4/2.5.
> You received this message because you are subscribed to the Google
> Groups "PyMySQL Users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to pymysql-user...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
|Re: PyMySQL is looking for a new maintainer||Patrick Dunnigan||8/1/13 8:16 AM|
I have no problem with dropping support for < 2.6
Thanks for pursuing this. If at some point this becomes "official", don't forget pypi.
|Re: PyMySQL is looking for a new maintainer||mIREK||8/1/13 8:18 AM|
I am using 2.6,2.7 porting some backend scripts to 3.x. So I am for Marcel ;-)
|Re: PyMySQL is looking for a new maintainer||Marcel Rodrigues||8/1/13 9:24 AM|
|Re: PyMySQL is looking for a new maintainer||Pete Hunt||8/1/13 12:18 PM|
|Re: PyMySQL is looking for a new maintainer||Naoki INADA||8/28/13 3:30 AM|
I'm happy about hear new maintainer!
How about making PyMySQL Organization on Github and move your repository to it?
Issues and PRs can be transferred.
2013年8月2日金曜日 4時18分47秒 UTC+9 Pete Hunt:
|Re: PyMySQL is looking for a new maintainer||Marcel Rodrigues||8/29/13 6:48 AM|
I'm aware that PyMySQL still has compatibility issues with newer versions of Django. It would be nice if we could solve this issue before releasing a new version to PyPI.
I have moved my fork to the organization.
This basically means that repository administration doesn't need to be limited to a single person anymore.
Thanks for the suggestions, Naoki.I have just created a PyMySQL organization on GitHub.
Anyone that has created issues or pull requests on github.com/petehunt/PyMySQL is encouraged to resubmit them on github.com/PyMySQL/PyMySQL, if they are still open and relevant.
2013/8/28 Naoki INADA <songof...@gmail.com>
|Re: PyMySQL is looking for a new maintainer||Naoki INADA||8/29/13 9:41 PM|
|Re: PyMySQL is looking for a new maintainer||Marcel Rodrigues||8/30/13 11:14 AM|
B) making the repository the root of the network.
A) detaching the repository from the network;
I was trying to do it the way that requires less actions from Pete, since he's busy.As far as I understand, the message "forked from petehunt/PyMySQL" can be removed in two ways:
In the first case, that message would still appear on other forks. In the second case, the other forks (and even petehunt/PyMySQL) would have the message "forked from PyMySQL/PyMySQL".
Both options would require the intervention of GitHub's staff, and option B would also require that Pete send an email to sup...@github.com requesting to make PyMySQL/PyMySQL the root of the network (it needs to come from him because he is the owner of the current root).
A third option is to move back the fork to my user account and ask Pete to move his repo to the organization, as you suggest. I think that most PRs there conflicts with the code ported to Python 3, and most issues were solved by the port. But sure it would be nice to have the PRs/issues closed accordingly and kept for future reference.
I would like to hear more opinions on all that.
2013/8/30 INADA Naoki <songof...@gmail.com>
|Re: PyMySQL is looking for a new maintainer||Pete Hunt||8/30/13 11:34 AM|
I've sent an email to GitHub to get this process started. Thanks for taking care of it; let me know what else you need from me!
|Re: PyMySQL is looking for a new maintainer||Marcel Rodrigues||9/3/13 8:18 AM|
Hi Pete, thanks for the help.
I've been discussing it with GitHub support and decided that it's better to move your repository (petehunt/PyMySQL) to the organization (PyMySQL), since it's the only way we can keep PRs and Issues. The fork is already back on my user account.
How to do that: go to https://github.com/petehunt/PyMySQL/settings and click on the [Transfer] button next to "Transfer Ownership". Type "PyMySQL" in both fields of the form and submit it.
P.S.: I just noticed that the root of the network has been moved to the fork and we will have to undo that, unfortunately. I will take care of it as soon as the repositories involved are in their right places.
2013/8/30 Pete Hunt <floyd...@gmail.com>
|Re: PyMySQL is looking for a new maintainer||Naoki INADA||9/7/13 2:43 AM|