Differences between revisions 7 and 113 (spanning 106 versions)
Revision 7 as of 2006-06-12 22:44:55
Size: 2373
Editor: 65
Comment:
Revision 113 as of 2007-08-21 17:23:51
Size: 7450
Editor: 65
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Given the recent spate of successful sprints, Google decided it would be a good idea to host a sprint. We've been talking about it since PyCon. Jeremy finally got the ball rolling. = Google Python Sprint 2007 =
Line 3: Line 3:
We plan to hold the sprint Aug 21-24, 2006. This date should be after 2.5 is released (early August). There will be 2 locations: Google's New York City office (NYC), and Google's Mountain View, California office (MTV). Google's Open Source Program Office is doing much of the internal coordination with Jeremy Hylton and Neal Norwitz handling more of the technical side. We hope many Googlers and non-Googlers will participate. Please add your name below if you are interested. ''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.)''
Line 5: Line 5:
The goals of the sprint have not yet been defined. We should try to fix any serious 2.5 bugs as well as cleanup the code to prepare for 2.6. Let us know if you have any questions.   * When: August 22-25, 9:30 am - 5:30pm local time
  * Where:
    * Mountain View Google Campus - University Theater Bldg 40
    * Chicago Google Engineering office
    * (Sorry, no Kirkland or New York sprints this year.)

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.

'''Tasks''' are now written up in an online spreadsheet:
http://spreadsheets.google.com/pub?key=pBLWM8elhFAmKbrhhh0ApQA

---- /!\ '''Edit conflict - other version:''' ----
Please don't edit the list here, it will disappear.
----
Is this spreadsheet supposed to be globally editable? If so, please enable editing by skip.montanaro@gmail.com. Thx... -- SkipMontanaro

Some suggestions:
  * Cleanup for 2.6/3.0 transition
  * Documentation for the transition
    * Convert PEPs to docs
    * Get new-style classes into the official docs
  * Add fixers to the 2to3 tool
  * Expand the SSL support in the socket module to do server-side
  * Add multipart/related support to the email package

Python 3 ideas:
  * Run 2to3 over a variety of packages and look for problems with the output (and ways it can be improved).
  * Convert the last remaining old-style tests to use unittest.
  * Add support for `__trunc__` and `trunc()`.
  * Update the docs for [http://www.python.org/dev/peps/pep-3135/ PEP 3135] and others (basically, reverse engineer what the code does and sync the PEPs up with that).
  * Hunt down deprecated code and docs and remove it.
  * Take a module's documentation and make sure it still applies (not terribly sexy, but incredibly valuable).
  * Get rid of `__mod__` and `__divmod__` methods on float objects.
  * 2to3 fixers: new metaclass syntax (PEP 3115); change `type(x) == int` into `isinstance(x, int)`.

---- /!\ '''Edit conflict - your version:''' ----

---- /!\ '''End of edit conflict''' ----
Line 8: Line 49:
Attendees:
  || Name || Location || Dates ||
  || Jeremy Hylton || NYC || Aug 21-24 ||
  || Neal Norwitz || NYC? || Aug 21-24 ||
  || Guido van Rossum || MTV || Aug 21-24 ||
== Attendees Sign Up Here ==
Line 14: Line 51:
Suggested sprint areas:
  * 2.5 bug fixing
  * Cleanup for 2.6
  * New features for 2.6 (PEP may be required)
  * Python 3000
  * Add your ideas 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 || 22-24 halftime, 25 fulltime || MTV || Yes ||
  || Brian Fitzpatrick || 22-25 || CHI || Yes ||
  || Skip Montanaro || 22-24 || CHI || No ||
  || Hasan Diwan || all days (evenings only) || MTV || NO ||
  || Brett Slatkin || 22-?? || MTV || Yes ||
  || Atul Varma || 23 || CHI || No ||
  || Anrew Wilson || 23 || CHI || No ||
  || Jono DiCarlo || 23 || CHI || No ||
  || Adrian Holovaty || 23 || CHI || No ||
  || Paul Smith || 23 || CHI || No ||
  || Cosmin Stejerean || 22-25 || CHI || No ||
  || Rob Kapteyn || 22-25 || CHI || No ||
  || Paul Lucas || 22-25 || MTV || No ||
  || Jason Prado || 22-23 || MTV || No ||
  || Anna Ravenscroft || 22-25PT || MTV || No ||
  || Keith Dart || 22-25 PT || MTV || Yes ||
  || Gregory P. Smith || 22,24 maybe 25 || MTV || Yes ||
  || Bill Janssen || ????? || MTV || No ||
  || Larry Hastings || 22-25 || MTV || No ||
  || Paul F. Dubois || 22-25 || MTV || No ||
  || Dobromir Montauk || 23PT || MTV || Yes ||
  || Alex Booth || 23PT || MTV || Yes ||
  || Molly Aplet || 23PT || MTV || Yes ||
  || Mikeal Rogers || 22-?? || MTV || No ||
  || Daniel Corson || 22-25 || MTV || No ||
  || Arif B Abdullah || 24-25 || MTV || No ||
  || Yuri Ginsburg || 22-25 (afternoons) || MTV || No ||
  || Ero Carrera || 22-25 || MTV || No ||
  || Benjamin Aranguren || 24-25 || MTV || No ||
  || Christopher Burns || 22-24, 25? || MTV || No ||
  || Tom Waite || 22-24, 25? || MTV || No ||
  || Thuon Chen || 22 (afternoon) 23-25 || MTV || No ||
  || John Reese || 22-? || MTV || Yes ||
  || Jacques Frechet || 22 || MTV || 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
Line 22: Line 101:
'''Administriva for Our Guests''' == Security - MTV ==
Badges will be provided to all attendees. Please wear them at all times.
Line 24: Line 104:
We're planning to feed you and provide network connectivity. We're also planning a Googler/Python Devs cocktail hour. == More on Location ==
Line 26: Line 106:
Google would like to invite you to give a presentation to our employees if you are interested.
  || Name || Location || Dates || Topic ||
=== Mountain View ===
1600 Amphitheatre Parkway, CA 94043;
University Theatre - 2nd Flr, Building 40
Line 29: Line 110:
Google would love to give a presentation to attendees if you're interested. Directions: [WWW] http://www.google.com/corporate/address.html#directions
Guests are welcome to arrive any time after 9:30 AM.
Line 31: Line 113:
  || Name || Location || Dates || Topic || (Non-Googlers: please go to the Building 40 reception and let the receptionist know you are here for the Python Sprint and you will receive a badge.)

=== Chicago ===

Chicago Sales & Engineering Office,
20 West Kinzie St.,
Chicago, IL 60610

More info: http://www.google.com/corporate/address.html
Line 34: Line 124:
'''Food''' == Come Prepared! ==
Line 36: Line 126:
We'll be providing lunch and dinner to our attendees and breakfast will be available from the microkitchens. 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.
Line 38: Line 128:
'''Housing''' 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 40: Line 130:
You'll be able to reserve hotel rooms in both NYC and MTV at Google's corporate rate. Details to follow. For py3k, check out the "py3k" branch. Also read PEPs 3000-3999.
Line 42: Line 132:
'''Security''' 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 44: Line 134:
We will pre-register you with security for both offices. Please make sure to get your name on the attendee list so we can get you pre-registered. More details to follow. === Questions ===
Line 46: Line 136:
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.
Line 47: Line 138:
'''More on Location''' Various [http://freenode.net/ Freenode IRC] channels appear to be unused: #py3k, #pysprint, #sprynt, etc.. I could register one if there was interest, but it's not strictly required. --pfein on irc://irc.freenode.net
Line 49: Line 140:
''New York City''

Connection Machine - Floor 16

''Mountain View''

University Theatre - 1st Flr, Building 40

(please note - only reserved until 2:30 PM on Thursday, 8/24 - do we need another room?)
I suspect #python-dev would be sufficient. -- SkipMontanaro

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
    • (Sorry, no Kirkland or New York sprints this year.)

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.

Tasks are now written up in an online spreadsheet: http://spreadsheets.google.com/pub?key=pBLWM8elhFAmKbrhhh0ApQA


/!\ Edit conflict - other version:


Please don't edit the list here, it will disappear.


Is this spreadsheet supposed to be globally editable? If so, please enable editing by skip.montanaro@gmail.com. Thx... -- SkipMontanaro

Some suggestions:

  • Cleanup for 2.6/3.0 transition
  • Documentation for the transition
    • Convert PEPs to docs
    • Get new-style classes into the official docs
  • Add fixers to the 2to3 tool
  • Expand the SSL support in the socket module to do server-side
  • Add multipart/related support to the email package

Python 3 ideas:

  • Run 2to3 over a variety of packages and look for problems with the output (and ways it can be improved).
  • Convert the last remaining old-style tests to use unittest.
  • Add support for __trunc__ and trunc().

  • Update the docs for [http://www.python.org/dev/peps/pep-3135/ PEP 3135] and others (basically, reverse engineer what the code does and sync the PEPs up with that).

  • Hunt down deprecated code and docs and remove it.
  • Take a module's documentation and make sure it still applies (not terribly sexy, but incredibly valuable).
  • Get rid of __mod__ and __divmod__ methods on float objects.

  • 2to3 fixers: new metaclass syntax (PEP 3115); change type(x) == int into isinstance(x, int).


/!\ Edit conflict - your version:



/!\ End of edit conflict


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

    22-24 halftime, 25 fulltime

    MTV

    Yes

    Brian Fitzpatrick

    22-25

    CHI

    Yes

    Skip Montanaro

    22-24

    CHI

    No

    Hasan Diwan

    all days (evenings only)

    MTV

    NO

    Brett Slatkin

    22-??

    MTV

    Yes

    Atul Varma

    23

    CHI

    No

    Anrew Wilson

    23

    CHI

    No

    Jono DiCarlo

    23

    CHI

    No

    Adrian Holovaty

    23

    CHI

    No

    Paul Smith

    23

    CHI

    No

    Cosmin Stejerean

    22-25

    CHI

    No

    Rob Kapteyn

    22-25

    CHI

    No

    Paul Lucas

    22-25

    MTV

    No

    Jason Prado

    22-23

    MTV

    No

    Anna Ravenscroft

    22-25PT

    MTV

    No

    Keith Dart

    22-25 PT

    MTV

    Yes

    Gregory P. Smith

    22,24 maybe 25

    MTV

    Yes

    Bill Janssen

    ?????

    MTV

    No

    Larry Hastings

    22-25

    MTV

    No

    Paul F. Dubois

    22-25

    MTV

    No

    Dobromir Montauk

    23PT

    MTV

    Yes

    Alex Booth

    23PT

    MTV

    Yes

    Molly Aplet

    23PT

    MTV

    Yes

    Mikeal Rogers

    22-??

    MTV

    No

    Daniel Corson

    22-25

    MTV

    No

    Arif B Abdullah

    24-25

    MTV

    No

    Yuri Ginsburg

    22-25 (afternoons)

    MTV

    No

    Ero Carrera

    22-25

    MTV

    No

    Benjamin Aranguren

    24-25

    MTV

    No

    Christopher Burns

    22-24, 25?

    MTV

    No

    Tom Waite

    22-24, 25?

    MTV

    No

    Thuon Chen

    22 (afternoon) 23-25

    MTV

    No

    John Reese

    22-?

    MTV

    Yes

    Jacques Frechet

    22

    MTV

    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.

More on Location

Mountain View

1600 Amphitheatre Parkway, CA 94043; University Theatre - 2nd Flr, Building 40

Directions: [WWW] http://www.google.com/corporate/address.html#directions Guests are welcome to arrive any time after 9:30 AM.

(Non-Googlers: please go to the Building 40 reception and let the receptionist know you are here for the Python Sprint and you will receive a badge.)

Chicago

Chicago Sales & Engineering Office, 20 West Kinzie St., Chicago, IL 60610

More info: http://www.google.com/corporate/address.html

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.

Various [http://freenode.net/ Freenode IRC] channels appear to be unused: #py3k, #pysprint, #sprynt, etc.. I could register one if there was interest, but it's not strictly required. --pfein on irc://irc.freenode.net

I suspect #python-dev would be sufficient. -- SkipMontanaro

GoogleSprint (last edited 2010-08-21 07:58:49 by 173-164-217-69-SFBA)

Unable to edit the page? See the FrontPage for instructions.