A recent review of my package asked me to consider making a python3 version. But the response below says that is difficult. It is several months old, has this changed? The other problem is that the package is an extension and there is currently no python3 program to test it. Should packagers create a python3 extension even if there is no way to test it? It might be a chicken and egg problem. Thank You On Thursday, November 17, 2011 05:55:20 AM Stefano Rivera wrote: > Hi Paul (2011.11.17_12:05:46_+0200) > > > I created a package with py2dsc. After some tweeks, it works correctly. > > The upstream says package also works with python 3. How do I alter my > > source package to also produce a python 3 version? > > That's currently non-trivial, and certainly not in the realm of things > py2dsc can safely do, yet. > > Basically, you'd need to override all the dh_auto_* rules to loop over > all supported python2 and python3 versions. > > If you don't need the python3 version, yet, I'd ignore this until the > tools improve. > > SR -- Paul Elliott 1(512)837-1096 pelliott@BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117
Attachment:
signature.asc
Description: This is a digitally signed message part.