On Mar 7, 2014, at 7:45 AM, Marius Gedminas wrote:
> On Fri, Mar 07, 2014 at 01:03:23AM -0500, Donald Stufft wrote:
>> The JSON API is functional again and is available for testing!
>
> Excellent!
>
> I can observe two differences with the current PyPI code:
>
> First, the Content-Type of the
On Fri, Mar 07, 2014 at 01:03:23AM -0500, Donald Stufft wrote:
> The JSON API is functional again and is available for testing!
Excellent!
I can observe two differences with the current PyPI code:
First, the Content-Type of the response differs:
$ curl -sI https://pypi.python.org/pypi/setupto
On Mar 6, 2014, at 7:28 AM, Donald Stufft wrote:
>>
>>
>> But the old PyPI codebase already had a JSON API[1]. I'm using it to keep
>> track of Python 3 support status of about 800 packages maintained by the
>> Zope Foundation: http://zope3.pov.lt/py3/
>>
>> [1] https://wiki.python.org/moin/
On Thu, Mar 6, 2014 at 3:28 PM, Donald Stufft wrote:
> On Mar 6, 2014, at 4:10 AM, Marius Gedminas wrote:
>> On Wed, Mar 05, 2014 at 07:01:49AM -0500, Donald Stufft wrote:
>>> On Mar 5, 2014, at 5:48 AM, anatoly techtonik wrote:
JSON-RPC is a better choice for recommended external API,
On Mar 6, 2014, at 4:10 AM, Marius Gedminas wrote:
> On Wed, Mar 05, 2014 at 07:01:49AM -0500, Donald Stufft wrote:
>> On Mar 5, 2014, at 5:48 AM, anatoly techtonik wrote:
>>> JSON-RPC is a better choice for recommended external API,
>>> because it doesn't rely on memory hungry and potentially
On 06/03/14 20:10, Marius Gedminas wrote:
> On Wed, Mar 05, 2014 at 07:01:49AM -0500, Donald Stufft wrote:
>> On Mar 5, 2014, at 5:48 AM, anatoly techtonik wrote:
>>> JSON-RPC is a better choice for recommended external API,
>>> because it doesn't rely on memory hungry and potentially unsafe
>>> X
On Wed, Mar 5, 2014 at 3:01 PM, Donald Stufft wrote:
>
> XMLRPC is used in order to maintain compatibility with what is already there.
> Something
> better will replace it eventually and XMLRPC will be deprecated.
Good to know that. Testing XMLRPC is a chance to port handlers to a better API,
so
On Wed, Mar 05, 2014 at 07:01:49AM -0500, Donald Stufft wrote:
> On Mar 5, 2014, at 5:48 AM, anatoly techtonik wrote:
> > JSON-RPC is a better choice for recommended external API,
> > because it doesn't rely on memory hungry and potentially unsafe
> > XML libraries.
> >
> > On Wed, Mar 5, 2014 at
JSON-RPC is a better choice for recommended external API,
because it doesn't rely on memory hungry and potentially unsafe
XML libraries.
On Wed, Mar 5, 2014 at 3:41 AM, Donald Stufft wrote:
> Just a quick FYI that the last missing piece (search) for XMLRPC was merged in
> Warehouse today. If you
On Mar 5, 2014, at 5:48 AM, anatoly techtonik wrote:
> JSON-RPC is a better choice for recommended external API,
> because it doesn't rely on memory hungry and potentially unsafe
> XML libraries.
>
> On Wed, Mar 5, 2014 at 3:41 AM, Donald Stufft wrote:
>> Just a quick FYI that the last missing
Just a quick FYI that the last missing piece (search) for XMLRPC was merged in
Warehouse today. If you have an application that depends on XMLRPC on PyPI and
you’d like to test it, please try against the url:
https://pypi-preview.a.ssl.fastly.net/pypi
Let me know if you find any issues, or yo
11 matches
Mail list logo