[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Some searx requirements
From: |
contact . ng0 |
Subject: |
Some searx requirements |
Date: |
Sat, 4 Feb 2017 16:34:57 +0000 |
These come from a branch so old I just had to start from from scratch again.
While I was at it, I saw some of them were being added to a new python branch,
but I can't filter that out and rebase against a moving-target branch.
I'm trying to get searx to work again, patches should work on their own, though
I need a comment on gunicorn and the one which adds pysocks as an input to some
package. I never packaged a python based server (? gunicorn is a server right?)
and lately I haven't been messing around with this branch so I don't know about
the pysocks thing, except that searx needs this for the tor capability.
- Some searx requirements,
contact . ng0 <=
- [PATCH 1/9] gnu: python-dateutils-2: Update to 2.5.3., contact . ng0, 2017/02/04
- [PATCH 9/9] gnu: python-requests: Add python-pysocks to propagated-inputs., contact . ng0, 2017/02/04
- [PATCH 4/9] gnu: Add python-pytest-httpbin., contact . ng0, 2017/02/04
- [PATCH 7/9] gnu: python-pytest: Update to 3.0.5., contact . ng0, 2017/02/04
- [PATCH 3/9] gnu: Add python-httpbin., contact . ng0, 2017/02/04
- [PATCH 2/9] gnu: Add python-gunicorn., contact . ng0, 2017/02/04