Differences between revisions 68 and 69

Google Python Sprint 2007

If you plan or hope to attend, please sign up below so we can have your badge ready at the lobby. (Googlers: please sign up so we can plan the space accordingly.)

When: August 22-25, 9:30 am - 5:30pm local time
Where:
- Mountain View Google Campus - University Theater Bldg 40
- Chicago Google Engineering office

For more information on the Chicago sprint, see http://mail.python.org/pipermail/chicago/2007-August/002401.html

Goals and Suggested Sprint Areas

The primary focus will be on getting new features into 3.0 before the first alpha. We hope to have a solid, stable and reasonably complete 3.0a1. You can make this happen and have fun doing it! Come join us.

Some suggestions:

Python 3000 (for tasks and status, see ["Python3000"])
Cleanup for 2.6/3.0 transition
Documentation for the transition
Add fixers to the 2to3 tool
Add your ideas here

Attendees Sign Up Here

Name	Dates	Location	Googler?
Neal Norwitz	22-25	MTV	Yes
Guido van Rossum	22-24	MTV	Yes
Talin	22-25	MTV	Yes
Collin Winter	22-25	MTV	Yes
Alex Martelli	?????	MTV	Yes
Brian Fitzpatrick	?????	CHI	Yes
Skip Montanaro	?????	CHI	No

Food

We'll be providing lunch and dinner to our attendees and breakfast will be available from the micro-kitchens. Our guests will dine with us in our cafes for their meals.

Housing - MTV

You can book a room at The Residence Inn Palo Alto/Mountain View; ask for Google's corporate rate. If you're looking to save funds, you might consider booking a penthouse room at the property and doubling up with another attendee. http://marriott.com/property/propertypage.mi?marshaCode=SFOMV

Security - MTV

Badges will be provided to all attendees. Please wear them at all times.

Come Prepared!

Please come prepared so we won't have to waste time helping everybody with their setup. Bring a laptop (preferably running Linux or OSX; we have limited svn setup experience for other systems, esp. Windows). Make sure svn is installed: http://subversion.tigris.org/ -- Check [http://prolificprogrammer.com/~hdiwan/blog/2006/08/02/home_subversion_repository_1.html Hasans Blog Entry on subversion ] for help with other systems.

For Python 2.6, check out the head branch; see http://www.python.org/dev/faq/#subversion-svn (use the instructions for anonymous checkout unless you already have developer privileges).

For py3k, check out the "py3k" branch. Also read PEPs 3000-3999.

In either case, make sure you have at least built and tested it once so you are familiar with the process. It's something like "./configure; make; make test" in the appropriate directory. (For Py3k, half a dozen tests typically fail -- a goal of the sprint will be to fix these.)

Questions

Are you guys on IRC, Google Talk, or something like that? Answer: no IRC AFAIK; some individuals can be IM'ed in gmail chat, e.g. gvanrossum@gmail.com, nnorwitz@gmail.com.

-  ⇤ ← Revision 68 as of 2007-08-13 17:06:55 → 
  Size: 3972
  Editor: 65
  Comment:
+   ← Revision 69 as of 2007-08-13 17:17:01 → ⇥
  Size: 3900
  Editor: 65
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 9:
-  * Who: Neal Norwitz, Talin, Alex Martelli, Collin Winter, Guido van Rossum (Mountain View); Brian Fitzpatrick (Chicago)
  * What: Python 3000 primarily
-Line 21:
+Line 19:
+  * Documentation for the transition
  * Add fixers to the 2to3 tool
 Line 71:
-For Python 2.5/2.6, check out the head branch; see http://www.python.org/dev/faq/#subversion-svn (use the instructions for anonymous checkout unless you already have developer privileges).
+For Python 2.6, check out the head branch; see http://www.python.org/dev/faq/#subversion-svn (use the instructions for anonymous checkout unless you already have developer privileges).
 Line 73:
-For py3k, check out the "py3k-struni" branch.  Also read PEPs 3000-3999.
+For py3k, check out the "py3k" branch.  Also read PEPs 3000-3999.
 Line 75:
-In either case, make sure you have at least built and tested it once so you are familiar with the process.  It's something like "./configure; make; make test" in the appropriate directory.  (For Py3k, 25 or so tests typically fail -- a goal of the sprint will be to fix these.)
+In either case, make sure you have at least built and tested it once so you are familiar with the process.  It's something like "./configure; make; make test" in the appropriate directory.  (For Py3k, half a dozen tests typically fail -- a goal of the sprint will be to fix these.)
 Line 79:
-Are you guys on IRC, Google Talk, or something like that?  Answer: no IRC AFAIK; some individuals can be IM'ed in gmail chat, e.g. gvanrossum@gmail.com.
+Are you guys on IRC, Google Talk, or something like that?  Answer: no IRC AFAIK; some individuals can be IM'ed in gmail chat, e.g. gvanrossum@gmail.com, nnorwitz@gmail.com.

Page

User