tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: if python version not accepted ...



On Fri, 01 Jan 2010 01:26:20 +0900, Jeremy C. Reed 
<reed%reedmedia.net@localhost> wrote:

py-setuptools is not ported to Python 3 (for example it uses execfile).

http://regebro.wordpress.com/2009/04/21/setuptools-on-python-3-work-on-hold/
(I don't know if that is the latest news.)

So I added to its Makefile:
PYTHON_VERSIONS_INCOMPATIBLE+=  31
I have installed:
python24
python25
python31 (wip)

But building it with PYTHON_VERSION_DEFAULT=31 attempted to install
python26. (Without PYTHON_VERSION_DEFAULT=31 set it will use python25.)

The /pyversion.mk comments say default is 25 but code (non-Darwin) shows
it is really 26.

But it does know to use 25:

t1:py-setuptools$ make show-var VARNAME=PYTHON_VERSION_DEFAULT
25

If I build some other py- packages it defaults to 25, like I expect.

Shouldn't it fail when PYTHON_VERSION_DEFAULT=31 and 31 is incompatible?
If not fail, then shouldn't it use 25 since that is what I have?

I also changed the Makefile to instead use:
PYTHON_VERSIONS_ACCEPTED=       26 25 24

And again with PYTHON_VERSION_DEFAULT=31 it attempted to install
python26.

Shouldn't it just use the python25 as if I didn't use the
PYTHON_VERSION_DEFAULT=31?

PYTHON_VERSION_ACCEPTED is appropriate order, not just descending sequence?

--
"Of course I love NetBSD":-)
OBATA Akio / obache%NetBSD.org@localhost


Home | Main Index | Thread Index | Old Index