> Are proof-of-concept projects acceptable as GSoC projects? I'd say so. It's more rewarding (both for the student and the project) if the code has a chance to be integrated, at least in principle. However, doing a project and then finding out that the real solution should be similar but different is perfectly fine, IMO - it gives some motivation for the student to do the real thing afterwards.
> Experimenting with this idea became significantly more feasible since > Brett wrote importlib, but would still require a strong understanding > of Python's import system. I suspect even a proof of concept that was > tested against just filesystem imports and zipimport would prove quite > tricky. That, of course, makes it a difficult GSoC project. Ideally, the student should have a clear vision of what needs to be done. Failing that, the mentor should have a clear vision, and would then need frequent communication with the student. > Once the concept has been proven... I'm sure we could figure out > *something* useful to do with the idea. It would depend on the details > of what actually turns out to be feasible. It can't hurt to post that idea on the wiki page, with detail as to what might constitute success of the project. Students are expected to write proposals elaborating what it is that they want to do, and a decision on accepting projects is only taken after we have the proposals (and ideally after the potential mentor had communication with the student). 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
