On Wed, Aug 22, 2007 at 08:49:12PM +0200, Maciej Fijalkowski wrote:

Hello,

This is the list of possibly orphaned parts of pypy. We should consider each item here and think in detail what to do with them. They're mostly broken or not actively maintained. If nobody shows an interest to maintain them, deleting would be the best solution to avoid clutter. Also they pose a maintenance burden when we proceed with the needed large refactorings. Maybe it is also a solution to lazily delete them as they are broken by refactoring if nobody steps up.

Of course deleted things can easily be brought back from svn history, if there is renewed interest. So the above may sound scarier than it is.

* llvm backend - we need a maintainer for that * pyrex backend (llvm depends on it tough) * js interpreter - needs a lot of work, before we might have usecases for that. * common lisp backend * squeak backend * ext compiler - would need a large rewrite from rctypes to rffi * rctypes (both) - delete as soon as they would not be needed * logic objspace, including constraint libraries

Please add aop.py and dbc.py (from pypy/lib) to that list. -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science Reprise et maintenance de sites CPS: http://www.migration-cms.com/

On Wed, Aug 22, 2007 at 08:49:12PM +0200, Maciej Fijalkowski wrote:

Hello,

This is the list of possibly orphaned parts of pypy. We should consider each item here and think in detail what to do with them. They're mostly broken or not actively maintained. If nobody shows an interest to maintain them, deleting would be the best solution to avoid clutter. Also they pose a maintenance burden when we proceed with the needed large refactorings. Maybe it is also a solution to lazily delete them as they are broken by refactoring if nobody steps up.

Of course deleted things can easily be brought back from svn history, if there is renewed interest. So the above may sound scarier than it is.

* llvm backend - we need a maintainer for that * pyrex backend (llvm depends on it tough) * js interpreter - needs a lot of work, before we might have usecases for that. * common lisp backend * squeak backend * ext compiler - would need a large rewrite from rctypes to rffi * rctypes (both) - delete as soon as they would not be needed * logic objspace, including constraint libraries

Please add aop.py and dbc.py (from pypy/lib) to that list. -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science Reprise et maintenance de sites CPS: http://www.migration-cms.com/