Re: [Python-Dev] GSoC Student Introduction

2008-04-23 Thread Martin v. Löwis
 See http://python.org/dev/bazaar/ for info. And if you have any other
 issues feel free to ask, Nick.

I certainly can't speak for the respective mentors, but I feel that
use bazaar really isn't the right answer to can I get commit access?

One motivation for GSoC is also community bonding, and having the
mentor (but not *only* the mentor) comment on the proposed changes,
and monitor the progress of the project. That the development branch
sits on the student's laptop doesn't really help in that process.

Instead, the student would have to push the branch somewhere to
a web-visible location. Now I question whether it's the student's
obligation to find a server himself, or whether the mentoring org
should provide the infrastructure (or, failing that, Google (*)).

So I think an answer to the question above involving bazaar might
be yes, but please don't commit to subversion, but only to the
bazaar repository.

Regards,
Martin

(*) FWIW, Google does provide the infrastructure; students are
encouraged (required?) to commit their work to code.google.com.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] BSDDB3

2008-04-23 Thread Martin v. Löwis
 I'm a bit nervous about syncing, because I have the feeling that
 python-dev is committing changes to python private branch of pybsddb. I
 would rather prefer patches send to me and integrate canonical pybsddb
 releases in Python frequently.

My understanding was that the pybsddb copy in Python *is* the official
code base. I think it's unfortunate that the pybsddb project was
revived, even though it was already dead.

Perhaps we should remove bsddb from Python again, and refer people to
pybsddb instead?

 Somebody suggested to post patches in the tracker, but I think this is
 not going to work. The diff from current python bsddb and the official
 version is so huge that nobody could follow it. A more sensible
 approach, I think, is to diff current python pybsddb against the
 version I used as my root (January?), integrate the changes in current
 canonical pybsddb and, then, drop the entire updated package into python.

-1. Who is going to do the 3k porting?

 I think this is the only way when integrating a project outside python
 SVN. Suggestions?.

The usual solution is to not integrate then, at all. Python doesn't
really ship with any libraries that also have an active life outside
of Python.

Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] PyArg_ParseTuple and Py_BuildValue question

2008-04-23 Thread Hrvoje Nikšić
On Thu, 2008-04-10 at 09:23 +0800, Alvin Delagon wrote:
 I'm currently writing a simple python SCTP module in C. So far it
 works sending and receiving strings from it.
[...]
 I'm going to construct an SS7 packet in python using struct.pack(). 
 Here's the question, how am I going to pass the packet I wrote in 
 python to my module and back? I already asked this question in 
 comp.lang.python but so far no responses yet.

Have you tried posting to the C API mailing list?

http://mail.python.org/mailman/listinfo/capi-sig


___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] GSoC Student Introduction

2008-04-23 Thread Paul Moore
On 23/04/2008, Martin v. Löwis [EMAIL PROTECTED] wrote:
  See http://python.org/dev/bazaar/ for info. And if you have any other
  issues feel free to ask, Nick.

 I certainly can't speak for the respective mentors, but I feel that
 use bazaar really isn't the right answer to can I get commit access?
[...]
 So I think an answer to the question above involving bazaar might
 be yes, but please don't commit to subversion, but only to the
 bazaar repository.

Agreed. Can I also point out that Bazaar isn't an official repository
for Python (yet). I don't want to open up the DVCS discussion again,
but I have recently finished looking at both Bazaar and Mercurial for
my personal use (including managing Python contributions) and decided
on Mercurial. A significant part of the decision was the fact that in
certain configurations, Bazaar is really, really slow.

It feels a little like Bazaar is becoming the de facto DVCS solution
for Python, and I'd like to avoid that happening until a proper
evaluation has been done.

Paul.

PS If the fact that Bazaar repos are set up is an important factor
here, I'd be willing to set up the equivalent Mercurial repos -
although I would need access to the relevant boxes and possibly some
admin assistance.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Encoding detection in the standard library?

2008-04-23 Thread M.-A. Lemburg

On 2008-04-23 07:26, Terry Reedy wrote:
Martin v. Löwis [EMAIL PROTECTED] wrote in message 
news:[EMAIL PROTECTED]

| I certainly agree that if the target set of documents is small enough it
|
| Ok. What advantage would you (or somebody working on a similar project)
| gain if chardet was part of the standard library? What if it was not
| chardet, but some other algorithm?

It seems to me that since there is not a 'correct' algorithm but only 
competing heuristics, encoding detection modules should be made available 
via PyPI and only be considered for stdlib after a best of breed emerges 
with community support. 


+1

Though in practice, determining the best of breed often becomes a
problem (see e.g. the JSON implementation discussion).

--
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Apr 23 2008)
 Python/Zope Consulting and Support ...http://www.egenix.com/
 mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
 mxODBC, mxDateTime, mxTextTools ...http://python.egenix.com/


 Try mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX for free ! 


   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
   Registered at Amtsgericht Duesseldorf: HRB 46611
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] GSoC Student Introduction

2008-04-23 Thread Guilherme Polo
2008/4/23, Martin v. Löwis [EMAIL PROTECTED]:
  See http://python.org/dev/bazaar/ for info. And if you have any other
   issues feel free to ask, Nick.


 I certainly can't speak for the respective mentors, but I feel that
  use bazaar really isn't the right answer to can I get commit access?

  One motivation for GSoC is also community bonding, and having the
  mentor (but not *only* the mentor) comment on the proposed changes,
  and monitor the progress of the project. That the development branch
  sits on the student's laptop doesn't really help in that process.

  Instead, the student would have to push the branch somewhere to
  a web-visible location. Now I question whether it's the student's
  obligation to find a server himself, or whether the mentoring org
  should provide the infrastructure (or, failing that, Google (*)).

  So I think an answer to the question above involving bazaar might
  be yes, but please don't commit to subversion, but only to the
  bazaar repository.

Hi Martin,

What is the point on having a branch in the svn repo if you won't be
able to commit ? Maybe I misunderstood what you said, so maybe could
you clarify that answer ?


  Regards,
  Martin

  (*) FWIW, Google does provide the infrastructure; students are
  encouraged (required?) to commit their work to code.google.com.

It is required to submit the final and complete work done during
GSoC to a project under code.google.com. That project will be
automatically created after gsoc ends. But yeh, we could create
another project there to use as a repo for the summer.

And thank you, James Tauber, effbot and everyone else that accepted me
as a student this year too. I guess I should create a new thread to
introduce myself and my project =)

Thanks,


 ___
  Python-Dev mailing list
  Python-Dev@python.org
  http://mail.python.org/mailman/listinfo/python-dev
  Unsubscribe: 
 http://mail.python.org/mailman/options/python-dev/ggpolo%40gmail.com



-- 
-- Guilherme H. Polo Goncalves
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] pydoc works with eggs? (python-2.5.1)

2008-04-23 Thread Neal Becker
Neal Becker wrote:

 pydoc blew up when I tried to view doc for pytools module, which is an
 egg:
 
 pydoc -p 8082
 pydoc server ready at http://localhost:8082/
 
 Exception happened during processing of request from ('127.0.0.1', 52915)
 Traceback (most recent call last):
   File /usr/lib64/python2.5/SocketServer.py, line 222, in handle_request
 self.process_request(request, client_address)
   File /usr/lib64/python2.5/SocketServer.py, line 241, in
   process_request
 self.finish_request(request, client_address)
   File /usr/lib64/python2.5/SocketServer.py, line 254, in finish_request
 self.RequestHandlerClass(request, client_address, self)
   File /usr/lib64/python2.5/SocketServer.py, line 522, in __init__
 self.handle()
   File /usr/lib64/python2.5/BaseHTTPServer.py, line 316, in handle
 self.handle_one_request()
   File /usr/lib64/python2.5/BaseHTTPServer.py, line 310, in
   handle_one_request
 method()
   File /usr/lib64/python2.5/pydoc.py, line 1924, in do_GET
 self.send_document(describe(obj), html.document(obj, path))
   File /usr/lib64/python2.5/pydoc.py, line 321, in document
 if inspect.ismodule(object): return self.docmodule(*args)
   File /usr/lib64/python2.5/pydoc.py, line 672, in docmodule
 contents.append(self.document(value, key, name, fdict, cdict))
   File /usr/lib64/python2.5/pydoc.py, line 322, in document
 if inspect.isclass(object): return self.docclass(*args)
   File /usr/lib64/python2.5/pydoc.py, line 807, in docclass
 lambda t: t[1] == 'method')
   File /usr/lib64/python2.5/pydoc.py, line 735, in spill
 funcs, classes, mdict, object))
   File /usr/lib64/python2.5/pydoc.py, line 323, in document
 if inspect.isroutine(object): return self.docroutine(*args)
   File /usr/lib64/python2.5/pydoc.py, line 891, in docroutine
 getdoc(object), self.preformat, funcs, classes, methods)
   File /usr/lib64/python2.5/pydoc.py, line 79, in getdoc
 result = inspect.getdoc(object) or inspect.getcomments(object)
   File /usr/lib64/python2.5/inspect.py, line 521, in getcomments
 lines, lnum = findsource(object)
   File /usr/lib64/python2.5/inspect.py, line 510, in findsource
 if pat.match(lines[lnum]): break
 IndexError: list index out of range
 
 
I see that installing the egg unzipped fixes this.  It looks to me that
pydoc doesn't work with zipped eggs.

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] GSoC Student Introduction

2008-04-23 Thread Christian Heimes
Martin v. Löwis schrieb:
 I certainly can't speak for the respective mentors, but I feel that
 use bazaar really isn't the right answer to can I get commit access?
 
 One motivation for GSoC is also community bonding, and having the
 mentor (but not *only* the mentor) comment on the proposed changes,
 and monitor the progress of the project. That the development branch
 sits on the student's laptop doesn't really help in that process.

Students have to sign the contributor agreement anyway or we can't use
their work. I don't see a problem with giving them svn commit privileges
as long as they restrict themselves to their sandbox.

 (*) FWIW, Google does provide the infrastructure; students are
 encouraged (required?) to commit their work to code.google.com.

People doesn't require the students to use their infrastructure. Google
just wants three evaluations from the mentors (after the community
bounding phase, mid term and at the end). Google also requires the
student to send in a tarball with their work - patches, docs, tests and
so on. The tarball is just required for legal reasons. Leslie once
explained it's a social and legal hack to make the contract work and the
lawyers happy.

Christian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] PyArg_ParseTuple and Py_BuildValue question

2008-04-23 Thread Benjamin Peterson
He emailed me back saying that he found the solution to his problem.

-- 
Cheers,
Benjamin Peterson
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


[Python-Dev] Externally developed modules (was Re: BSDDB3)

2008-04-23 Thread Nick Coghlan

Martin v. Löwis wrote:

I think this is the only way when integrating a project outside python
SVN. Suggestions?.


The usual solution is to not integrate then, at all. Python doesn't
really ship with any libraries that also have an active life outside
of Python.


Not entirely true - we have the ones listed in PEP 360. However, I think 
of those only Optik (aka optparse) is currently seeing active external 
updates.


Of course, we also have a big warning at the top of the PEP saying 
*Never Ever Do This Again*.


Cheers,
Nick.

--
Nick Coghlan   |   [EMAIL PROTECTED]   |   Brisbane, Australia
---
http://www.boredomandlaziness.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] pydoc works with eggs? (python-2.5.1)

2008-04-23 Thread Phillip J. Eby

At 06:48 AM 4/23/2008 -0400, Neal Becker wrote:

Neal Becker wrote:

 pydoc blew up when I tried to view doc for pytools module, which is an
 egg:

 pydoc -p 8082
 pydoc server ready at http://localhost:8082/
 
...

I see that installing the egg unzipped fixes this.  It looks to me that
pydoc doesn't work with zipped eggs.


What's odd about this is that it *did* at one time.  Or at least 
help() did.  The changes I made in 2.5 were mainly so that 
help(package) would work on zipped eggs.


From the traceback, it looks like the issue is that it's trying to 
parse comments out of the source for an object with no docstring.  I 
didn't know it could do that, so I never tried testing it.


___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Encoding detection in the standard library?

2008-04-23 Thread Bill Janssen
[EMAIL PROTECTED] writes:
  When a web browser POSTs data, there is no standard way of communicating
  which encoding it's using.
 
 That's just not true. Web browser should and do use the encoding of the
 web page that originally contained the form.

I wonder if the discussion is confusing two different things.  Take a
look at
http://www.w3.org/TR/REC-html40/interact/forms.html#h-17.13.4.

There are two prescribed ways of sending form data:
application/x-www-form-urlencoded, which can only be used with ASCII
data, and multipart/form-data.  ``The content type
multipart/form-data should be used for submitting forms that contain
files, non-ASCII data, and binary data.''

It's true that the page containing the form may specify which of these
two forms to use, but the character encodings are determined by the
choice.

 For web forms, I always encode the pages in UTF-8, and that always
 works.

Should work, if you use the multipart/form-data format.

Bill

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] BSDDB3

2008-04-23 Thread Brett Cannon
On Tue, Apr 22, 2008 at 11:12 PM, Martin v. Löwis [EMAIL PROTECTED] wrote:
  I'm a bit nervous about syncing, because I have the feeling that
   python-dev is committing changes to python private branch of pybsddb. I
   would rather prefer patches send to me and integrate canonical pybsddb
   releases in Python frequently.

  My understanding was that the pybsddb copy in Python *is* the official
  code base. I think it's unfortunate that the pybsddb project was
  revived, even though it was already dead.

  Perhaps we should remove bsddb from Python again, and refer people to
  pybsddb instead?


+1 from me! The amount of issues the bsddb module has caused over the
years suggests to me it would do better as an external project again.

-Brett
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] GSoC Student Introduction

2008-04-23 Thread Rodrigo Bernardo Pimentel
On Wed, Apr 23 2008 at 07:56:44AM BRT, Christian Heimes [EMAIL PROTECTED] 
wrote:
 Martin v. Löwis schrieb:
  I certainly can't speak for the respective mentors, but I feel that
  use bazaar really isn't the right answer to can I get commit access?
  
  One motivation for GSoC is also community bonding, and having the
  mentor (but not *only* the mentor) comment on the proposed changes,
  and monitor the progress of the project. That the development branch
  sits on the student's laptop doesn't really help in that process.

Agreed. Using bazaar, at least in this context, involves pushing changes
regularly to someplace visible, where the mentor and other developers may
see and comment.

 Students have to sign the contributor agreement anyway or we can't use
 their work. I don't see a problem with giving them svn commit privileges
 as long as they restrict themselves to their sandbox.

With that, http://python.org/dev/bazaar/ says anybody with write access to
the Subversion repository can push their own branches to python.org, so
GSoC students could use bzr and push their changes to python.org regularly,
for mentor (and, more generally, core developers) comments.

Cheers,


rbp
-- 
Rodrigo Bernardo Pimentel [EMAIL PROTECTED] | GPG: 0x0DB14978
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] BSDDB3

2008-04-23 Thread Gregory P. Smith
On Tue, Apr 22, 2008 at 8:09 PM, Jesus Cea [EMAIL PROTECTED] wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Trent Nelson wrote:
 | I remember those rampant BSDDB crashes on Windows well.
 [...]
 | basically, the tests weren't cleaning up their environment in
 | the right order, so BSDDB was getting passed completely and
 | utterly bogus values.

 Next week I will (if nothing goes wrong) publish pybsddb 4.6.4. This
 release supports distributed transactions and replication, testsuite is
 way faster, and rewritten to be able to launch tests from multiple
 threads/processes if you wish, setuptools/pypi support, etc.

 I think this release would be appropiate to integrate in Python. I think
 most demands are solved and new features are interesting (replication,
 distributed transactions, do not crash when closing objects in the wrong
 order...). Also, I completed the documentation, with the full supported
 API, and ported it to Python 2.6 documentation system. The result:

 http://www.jcea.es/programacion/pybsddb.htm#bsddb3-4.6.4
 http://www.jcea.es/programacion/pybsddb_doc/preview/

 I'm very interested in integrating this release in Python 2.6 for the
 new features, the full documentation, and to get feedback from Buildbot
 and python-dev community. Also, I would like to avoid to integrate
 pybsddb late in the python 2.6 release cycle; I hope to be away of my
 computer in August! :).

 I'm a bit nervous about syncing, because I have the feeling that
 python-dev is committing changes to python private branch of pybsddb. I
 would rather prefer patches send to me and integrate canonical pybsddb
 releases in Python frequently.

 Somebody suggested to post patches in the tracker, but I think this is
 not going to work. The diff from current python bsddb and the official
 version is so huge that nobody could follow it. A more sensible
 approach, I think, is to diff current python pybsddb against the
 version I used as my root (January?), integrate the changes in current
 canonical pybsddb and, then, drop the entire updated package into
 python.


Agreed.  I forked jcea's version found in his svn repository from python
trunk at r60209.

The only change to any Modules/*bsddb*  files made to python trunk since
then was me manually applying one bugfix that jcea had made in his
repository.  My goal all along had been to merge his changes back into
python trunk until he had commit access.  Obviously I haven't had time to do
that.

The changes to Lib/bsddb/* since then have been test suite updates which I
think jcea should go through and selectively merge as appropriate into his
repository (he has done a lot of test suite cleanup). ( svn://
svn.argo.es/jcea/pybsddb/trunk )

After that, merging his changes into trunk will be relatively easy and I
think we should give jcea commit access and let him do it and henceforth use
python svn as the official repository for the pybsddb code and
documentation.

I do not see this as a daunting task assuming jcea is willing to be
volunteered to do the merge and to handle any py3k merge issues that come
up.


Alternatively: (removal of bsddb from the standard library)

If people want to go the other route a remove bsddb from Python all together
letting it thrive as a standalone addon module, what will this mean to the
old shelve and dbhash standard library that use bsddb?  Someone should write
a sqlite backend for shelve.  Either way it should not be removed from 2.6
as it needs to be marked at deprecated for one release round only to be
taken out in 2.7 and that does leave open the question of should it exist in
3.0 at all or just start out deprecated there?


-gps
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] GSoC Student Introduction

2008-04-23 Thread Martin v. Löwis
 What is the point on having a branch in the svn repo if you won't be
 able to commit ? Maybe I misunderstood what you said, so maybe could
 you clarify that answer ?

What I meant is this: you need commit privileges regardless of whether
you are going to use bazaar or subversion (i.e. even for bazaar, you
still need commit privileges). So if mentors favor usage of bazaar
over subversion, they still need to arrange their students to get
commit privileges, and then ask them not to use these privileges for
subversion, but only for bazaar (because we only have a single set
of credentials that we manage).

HTH,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Externally developed modules (was Re: BSDDB3)

2008-04-23 Thread Martin v. Löwis
 The usual solution is to not integrate then, at all. Python doesn't
  really ship with any libraries that also have an active life
 outside of Python.
 
 Not entirely true - we have the ones listed in PEP 360. However, I
 think of those only Optik (aka optparse) is currently seeing active
 external updates.

Hence my classification doesn't really, which I meant to be vague.

 Of course, we also have a big warning at the top of the PEP saying 
 *Never Ever Do This Again*.

I think that's what Guido once said.

Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Encoding detection in the standard library?

2008-04-23 Thread Martin v. Löwis
 For web forms, I always encode the pages in UTF-8, and that always
 works.
 
 Should work, if you use the multipart/form-data format.

Right - I was implicitly assuming that.

Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] GSoC Student Introduction

2008-04-23 Thread Guilherme Polo
2008/4/23 Martin v. Löwis [EMAIL PROTECTED]:
  What is the point on having a branch in the svn repo if you won't be
   able to commit ? Maybe I misunderstood what you said, so maybe could
   you clarify that answer ?

  What I meant is this: you need commit privileges regardless of whether
  you are going to use bazaar or subversion (i.e. even for bazaar, you
  still need commit privileges). So if mentors favor usage of bazaar
  over subversion, they still need to arrange their students to get
  commit privileges, and then ask them not to use these privileges for
  subversion, but only for bazaar (because we only have a single set
  of credentials that we manage).

I see, thanks for clearing it up.

But, what about giving students a branch in the svn and instructing
them to commit only there ? (Chris mentioned this two emails ago). If
for some reason svn is not the way to go, then I'm happy in using
bazaar for commits anyway.
Also, are you (PSF) planning to do this now or just at the official
gsoc start ? And, is there some internal discussion going on to decide
if students are going to get a branch or something at python
repositories ?


  HTH,
  Martin




-- 
-- Guilherme H. Polo Goncalves
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] GSoC Student Introduction

2008-04-23 Thread Martin v. Löwis
 But, what about giving students a branch in the svn and instructing
 them to commit only there ? (Chris mentioned this two emails ago). If
 for some reason svn is not the way to go, then I'm happy in using
 bazaar for commits anyway.

I think it's for the mentor to decide. I see no problems with svn -
it's just that Brett suggested to use bazaar.

 Also, are you (PSF) planning to do this now or just at the official
 gsoc start ? And, is there some internal discussion going on to decide
 if students are going to get a branch or something at python
 repositories ?

No, no discussion needed. The students should just send me their SSH
keys, and their preferred form of firstname.lastname (some people
may have names more complex than that), and I'll add them.

Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] GSoC Student Introduction

2008-04-23 Thread Christian Heimes
Guilherme Polo schrieb:
 Also, are you (PSF) planning to do this now or just at the official
 gsoc start ? And, is there some internal discussion going on to decide
 if students are going to get a branch or something at python
 repositories ?

I suggest we use the bounding period to set up the infrastructure for
the students. I've already written a private mail to my student with
several small tasks like subscribing to mailing lists, creating accounts
at bugs.python.org + wiki.python.org, mailing the contribution agreement
etc.

By the end of the bounding period everything should be in place -
including the working environment on the students' computers.

Christian

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com