Re: [Python-Dev] A decade as a core dev
On Apr 18, 2013, at 11:02 AM, Brett Cannon wrote: > Today marks my 10 year anniversary as a core developer on Python. I > wrote a blog post to mark the occasion > (http://sayspy.blogspot.ca/2013/04/a-decade-of-commits.html), but I > wanted to personally thank python-dev for the past decade (and > whatever comes in the future). Wow 10 years that is incredible!! Your blog post was awesome. You are an inspiration to me as I just started contributing this past October. I can honestly see how you have spent 10 years of "spare hours" night time engineering. I find contributing a bit addictive myself. Here is what happens to me at night, on my right shoulder a little Guido appears out of thin air and says "go to bed" but then on my left shoulder another Guido appears and says "all you have to do is test this last patch". Next thing you know it is 2 am and I have to get up at 5 am for work so I convince myself to stay up all night. Indeed contributing to Python is very rewarding. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Our failure at handling GSoC students
On Aug 6, 2013, at 3:26 PM, Antoine Pitrou wrote: > I would like to point out that we currently fail at handling GSoC > projects and bringing them to completion. In the past I have noticed the same thing with IDLE. Students and mentors act outside of the standard Python development process then the final student products never get committed. > One cruel example is the set of PEP 3121 / PEP 384 refactorings done by > Robin Schreiber: > http://bugs.python.org/issue?%40columns=id%2Cactivity%2Ctitle%2Ccreator%2Cassignee%2Cstatus%2Ctype&%40sort=-activity&%40filter=status&%40action=searchid&ignore=file%3Acontent&%40search_text=pep+3121&submit=search&status=-1%2C1%2C3 I agree this is a sad example. > What didn't produce an alarm during Robin's work is that GSoC work is > done in private. Therefore, other core developers than the mentor don't > get to give an advice early, as would happen with any normal proposal > done publicly (on the mailing-list or on the bug tracker). It is also > likely that the mentor gets overworked after the GSoC period is over, > is unable to finalize the patch and push it, and other core devs have a > hard time catching up on the work and don't know So for this year I designed an IDLE project that specifically forced the students to be like normal contributors and use the standard Python development model. See this link for the project description: http://wiki.python.org/moin/SummerOfCode/2013/python-core From the project description: "Successful student proposals should not under estimate how long it takes to get code committed to CPython. A student must be able to concisely communicate and document the unit test framework's design to the Python community in order to get the framework committed to the CPython source tree. Do not underestimate how much time this communication and documentation will actually take in your proposal!!! Often times it will take several passes and several code reviews for a patch to get committed into CPython. This project is approximately 40% coding and 60% communication. This project requires average Python coding skills with excellent communication skills and a unrelenting persistence to get this job done to the satisfaction of at least one Python Core Developer so the work will be committed into the CPython source tree." To date the students have gotten three commits completed and seven total issues opened. Here is a google spreadsheet with the details: https://docs.google.com/spreadsheet/lv?key=0AqHo248BJw3RdFRnREo5TGtrQmxvQi1oem1HUS1PNGc It is too early to tell how effective the students have been. I do wish more unit tests were created but it all takes time to convince a core Python developer to make the commit (and with good reason). In this case Terry Reedy has been a huge help! I think the students are having fun and hopefully will stay involved for years to come. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Completed: Google Summer of Code 2013 IDLE Unit Testing and Improvements
In April 2013 we challenged students to not spend their summer idle around the swimming pool but rather spend their time on IDLE and make a difference. IDLE is Python’s Integrated Development Environment (IDE) that is shipped with each Python release (http://en.wikipedia.org/wiki/IDLE_(Python)). Since IDLE ships with Python it is often the first IDE a new Python programmer uses. The Python development community wants to make IDLE an awesome experience especially for people that are learning Python. Despite the fact that IDLE originally shipped in 1998 it had no unit test cases, making it difficult to confidently update the code and ship new versions. For this Google Summer of Code project our students Jayakrishnan Rajagopalasarma (http://123works.blogspot.com/search/label/GSoC%202013) and Phil Webster (http://weblog.philwebster.net/tag/gsoc/) had to not only create the unit tests but assist with design of the unit test framework (http://bugs.python.org/issue15392). By the end of the summer of 2013 Phil and Jayakrishnan have worked on five patches that have been committed to the CPython open source project. In addition the team has started work on an additional five issues (at bugs.python.org) but have not completed them yet. Jayakrishnan explored an idea to add automatic PEP8 checking to IDLE http://bugs.python.org/issue18704. Our hope is that both JayKrish and Phil continue to contribute to Python even now that GSoC is complete. The team wishes to thank Google and the Python Software Foundation for this opportunity to contribute to Python. Thanks to all the Python Core Developers that helped review and commit issues for the students. Special thanks goes to Terry Reedy who provided outstanding feedback on issues and performed all of the student’s commits. Finally thanks to Terri Oda for being a great GSoC administrator for the Python Software Foundation and helping by assigning an awesome co-mentor J.H. Hawley. The complete list of closed issues is below: http://bugs.python.org/issue18279 http://bugs.python.org/issue18189 http://bugs.python.org/issue18425 http://bugs.python.org/issue18226 http://bugs.python.org/issue18489 The complete list of started issues is below: http://bugs.python.org/issue18292 http://bugs.python.org/issue18910 http://bugs.python.org/issue18409 http://bugs.python.org/issue18410 http://bugs.python.org/issue18592 ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Please review simple patch for IDLE documentation last updated 11/28/2012
Greetings, I submitted a simple patch for updates to IDLE's documentation http://bugs.python.org/issue5066 and it has not been reviewed by an official Python developer. Since it is now been over 1month since last update can somebody please review and or commit? I did get some comments from another contributor and updated the patch based on those comments. The original bug was opened in 2009 and the IDLE documentation is out of date with undocumented menu options and inconsistencies between the help file and the HTML documentation. I hate to be pushy but I would like to see some progress made on IDLE. Thanks for the support. Sent from my iPad___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Please review simple patch for IDLE documentation last updated 11/28/2012
On Jan 4, 2013, at 10:23 AM, "R. David Murray" wrote: > On Fri, 04 Jan 2013 10:04:14 -0500, Todd V Rovito wrote: >> I submitted a simple patch for updates to IDLE's documentation >> http://bugs.python.org/issue5066 and it has not been reviewed by >> an official Python developer. Since it is now been over 1month >> since last update can somebody please review and or commit? I >> did get some comments from another contributor and updated the >> patch based on those comments. The original bug was opened in >> 2009 and the IDLE documentation is out of date with undocumented >> menu options and inconsistencies between the help file and the >> HTML documentation. I hate to be pushy but I would like to see >> some progress made on IDLE. Thanks for the support. > > IMO it isn't pushy to ask about an issue that seems ready but on which > no action has been taken for an extended period. It could be that the > nosy committers have just forgotten about it. > > In the future, it best way to approach this situation (patch that seems > ready but no action has been taken) is to ping the issue first, and if > you don't get a response after a few days, to post here as you did. Good suggestion I will "ping" the bug report! FYIthe excellent developer's guide http://docs.python.org/devguide/patch.html#reviewing states "Getting your patch reviewed requires a reviewer to have the spare time and motivation to look at your patch (we cannot force anyone to review patches). If your patch has not received any notice from reviewers (i.e., no comment made) after a substantial amount of time then you may email python-dev@python.org asking for someone to take a look at your patch." The Developer's guide does not mention pinging the patch maybe that is common sense so it doesn't need to be documented but I had assumed somebody was watching bugs that had patches applied but no commits. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Please review simple patch for IDLE documentation last updated 11/28/2012
On Jan 4, 2013, at 11:51 AM, "R. David Murray" wrote: > On Fri, 04 Jan 2013 10:40:10 -0500, Todd V Rovito wrote: >> On Jan 4, 2013, at 10:23 AM, "R. David Murray" wrote: >> >>> On Fri, 04 Jan 2013 10:04:14 -0500, Todd V Rovito >>> wrote: >>>>I submitted a simple patch for updates to IDLE's documentation >>>>http://bugs.python.org/issue5066 and it has not been reviewed by >>>>an official Python developer. Since it is now been over 1month >>>>since last update can somebody please review and or commit? I >>>>did get some comments from another contributor and updated the >>>>patch based on those comments. The original bug was opened in >>>>2009 and the IDLE documentation is out of date with undocumented >>>>menu options and inconsistencies between the help file and the >>>>HTML documentation. I hate to be pushy but I would like to see >>>>some progress made on IDLE. Thanks for the support. >>> >>> IMO it isn't pushy to ask about an issue that seems ready but on which >>> no action has been taken for an extended period. It could be that the >>> nosy committers have just forgotten about it. >>> >>> In the future, it best way to approach this situation (patch that seems >>> ready but no action has been taken) is to ping the issue first, and if >>> you don't get a response after a few days, to post here as you did. >> >> Good suggestion I will "ping" the bug report! FYIthe excellent >> developer's guide http://docs.python.org/devguide/patch.html#reviewing >> states "Getting your patch reviewed requires a reviewer to have the >> spare time and motivation to look at your patch (we cannot force >> anyone to review patches). If your patch has not received any notice >> from reviewers (i.e., no comment made) after a substantial amount of >> time then you may email python-dev@python.org asking for someone to >> take a look at your patch." >> >> The Developer's guide does not mention pinging the patch maybe that is >> common sense so it doesn't need to be documented but I had assumed >> somebody was watching bugs that had patches applied but no commits. > > Adding that to the developers guide sounds like a good idea. You could > open a new issue in the tracker with that suggestion :). Thanks I will add an issue to the tracker and will even submit a patch. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
