[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Some searx requirements
From: |
ng0 |
Subject: |
Re: Some searx requirements |
Date: |
Sat, 4 Feb 2017 16:40:29 +0000 |
On 17-02-04 16:34:57, address@hidden wrote:
> 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,
Of course I meant to say: I'm trying to get searx to work. If we already
had it, that would be great ;)
>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.
>
>
--
ng0 -- https://www.inventati.org/patternsinthechaos/
- Re: [PATCH 7/9] gnu: python-pytest: Update to 3.0.5., (continued)
- [PATCH 3/9] gnu: Add python-httpbin., contact . ng0, 2017/02/04
- [PATCH 2/9] gnu: Add python-gunicorn., contact . ng0, 2017/02/04
- [PATCH 8/9] gnu: python-requests: Update to 2.12.4., contact . ng0, 2017/02/04
- [PATCH 6/9] gnu: Add python-pytest-httpbin-0.0.7., contact . ng0, 2017/02/04
- [PATCH 5/9] gnu: Add python-pysocks., contact . ng0, 2017/02/04
- Re: Some searx requirements,
ng0 <=