On Mon, Nov 24, 2014 at 08:52:21PM +0000, Fred wrote:
> On 11/24/14 15:01, Landry Breuil wrote:
> >On Mon, Nov 24, 2014 at 02:50:06PM +0000, Fred wrote:
> >>On 11/22/14 07:55, Landry Breuil wrote:
> >>>On Sat, Nov 22, 2014 at 12:34:40AM +0000, Fred wrote:
> >>>>Hi Ports@
> >>>>
> >>>>Attached is a port for radio tray an online radio streaming app.
> >>>>
> >>>>I have tested it on i386 and amd64.
> >>>
> >>>Some comments:
> >>>- why hardcoding the python version ?
> >>
> >>This confused me a bit - I'm not sure where I have hard coded the python
> >>version.
> >
> >MODPY_VERSION = ${MODPY_DEFAULT_VERSION_2}
> >
> >You should only use it if you have a reason..
>
> So it's not needed if the code does not work with Python 3?
No reason to prevent it from working someday, even if upstream
development is dormant, a future release might make this work. And given
that if imported, no python3 flavor would be linked to the tree, one
would have to manually set MODPY_VERSION to try building it with py3.
I'm not sure we have a policy on that, but i just find it wrong to force
MODPY_VERSION.
Landry
