PyXB already uses a single-source: the python2 version is primary and python3 is derived automatically by it, but not in a way that could be executed at installation time on an arbitrary user system.  Roughly 100 files in the distribution must be changed to work with python3: to a large extent because pyxb must use unicode string literals like u'this' and python3 wouldn't accept that syntax until PEP 414 in version 3.3.  The distribution is big enough I'm not going to put complete source for both versions in the same tar file.

I'll keep my mind open on this, but for the foreseeable future chances are if you want the python3 stuff you'll have to get it from git, not PyPI.  The best chance for a mixed-version source is if I don't support python3 older than version 3.3, which probably isn't feasible for a few more years.

Peter



On Sun, Feb 16, 2014 at 5:02 PM, 翁哲 <wengcsyz@gmail.com> wrote:
Find this might be useful.

stackoverflow.com/questions/2398626/how-to-organize-python-modules-for-pypi-to-support-2-x-and-3-x


2014-02-17 9:45 GMT+11:00 翁哲 <wengcsyz@gmail.com>:

Hi,

Yes, I'm starting to look into this. Besides, I think this is would be a quite beneficial chance for PyXB to add support to python 3.x, whichever a python 2.x and 3.x dual release or a first-go python 3.x release.

Cheers,
John



----- Original Message -----
From: Nathan Robertson <nathanr@nathanr.net>
Date: 12 February 2014 15:50
Subject: Re: [pyxb-users] Python 3.x testing
To: Peter Bigot <bigotp@acm.org>
Cc: PyXB Users <pyxb-users@lists.sourceforge.net>


Ok, I'll get one of my guys to take a look at that in the coming weeks.


On 12 February 2014 14:48, Peter Bigot <bigotp@acm.org> wrote:

> I'm still considering the future of 1.2.x versus 1.3 versus 2.0.  I don't
> anticipate there being a dual release unless there's some way to have the
> same version number with different tar files support python2 and python3
> under PyPI, which seems to be the way most people get PyXB these days.  At
> this time I don't think it's possible to have a source release that
> supports both versions, and I won't be dropping 2.x support, but I'll look
> into that before the next release (whenever that may be).
>
> Peter
>
>
> On Tue, Feb 11, 2014 at 8:23 PM, Nathan Robertson <nathanr@nathanr.net>wrote:
>
>> Hi Peter,
>>
>> Sure, thanks. We're still running 1.2.2 in production at the moment
>> anyway, so we're missing those changes in any case.
>>
>> If you could resync the python3 dev branch at some point in the next few
>> weeks or so that'd be great - I'll be assigning one of my programmers to
>> gradually working away at Python 3.x issues in our code, and once he's done
>> with that we'll be looking to send it to production. Is 1.2.4 intended to
>> be a Python 2.x and Python 3.x dual release?
>>
>> Regards,
>> Nathan.
>>
>>
>>
>> On 12 February 2014 12:28, Peter Bigot <bigotp@acm.org> wrote:
>>
>>> Yes.  I don't keep it up to date with the latest changes to the next
>>> branch (e.g. it doesn't have the xs:decimal changes), but if you have
>>> problems with it I can take a look and resync it.
>>>
>>> Peter
>>>
>>>
>>> On Tue, Feb 11, 2014 at 5:36 PM, Nathan Robertson <nathanr@nathanr.net>wrote:
>>>
>>>> Hi,
>>>>
>>>> More an FYI for Peter than anything else.
>>>>
>>>> A couple of weeks ago we removed our last remaining Python 3.x
>>>> incompatible package (Twisted) after rewriting the code that depended on
>>>> it. So, we're now Python 3.x ready, and so we will begin testing the
>>>> pyxb-1.2.3-DEV branch referenced in Peter's mailing list post of 16th
>>>> September 2013 which works with Python 3.x (I'm assuming that branch is
>>>> still the latest Python 3.x compatible one?).
>>>>
>>>> Anyway, I'll let you know how we go over the coming weeks.
>>>>
>>>> Nathan.
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Android apps run on BlackBerry 10
>>>> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
>>>> Now with support for Jelly Bean, Bluetooth, Mapview and more.
>>>> Get your Android app in front of a whole new audience.  Start now.
>>>>
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> pyxb-users mailing list
>>>> pyxb-users@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/pyxb-users
>>>>
>>>>
>>>
>>
>

--


John Weng | Software Engineer
Les Mills Asia Pacific | john@lesmills.net.au
PO Box 3998 Manuka ACT 2603 AUSTRALIA
tel 0415786645 | fax +612 6282 0563 | www.lesmills.com.au
The contents of this email and its attachments are confidential and privileged. Any unauthorised use of the contents or trademarks is expressly prohibited. If you receive this email in error, please contact us, then delete the email and any attachments. BODYPUMP®, BODYCOMBAT®, BODYBALANCE®, BODYSTEP®, BODYATTACK®, BODYJAM®, RPM™, BODYVIVE®, SH'BAM®, CXWORX®, LES MILLS GRIT™, BORN TO MOVE™, SMARTBAR™ and SMARTSTEP™ are all registered trademarks of Les Mills Asia Pacific.



--


John Weng | Software Engineer
Les Mills Asia Pacific | john@lesmills.net.au
PO Box 3998 Manuka ACT 2603 AUSTRALIA
tel 0415786645 | fax +612 6282 0563 | www.lesmills.com.au
The contents of this email and its attachments are confidential and privileged. Any unauthorised use of the contents or trademarks is expressly prohibited. If you receive this email in error, please contact us, then delete the email and any attachments. BODYPUMP®, BODYCOMBAT®, BODYBALANCE®, BODYSTEP®, BODYATTACK®, BODYJAM®, RPM™, BODYVIVE®, SH'BAM®, CXWORX®, LES MILLS GRIT™, BORN TO MOVE™, SMARTBAR™ and SMARTSTEP™ are all registered trademarks of Les Mills Asia Pacific.