Re: [nycpython] Python bug week-end : 20-21 November

From: user 6.
Sent on: Friday, October 29, 2010 10:03 AM
On Thu, Oct 28, 2010 at 6:42 PM, Robert LaMarca
<[address removed]> wrote:
> I might be.. I might also be traveling then.. but might be interested.
> also.. might be fun to have a pre-meeting? ?Might help those of us new to the
> idea find our bearings.. we could help each other identify possible bugs to work
> on..
I'd like to attend a pre-meeting to brush on on the python source, and
the bug list.

I've poked around at the python C source, was looking for how passing
self to methods was implemented,
would like to investigate the structure further and work on bug fixes:

these are the parts that seamed like a good place to start:
wget http://www.python...­ && tar
-xzf Python*; cd Python*

./Objects/object.c
./Objects/typeobject­.c
./Objects/tupleobjec­t.c

+
| fire crow
| computer programmer
!___________________­__

? http://firecrow.c...­, [address removed],[masked], New York City, USA

>
>
>
>
>
> ----- Original Message ----
> From: Wes Chow <[address removed]>
> To: [address removed]
> Sent: Thu, October 28,[masked]:29:22 PM
> Subject: Re: [nycpython] Python bug week-end : 20-21 November
>
>
> Any interest in folk physically meeting somewhere that weekend?
>
> Wes
>
>
>
> On 10/28/[masked]:12 PM, David Christian wrote:
>> FYI...
>>
>> ---------- Forwarded message ----------
>> From: Antoine Pitrou<[address removed]>
>> Date: Mon, Oct 25, 2010 at 5:03 PM
>>
>> Hello,
>>
>> The development team of the Python interpreter (a.k.a python-dev) is
>> organizing a bug week-end on Saturday 20th and Sunday 21st of November.
>>
>> We would like to encourage anyone who feels interested in participating
>> to give it a try. Contributing to Python is much less intimidating than
>> it sounds. You don't need to have previous experience with modifying
>> the Python source; in fact bug days offer a good opportunity to learn
>> the basics by asking questions and working on relatively simple bugs
>> (see "how to get prepared" below). And most core developers are actual
>> human beings!
>>
>> How it happens
>> --------------
>>
>> The bug week-end will happen on the #python-dev IRC channel on the
>> Freenode network, where several core developers routinely hang out. No
>> physical meeting is scheduled as far as I know, but anyone is
>> encouraged to organize one and announce it on the official Python
>> channels such as this one.
>>
>> Participants (you!) join #python-dev and collaboratively go through the
>> Python issue tracker at http://bugs.pytho...­ . From there, you can
>> provide patches and/or review existing patches. Also, you can help us
>> assess issues on any specific topic you have expertise in (the range of
>> topics touched in the stdlib is quite broad and it is more than likely
>> that the core developers' expertise is lacking in some of them).
>>
>> Or, if you feel shy, you can simply watch other people work and
>> slowly get more confident about participating yourself.
>> Development is public and lurkers are welcome.
>>
>> What you can work on
>> --------------------­-
>>
>> Our expectation is that Python 3.2 beta 1 will have been released a
>> couple of days before the bug week-end and, therefore, one primary goal
>> is to polish the 3.2 branch for the following betas and the final
>> release. There are many issues to choose from on the bug tracker; any
>> bug fixes or documentation improvements will do. New features are
>> discouraged: they can't be checked in before the official 3.2 release.
>>
>> How to get prepared
>> -------------------
>>
>> If you are a beginner with the Python codebase, you may want to read the
>> development guide available here (courtesy of Brian Curtin):
>> http://docs.pytho...­
>>
>> There's a small practical guide to bug days/week-ends on the wiki:
>> http://wiki.pytho...­
>>
>> And the development FAQ holds answers to generic development questions:
>> http://www.python...­
>>
>> You can also do all of the above during the bug week-end, of course.
>> Please, don't hesitate to ask us questions on the #python-dev channel.
>>
>> Regards
>>
>> Antoine.
>>
>>
>
> --
> http://www.s7labs...­
>
>
>
> --
> Please Note: If you hit "REPLY", your message will be sent to everyone on this
> mailing list ([address removed])
> http://www.meetup...­
> This message was sent by Wes Chow ([address removed]) from The New York Python
> Meetup Group.
> To learn more about Wes Chow, visit his/her member profile:
> http://www.meetup...­
> To unsubscribe or to update your mailing list settings, click here:
> http://www.meetup...­
> Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]
>
>
>
> --
> Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
> http://www.meetup...­
> This message was sent by Robert LaMarca ([address removed]) from The New York Python Meetup Group.
> To learn more about Robert LaMarca, visit his/her member profile: http://www.meetup...­
> To unsubscribe or to update your mailing list settings, click here: http://www.meetup...­
> Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]
>
>



--

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy