Well, I do not think it is unfortunate at this point.
As a newuser I would rather have accuracy as opposed to speed (though I
respect that others may be in a different situation).
-Tim
On Wed, 2009-12-02 at 06:33 -0700, Peter A. Bigot wrote:
> Unfortunately, performance took a back seat to vali
When I put PyXB in my setup.py buildout finds PyXB-doc and therefore (no
setup) installation halts.
Even specifying PyXB-full or PyXB-base doesn't help.
My solution so far has been to install it in the local virtualenv
site-packages. When I begin distributing my application I would like
for in
On Fri, 2009-12-04 at 05:52 -0700, Peter A. Bigot wrote:
> I hadn't heard of buildout before you mentioned it. PyXB's PyPI
> presence is somewhat half-hearted, as I've avoided the whole egg thing:
> I really need the distribution to install without requiring tools that
> don't come with Python,
On Fri, 2009-12-04 at 19:59 -0700, Peter A. Bigot wrote:
> OK, I updated PyPI with PyXB 1.1.0 and only installed the full release.
> The base release has everything that's needed to download and translate
> the web service and OpenGIS location schemas that come with the full
> version, and is o
On Sat, 2009-12-05 at 05:45 -0700, Peter A. Bigot wrote:
> Two things:
>
> Based on this, I went ahead and put the base release back up on PyPI.
> Try using "PyXB==base-1.1.0" instead. There are no bundles in that, so
> you might avoid the problem there.
>
Okay, this kind of works. It seem
On Sat, 2009-12-05 at 07:43 -0700, Peter A. Bigot wrote:
> The first problem is probably that there is no egg. I don't use
> easy_install; the release is a compressed tar file of the source. So if
> something's trying to make an egg out of the thing as an intermediate
> step, it'll probably cr
