Status of the python-dev task
Hi, According to Joey Hess, it seems that the python-dev needs someone to maintain it. At the moment, the python-dev does look like : Task: python-dev Section: devel Description: Python Almost all of the Debian-packaged Python tools and extensions, for developing scripts and simple or complex applications in Python. Packages: python-base python-doc ddd dpkg-python gadfly gimp-python htmlgen idle pydb # pyrite python-bobo python-bobopos python-dev python-examples python-extclass python-gdbm python-gdk-imlib python-gendoc python-glade python-gnome python-gtk # python-history python-imaging-sane python-imaging-tk python-kjbuckets python-ldap python-mpz python-mxdatetime python-mxstack python-mxtexttools python-mxtools python-netcdf python-newt python-numeric python-numeric-tutorial python-pam # python-pdb python-pmw python-pygresql # python-rng python-tk # python-wpy python-xml # python-zlib pythondoc saml sulfur swig Those commented packages seems not to be in woody or no longer exist. Maintainers, if your python packages did not enter testing, you should have a look to the testing pages in order to figure out what happened and to resolve the problems ASAP. Thanks to apt-cache, I listed the following packages that could be considered as part of python-dev: -=-=-=-=-=-=- WOODY: dcoppython - Python bindings for DCOP dpkg-python - Python interface modules for dpkg gadfly - SQL database and parser generator in Python gimp-python - Write plugins for Gimp in Python htmlgen - Generation of HTML documents with Python scripts. idle - An IDE for Python using Tkinter idle-python2 - An IDE for Python2 using Tkinter jaxml - Python module for generating XML documents libkdexparts-dev - Python bindings for DCOP libkdexparts1 - Python bindings for DCOP libwxgtk2.2-python - wxWindows Cross-platform C++ GUI toolkit (Python binding) pms - An MUA framework in Python pyao - A Python interface to the Audio Output library pychecker - Finds common bugs in python source code pydb - An enhanced Python command-line debugger pydict - an English/Chinese Dictionary written with python/gtk pyogg - A Python interface to the Ogg library python-4suite - FourThought XML Processing Tools for Python (1.5.x) python-base - An interactive object-oriented scripting language. python-bobo - Python Object Publisher python-bobodtml - Document templates with fill-in fields. python-bobopos - The Bobo Persistent Object System. python-dev - Header files and a static library for Python. python-distutils - A standard suite of Module Distribution Utilities for Python python-doc - Documentation for the scripting language Python (info+html). python-ecasound - python binding files for ecasound python-elisp - Emacs-lisp python-mode for the scripting language Python. python-examples - Examples for the scripting language Python. python-extclass - Improves integration between Python and C++ classes python-gdbm - GNU dbm database support for Python. python-gdk-imlib - GTK gdk_imlib support module for Python. python-gendoc - Documentation generation from Python source files. python-glade - Put a bit of python code behind interfaces built with GLADE. python-gnome - PyGNOME -- Python bindings for GNOME. python-gnuplot - A pipe-based interface to the gnuplot plotting program python-gtk - GTK support module for Python. python-happydoc - Python Documentation Extraction Tool python-happydoc-doc - Python Documentation Extraction Tool Documentation python-imaging - The Python Imaging Library. python-imaging-doc - Documentation and examples for the Python Imaging Library. python-imaging-sane - The Python Imaging Library SANE interface. python-imaging-tk - The Python Imaging Library (Module with Tk support). python-kjbuckets - Set and graph data types for Python python-ldap - An LDAP module for Python. python-mpz - Multiple-precision arithmetic support for Python. python-mxdatetime - Date and time handling routines and types for Python python-mxstack - A fast stack implementation for Python. python-mxtexttools - Fast text manipulation tools for Python python-mxtools - A collection of new builtins for Python python-mysqldb - A Python interface for MySQL python-netcdf - A netCDF interface for Python python-newt - A newt module for Python. python-numeric - Numerical (matrix-oriented) Mathematics for Python python-numeric-tutorial - Tutorial for the Numerical Python Library python-orbit - Python bindings for ORBit python-pam - A Python interface to the PAM library. python-pcgi - Persistent CGI for Python python-pmw - Pmw -- Python MegaWidgets python-pmw-doc - Pmw -- Python MegaWidgets python-pqueue - priority queue extension for Python 1.5.2 python-regrtest - Regression test for the Python distribution. python-reportlab - ReportLab library to create PDF documents using Python python-scientific - Python modules useful for scientific computing python-scientific-doc - Python modules useful for scientific computing
Re: Status of the python-dev task
Jérôme Marant wrote: > According to Joey Hess, it seems that the python-dev needs > someone to maintain it. Well, the best maintainer would probably (presumably) be the maintainer[1] of task-pthon-dev. I'm going to go through and contact the maintainers of the task packages indiviually and work this stuff out. > This is a very long list and I'm not sure all of them should > be put in a single task, for few reasons: > > - there are both python and python2 package. > - some of them are not used a lot. I seriously doubt that they all belong in any task. If we had a perl task, it would be *insane* to make it include lib*-perl. Knowing little of python, I can only draw an analogy. Our guidelines include the following: Care should be taken when adding new tasks to ensure that the new task is suitably generic -- it should be something of value to a large number (at least 10%) of our users. It must not perform the same general purpose as some other existing task. It must contain packages that are the ones in most common use, and software that is of the best perceived quality. > As long as there is a speration between python and python2, > I would propose to create a second task called python2-dev > that would contain all python2 specific packages. > (I still don't know what was stated about the separation, so > does my proposal make sense?) > > Now, some questions: > - what packages are not worth having? > - should we split the task in smaller ones? You have to run new tasks by myself, Anthony Towns and Randolph Chung right now. The guidelines and working consensus we have is emphatically against splitting up tasks (see above), and the set of tasks we've settled on was chosen after a lot of consideration to be at the right level of granularity (though we're certianly open to interesting new tasks if they meet the guildlines). If the python/python2 split is a problem, the maintainer of this task basically has to decide if it will offer python, python2, or both. Another thing to bear in mind is that the new system makes it reasonably easy to select a task thus selecting all the packages in it, and then drop down to per-package selection and remove or change some of the selections, before anything is installed. -- ±see shy jo [1] Hi David. The only task-pthon package I can find is in potato.
