Re: Python and Debian infrastructure

2015-04-16 Thread Paul Wise
On Thu, Apr 16, 2015 at 10:48 PM, Jan Dittberner wrote: > Pyramid is a bit more lightweight Flask might be another option for lightweight framework needs. > Paul already suggested to merge debianmemberportfolio with db.debian.org but > I did not have time to evaluate that option yet. That is an

Re: Python and Debian infrastructure

2015-04-16 Thread Jan Dittberner
On Thu, Apr 16, 2015 at 02:30:16PM +0200, Nicolas Chauvat wrote: > On Thu, Apr 16, 2015 at 02:58:53PM +0800, Paul Wise wrote: > > Port services based on Pylons (deprecated) to something else like Django: > > Pylons is deprecated in favor of Pyramid. It could be that porting > these services to Pyr

Re: Python and Debian infrastructure

2015-04-16 Thread Nicolas Chauvat
On Thu, Apr 16, 2015 at 02:58:53PM +0800, Paul Wise wrote: > Port services based on Pylons (deprecated) to something else like Django: Pylons is deprecated in favor of Pyramid. It could be that porting these services to Pyramid will be easier than rewriting on top of Django. -- Nicolas Chauvat

Re: Python and Debian infrastructure

2015-04-16 Thread Barry Warsaw
On Apr 16, 2015, at 02:58 PM, Paul Wise wrote: >Does anyone know of any other deprecated Python stuff that we should >move away from? One of the things I'd like to see happen, probably from the PyPA (Python Packaging Authority), is some help for determining this via PyPI. For example, if you sea

Python and Debian infrastructure

2015-04-15 Thread Paul Wise
In addition to the Python 3 related work: Port service dependencies to Python 3. Port service code-bases to Python 3. We also need to: Port Django based services to Django 1.7 Port services based on Pylons (deprecated) to something else like Django: snapshot.debian.org debexpo (mentors.debian.