How Python is Developed

Slide 1

Slide 1 text

How Python is Developed Brett Cannon [email protected] PyCon 2009

Slide 2

Slide 2 text

OMG! A bug!

Slide 3

Slide 3 text

“Who can I talk with to make sure it’s a bug?” comp.lang.python python-dev

Slide 4

Slide 4 text

“I should tell somebody about this.” http://bugs.python.org/

Slide 5

Slide 5 text

“Oh look, a bug.” new-bugs-announce python-bugs-list

Slide 6

Slide 6 text

“Look at what triggers the bug!”

Slide 7

Slide 7 text

“This should be ﬁxed.”

Slide 8

Slide 8 text

“Here’s a patch to ﬁx it!”

Slide 9

Slide 9 text

What a patch needs • PEP 7/8 conformance • Unit tests • Doc changes • Misc/NEWS • Misc/ACKS

Slide 10

Slide 10 text

“LGTM.”

Slide 11

Slide 11 text

Please be patient when waiting for a review! Only 26 developers from December 1 to March 12 changed more than 100 lines of code; 39 changed any code.

Slide 12

Slide 12 text

“Committed.”

Slide 13

Slide 13 text

“I have an idea!”

Slide 14

Slide 14 text

“I should bounce this idea off some people.” python-ideas comp.lang.python

Slide 15

Slide 15 text

“Look at what I made Python do!”

Slide 16

Slide 16 text

“PEP time!” http://www.python.org/dev/peps/

Slide 17

Slide 17 text

“Does that shed come in puce?” python-dev

Slide 18

Slide 18 text

“Make the shed spam-colored and we will include it.”

Slide 19

Slide 19 text

“I made Python better!”

Slide 20

Slide 20 text

“How can I join the cool crowd?”

Slide 21

Slide 21 text

Contribute on bugs.python.org .

Slide 22

Slide 22 text

Request developer privileges on the issue tracker.

Slide 23

Slide 23 text

Ask for commit privileges.

Slide 24

Slide 24 text

• http://www.python.org/dev/setup/ • http://www.python.org/dev/workﬂow/