On 15 April 2015 at 05:07, Glyph wrote:
> Is there a way to answer this question as a query against PyPI metadata? It
> seems like the information ought to be there, in some form...
>
> -g
IME a lot of projects don't keep their PyPI metadata up-to-date.
I already responded to Paul on Twitter, b
> On Apr 15, 2015, at 3:37 AM, Cory Benfield wrote:
>
> On 15 April 2015 at 05:07, Glyph wrote:
>> Is there a way to answer this question as a query against PyPI metadata? It
>> seems like the information ought to be there, in some form...
>>
>> -g
>
> IME a lot of projects don't keep their
On 15 April 2015 at 09:06, Donald Stufft wrote:
> lol whoops, pip supports 3.2, requests still works on 3.2 though!
Heh, yeah: we don't support 3.2 but we do support pip, so as long as
it works well enough for you then that's fine by me.
That said, 3.2 is bad and people using it should feel bad.
On Tue, Apr 14, 2015 at 12:54 PM, Hynek Schlawack wrote:
> Greetings fellow Pythoneers,
>
> I'm happy to announce that pyOpenSSL 0.15 is now available.
>
>
Congrats on getting the release out, Hynek. Thanks once again for stepping
in to take over the lead role on the pyOpenSSL project. Thanks a
Thank you for your years of maintenance of pyOpenSSL!
Alex
On Wed, Apr 15, 2015 at 2:02 PM, Jean-Paul Calderone <
[email protected]> wrote:
> On Tue, Apr 14, 2015 at 12:54 PM, Hynek Schlawack wrote:
>
>> Greetings fellow Pythoneers,
>>
>> I'm happy to announce that pyOpenSSL 0.15 is now a
Thank you very much to Jean-Paul and Hynek for getting out this most recent
release! (And thanks to Hynek for my opportunity to contribute my first patch
to pyOpenSSL ;-)).
-glyph
> On Apr 15, 2015, at 14:10, Alex Gaynor wrote:
>
> Thank you for your years of maintenance of pyOpenSSL!
>
> Al
