On Wed, Mar 05, 2014 at 07:01:49AM -0500, Donald Stufft wrote:
On Mar 5, 2014, at 5:48 AM, anatoly techtonik techto...@gmail.com 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
On Wed, Mar 5, 2014 at 3:01 PM, Donald Stufft don...@stufft.io 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
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 techto...@gmail.com wrote:
JSON-RPC is a better choice for recommended external API,
because it doesn't rely on memory hungry and potentially
On Mar 6, 2014, at 4:10 AM, Marius Gedminas mar...@pov.lt wrote:
On Wed, Mar 05, 2014 at 07:01:49AM -0500, Donald Stufft wrote:
On Mar 5, 2014, at 5:48 AM, anatoly techtonik techto...@gmail.com wrote:
JSON-RPC is a better choice for recommended external API,
because it doesn't rely on memory
On Thu, Mar 6, 2014 at 3:28 PM, Donald Stufft don...@stufft.io wrote:
On Mar 6, 2014, at 4:10 AM, Marius Gedminas mar...@pov.lt wrote:
On Wed, Mar 05, 2014 at 07:01:49AM -0500, Donald Stufft wrote:
On Mar 5, 2014, at 5:48 AM, anatoly techtonik techto...@gmail.com wrote:
JSON-RPC is a better
Hi Distutils !
I don’t follow this list and haven’t looked at it in a long time. However,
I’m learning via twitter that a brand new setuptools release that’s just gone
out has just removed the “Feature” mechanism.
Now as you’re all rolling your eyes and preparing to bang out frustrated
On Mar 6, 2014, at 12:55 PM, Michael Bayer mike...@zzzcomputing.com wrote:
Hi Distutils !
I don’t follow this list and haven’t looked at it in a long time. However,
I’m learning via twitter that a brand new setuptools release that’s just gone
out has just removed the “Feature”
pje said:
The Feature() facility was never completely implemented or
supported, and even if it were, it should be deprecated now, as it
will not be compatible with the coming packaging systems based on PEP
426. If you need separate features, use separate distributions and
extras instead.
(The
On Mar 6, 2014, at 12:55 PM, Michael Bayer mike...@zzzcomputing.com wrote:
changelog! Or the setuptools blog. Or this list. I assume you guys have it
under control (and you certainly do!). There seem to be other people like me
(people
please note this correction to my last email: “I
On Mar 6, 2014, at 1:07 PM, Daniel Holth dho...@gmail.com wrote:
pje said:
The Feature() facility was never completely implemented or
supported, and even if it were, it should be deprecated now, as it
will not be compatible with the coming packaging systems based on PEP
426. If you need
It is certainly broken.
On Thu, Mar 6, 2014 at 1:37 PM, Michael Bayer mike...@zzzcomputing.com wrote:
On Mar 6, 2014, at 1:07 PM, Daniel Holth dho...@gmail.com wrote:
pje said:
The Feature() facility was never completely implemented or
supported, and even if it were, it should be
Michael Bayer mike_mp at zzzcomputing.com writes:
I don’t know the metadata format in pep426 well enough to comment (as I
wanted to use it one day and found
that it seemed to still be pretty much vapor), but I’ll reiterate: these
are source distributions, not
binaries or wheels or anything
On Mar 6, 2014, at 2:59 PM, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
Michael Bayer mike_mp at zzzcomputing.com writes:
I don’t know the metadata format in pep426 well enough to comment (as I
wanted to use it one day and found
that it seemed to still be pretty much vapor), but I’ll
On Thu, Mar 6, 2014 at 10:37 AM, Michael Bayer mike...@zzzcomputing.comwrote:
On Mar 6, 2014, at 1:07 PM, Daniel Holth dho...@gmail.com wrote:
pje said:
The Feature() facility was never completely implemented or
supported, and even if it were, it should be deprecated now, as it
will
Donald Stufft donald at stufft.io writes:
2. Use older versions of setuptools
That's not really an answer, unless downgrading works. For example, a
recently created venv would contain the latest setuptools, and perhaps it
would be required by other distributions in the venv. How then would
On Mar 6, 2014, at 4:15 PM, Marcus Smith qwc...@gmail.com wrote:
On Thu, Mar 6, 2014 at 10:37 AM, Michael Bayer mike...@zzzcomputing.com
wrote:
On Mar 6, 2014, at 1:07 PM, Daniel Holth dho...@gmail.com wrote:
pje said:
The Feature() facility was never completely
From:Michael Bayer mike...@zzzcomputing.com
OK so why does PEP-426 compatibility imply removal of command line switches
from setup.py files ?
As far as I know, it doesn't. My distil tools complies with a fairly recent
version of PEP 426 and AFAIK has no problem building / installing
This is my understanding as well except it inverses the default.
SQLAlchemy wants the C exts installed unless they can't be if the user opts
out. Extras would cause if to not be installed unless the user opts in.
This is probably not a reasonable solution.
ok, that's odd, so there is no
On Mar 6, 2014, at 4:35 PM, Marcus Smith qwc...@gmail.com wrote:
This is my understanding as well except it inverses the default. SQLAlchemy
wants the C exts installed unless they can't be if the user opts out. Extras
would cause if to not be installed unless the user opts in. This is
Hello,
I proposed a patch https://github.com/pypa/pip/pull/1465 to pip, with
respect to treatment of the platform tag on OS X, and Chris Barker proposed
that I bring the discussion here.
The situation:
PEP 425 describes the platform tag as:
The platform tag is simply
In article
cahnn8bw+ufqrfqsuszq81whm+xtheb-rp-d9na0tkttgjph...@mail.gmail.com,
MinRK benjami...@gmail.com wrote:
I proposed a patch https://github.com/pypa/pip/pull/1465 to pip, with
respect to treatment of the platform tag on OS X, and Chris Barker proposed
that I bring the discussion here.
On Thu, Mar 6, 2014 at 4:27 PM, MinRK benjami...@gmail.com wrote:
I proposed a patch https://github.com/pypa/pip/pull/1465 to pip, with
respect to treatment of the platform tag on OS X, and Chris Barker proposed
that I bring the discussion here.
Note -- there is some more discusion on that
On Mar 6, 2014, at 7:28 AM, Donald Stufft don...@stufft.io 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]
23 matches
Mail list logo
