Hi, Is there any news regarding this? I did GSoC last year and although I don't think I'm in a position to do it again this year, I still think that involvement in GSoC can be very beneficial to Pylons, especially that it is still young (relatively, comparing e.g. Pyramid 1.0 to Django) and there are many things that can be improved or built on top of Pyramid . If I get it correctly, the Sphinx/pocoo folks even got one 'core developer' as a result from last year's GSoC.
At the very least, just by applying, Pylons Project will get screened by prospective students that are looking for projects, which means free publicity. I myself found a number of interesting open source projects I've never heard of before when screening for potential projects last year. Just from the top of my head I can think of some ideas that are hopefully suitable for GSoC: - porting to Python 3 as mentioned before - creating or improving or help develop a higher-level framework a la turbogears, or cms a la drupal - create a portal for non-official Pyramid add-ons and similar stuff (with cool things like number of downloads, dependency graph, % completion-to-official-status, unit tests automation, code repository, compatibility data) -> refer to http://djangopackages.com/ or http://www.symfony-project.org/plugins/ or http://drupal.org/project/modules -------- Leontius Adhika Pradhana (Leon) http://leapon.net/ On Tue, Mar 8, 2011 at 3:25 AM, Chris McDonough <[email protected]> wrote: > On Mon, 2011-03-07 at 10:35 -0800, Mike Orr wrote: > > Which of Pyramid's dependencies have been ported to Python 3, or which > > have significant archaisms that would be hard to port? > > Already Py3 compat: > > - Chameleon (2.X) > - distribute (Chameleon 2 dependency) > - unittest2 (Chameleon 2 dependency) > - Mako > - zope.interface > > Not required under Py3: > > - ordereddict (Chameleon dependency under Python 2.6 and under) > - setuptools (distribute can fill in) > > Suggest replacement: > > - Paste > - PasteDeploy > - PasteScript > > We really don't use very much of Paste, and the parts we do make use of > we make use of very shallowly. I think it would be easier to recreate > (or "liberate") the parts we do use into a separate package than it > would be to port these three packages. > > Not yet ported: > > - pyramid > - repoze.lru > - translationstring > - venusian > - WebOb -- being worked on at PyCon > - zope.component > - zope.configuration > - zope.deprecation > - zope.event > - zope.i18nmessageid > - zope.schema > > I don't think we'd be able to get around porting any of these. Lennart > Regebro (he of "Porting to Python 3" book) has already started porting > some of the zope packages to Python 3, but I'm not sure where they're > all at at the moment. > > - C > > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/pylons-discuss?hl=en. > > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
