Hi Peter,
We've been using 1.2.4-DEV in production on Python 3 (currently 3.4.1)
since that branch was created and announced on the mailing list. We've
found it to be stable and reliable - we've got roughly 200'000 lines of
code (mixed Java JAXB and Python PyXB), and about 4700 lines of XML schema.
So we've been running a fairly large application in production with PyXB on
Python 3.x for quite a while now.
We have our own internal pypiserver with mirrors of the versions of the
packages we use, and created a 1.2.4-DEV PyPI package (probably 3.x only,
but we only use 3.x) and put it there.
I'd personally like to thank you for creating 1.2.4-DEV. Before that point,
PyXB was the only element in our stack that we could neither substitute
with another 3.x compantible product, or upgrade to a 3.x compatible
version. Even though it wasn't tagged as a production release, we found it
stable, and it allowed us to upgrade to 3.x.
Michael: We also backported the RPMs for Python 3.4.1 from RawHide to RHEL
6. It took us a day to figure it out, but that's also in production now,
and served out of our internal yum repo. I gather that updated Python
packages wouldn't usually qualify for EPEL, but given given python3-* isn't
in the base RHEL 6 distro I'm guessing it may qualify.
Regards,
Nathan.
On 20 August 2014 21:39, Peter Bigot <big...@acm.org> wrote:
> There is no planned release date; it's whenever I get tired of working
> on other things and turn attention to PyXB. 1.2.5 is more likely than
> 1.3.0, and python3 will be part of 1.3.0. The hold-up there is that
> PyXB includes generated bindings for a large number of schema, and at
> this time I don't believe the bindings generated under python2 work
> for python3 or vice-versa. Since PyPI doesn't allow me to have two
> packages no release can officially support both until I figure out a
> solution to that.
>
> The more people express an interest the more likely it'll happen. It
> also tends to be correlated to bug reports, which also get me working
> on PyXB. FWIW, development (including bug reports) is now hosted on
> github at https://github.com/pabigot/pyxb though I'll still push
> release packages onto sourceforge.
>
> Peter
>
> On Wed, Aug 20, 2014 at 5:15 AM, Michal Srb <m...@redhat.com> wrote:
> > Hi,
> >
> > I'm a maintainer of PyXB package in Fedora and I'm really looking
> > forward to PyXB 1.2.4 (or 1.3.0?) release with official Python 3
> > support. I would like to ask if there is any ETA on when it could be
> > officially released.
> >
> > Thanks and regards
> > Michal
> >
> >
> ------------------------------------------------------------------------------
> > Slashdot TV.
> > Video for Nerds. Stuff that matters.
> > http://tv.slashdot.org/
> > _______________________________________________
> > pyxb-users mailing list
> > pyxb-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/pyxb-users
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds. Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> pyxb-users mailing list
> pyxb-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pyxb-users
>
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
pyxb-users mailing list
pyxb-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pyxb-users
