RFS: pickleshare -- File system based database that uses Python pickles
Hi, I'm looking for a sponsor for my package: * Package name:pickleshare Version: 0.5 Upstream author: Ville Vainio * URL: https://github.com/pickleshare/pickleshare * License: Expat Progr. lang.:Python Description: File system based database that uses Python pickles Like shelve, a PickleShareDB object acts like a normal dictionary. Unlike shelve, many processes can access the database simultaneously. Changing a value in database is immediately visible to other processes accessing the same database. . Concurrency is possible because the values are stored in separate files. Hence the "database" is a directory where all files are governed by PickleShare. This is a dependance of IPython/Jupyter ; it is available on mentors.debian.net : http://mentors.debian.net/package/pickleshare dget -x http://mentors.debian.net/debian/pool/main/p/pickleshare/pickleshare_0.5-1.dsc or in git: Vcs-Git: git://anonscm.debian.org/python-modules/packages/pickleshare.git Vcs-Browser: https://anonscm.debian.org/cgit/python-modules/packages/pickleshare.git Thanks, Snark on #debian-python
Re: team vs individual as maintainer
[Piotr Ożarowski, 2015-10-07] > [Barry Warsaw, 2015-10-07] > > * Team in Maintainers is a strong statement that fully collaborative > > maintenance is preferred. Anyone can commit to the vcs and upload as > > needed. A courtesy email to Uploaders can be nice but not required. > > > > * Team in Uploaders is a weak statement of collaboration. Help in > > maintaining > > the package is appreciated, commits to vcs are freely welcomed, but before > > uploading, please contact the Maintainer for the green light. > > how about making it official and adding it to the policy? done. I also added policy.rst file to python-modules.git repo (it still clearly states we use SVN only, though!) -- evil general Piotr signature.asc Description: PGP signature
Django 1.8 in unstable in early November
Hello, I just filed 20 bugs on packages that FTBFS with Django 1.8. They have two weeks to be fixed before we upload Django 1.8 to unstable. https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=python-dja...@packages.debian.org;tag=django18 If you maintain a package in the Django ecosystem, please double check that it's ready for Django 1.8. The fact that it doesn't fail to build does not mean that it will necessarily work if you don't have any tests or if you don't run them. If you file more bugs related to Django 1.8, don't hesitate to add the "django18" usertag associated to the "python-dja...@packages.debian.org" user. (I wish we could easily rerun the DEP-8 functional tests with a new version of the package) Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
