First, ensure you're using the latest setuptools -- 0.6c9.
If the problem still occurs, try running easy_insatll with the -v
(verbose) option. Otherwise we can't tell what actually happened here.
--
Philip Jenvey
http://files.turbogears.org/eggs/
I compile and upload binary eggs for simplejson on as much platform as
I can and I regularly do so for Windows (py24 & py25), Linux (py25)
and Macos 10.5 (py25)
Florent.
If you're in a pinch and can't get simplejson to work, there are some
other JSON modules that are pure python. The calling interfaces may
be just slightly different, but not much. It should be very easy to make
a simple wrapper for any of them that completely replicated the
simplejson interface if you need it.
See http://deron.meranda.us/python/comparing_json_modules/
and my own module at
http://deron.meranda.us/python/demjson/
My module actually can be trimmed to just a single *.py
file which can be very easily installed if needed, or just dropped
into your own project.
Note that Python 3.0 has officially included simplejson (although
being renamed). But most of the various modules by all the
authors do a pretty decent job of JSON handling now.
--
Deron Meranda
People aren't installing simplejson because they're using it; they're
installing it because it's a Pylons dependency. So you either have to
download Pylons manually and hack setup.py, or find some way to get
simplejson installed. It's only used for the @jsonify decorator.
I've argued for dropping the dependency or downgrading it to the older
simplejson that doesn't have this install problem, but was overruled
by "hopefully simplejson will fix their package soon".
--
Mike Orr <slugg...@gmail.com>
AFAICT this is a new problem (at least I don't recognize it). Just to
clarify I did submit fixes for all the issues we encountered (to both
setuptools and simplejson), we were just waiting for the
setuptools-0.6c9 release, which was overdue anyway. That's been out
for over a month now.
Maybe we should reconsider dropping it -- I don't like a lot of
dependencies either -- but first I'd like to know what the actual
problem is here.
--
Philip Jenvey
I'm not sure what the problem is, but if someone gives me a patch that
makes simplejson easy_install from Windows then I'll apply it. I
don't/won't use Windows or care about Windows at work so it's not a
priority of mine. The current implementation of setup.py that tries to
allow Windows users to build without a compiler was contributed and
applied because it doesn't negatively affect the platforms I care
about. If someone contributes a better patch I'll gladly apply it. In
the same vein I'll accept people to manage Windows binary releases if
that's what's necessary.
simplejson works just fine with or without the C extension and works
everywhere I've needed it (Mac OS X, FreeBSD, Linux). Every bug that's
ever been filed has been fixed. It's actually quite fast (at least in
recent incarnations) without the C extension because it was optimized
as far as I could get it without C, and then I beefed up the extension
to get those extra cycles wherever possible because we use it so
extensively at Mochi Media (probably gigabytes a day if not more). For
our data simplejson 2.x is faster than cPickle, so it's our
serialization de jour for internal and external stuff.
If you come up with a fix, the right place to contribute it is
http://code.google.com/p/simplejson/issues/list -- don't be daunted by
the lack of other open issues; it's only empty because there are no
known bugs (other than perhaps Windows packaging related issues, which
get closed as WontFix without a working patch).
-bob
I could handle binary builds and help for the upload to pypi if you're
interested.
Florent.
Absolutely, just let me know what your PyPI username is and I'll grant
you maintainer access to provide Windows builds. I don't hear any
complaints from anyone else (and even Windows users don't generally
voice them directly). The responsibilities for a binary maintainer
are:
1. Follow PyPI and/or http://bob.pythonmac.org/ to watch for releases
(I don't blog much and release even less frequently)
2. Provide Windows builds for the versions of Python that Windows
users care about (I'm guessing 2.4, 2.5, 2.6). simplejson was
compatible at 2.3 a long time ago, but that compatibility has not been
maintained (it may still work, but I haven't heard anything one way or
the other). I'm not sure what the 64-bit story is for Windows users
is, so that might potentially add a couple extra build configurations.
If you can't provide all build configurations for Windows that's fine
too, some is certainly better than none!
-bob
florentaide
I can handle win (py24 & py25) linux (py25) macos 10.5 (py25)
Florent.
Done.
-bob