When I started this seemed like an easy way to share files. I'm not entirely happy with the number of packages that I ended up putting in python.scm, grapql-* seems like it could be broken off, django ones could go in Hartmut's django.scm. Python-nautilus doesn't seem to belong anywhere. I'd like to move all the sqlalchemy packages to databases.scm, but I don't think there's anything we can do about python.scm hitting 10k+ lines.
python-nautilus can be upgraded to 0.5.x, but it involves packaging more python packages, so I figured that could wait until later. I've also included my "master file" that I pulled the patches from, it makes building all the patches a bit easier to only have to drop in one file than to apply 16 patches. Efraim Flashner (16): gnu: Add python-pika. gnu: Add python-peewee. gnu: Add python-promise. gnu: Add python-pytest-mock. gnu: Add python-graphql-core. gnu: Add python-graphql-relay. gnu: Add python-sqlalchemy-utils. gnu: Add python-pytest-django. gnu: Add python-django-filter. gnu: Add python-graphene. gnu: Add python-consul. gnu: Add python-cov-core. gnu: Add python-nose2. gnu: Add python-bcrypt. gnu: Add python-nautilus. gnu: Add onionshare. gnu/local.mk | 1 + gnu/packages/databases.scm | 30 ++ gnu/packages/password-utils.scm | 35 ++ .../patches/onionshare-fix-install-paths.patch | 39 ++ gnu/packages/python.scm | 452 ++++++++++++++++++++- gnu/packages/tor.scm | 100 +++++ 6 files changed, 656 insertions(+), 1 deletion(-) create mode 100644 gnu/packages/patches/onionshare-fix-install-paths.patch -- 2.10.0