On 8/14/07, Christian Heimes <[EMAIL PROTECTED]> wrote: > Benji York wrote: > >> But wouldn't the only reason you want to step into, > >> e.g. pickle be if there were a bug in pickle itself? > > > > I believe he's talking about a situation where pickle calls back into > > Python. > > Yes, Benji is right. In the past I run into trouble with pickles two or > times. I was successfully able to debug and resolve my problem with the > pickle module and pdb. I like to keep the option in the Python 3.0 > series. In my opinion it is very useful to step through Python code to > see how the code is suppose to work. > > I'm trying to get involve in the Python core development process. It > seems that I'm not ready yet to contribute new ideas because I'm missing > the big picture.
Just stick around for a while and you will pick up on a general theme in how decisions are made. > On the other hand I don't know how I can contribute to > existing sub projects for Py3k. I find it difficult to get in. :/ Well, don't force it unless you like the subproject. If you are just looking for something to do there are always bugs to squash or patches to evaluate. Otherwise I would suggest just waiting until something comes along that grabs your attention and bugging anyone else who is working on it for any guidance you need. Yes, it can take a little while to get into the groove, but we are all nice guys and are happy to answer your questions. -Brett _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
