On Thu, 28 Aug 2003, Michal Pasternak wrote:

>  * Python 2.3 should be set as a default version of Python in
>    lang/python/pyversions.mk
>
>  * also some effort should be put to check whether we can add py23 or
>    py23pth to PYTHON_VERSIONS_ACCEPTED in some packages. Packages, which use
>    this variable will _not_ choose Python 2.3, even if it is installed, just
>    because it is not listed there. Such packages are now py-wxWindows
>    and py-twisted (in pkgsrc-wip)
>
>  * I don't think that using old version of Python as a default version for
>    freshly compiled packages is a good idea. Rahter, packages should use
>    2.3 (because it is the latest stable release) - and if any bugs are
>    encountered, such packages should be patched to work with new
>    Python version, or left with current setting of PYTHON_VERSIONS_ACCEPTED
>
>    As Python 2.3 is current stable release, this should the proper way
>    to handle this issue. Please correct me if I'm wrong.
>
>  * I am a little bit worried about pkg-commiters reaction time. Is there any
>    way an user like me could help? Sending PRs or patches gets a little bit
>    pointless, when noone is there to review them. I know, that we all have
>    our own lifes, sometimes wives, kids, cats and dogs to feed and I
>    understand, that many of us will never get paid for working on pkgsrc or
>    NetBSD in general, but I'd really like to see things move in a little bit
>    more dynamical way. Is there anything I could do to help? Oh, yes,
>    I know pkgsrc-wip. Anything else I could do?

	Do you have a reference to a PR or set of patches which permits
	Python 2.3 to be optionally specified by a user to be used in
	pkgsrc and to be used by all (or most) python related packages?
-- 
		David/absolute          -- www.netbsd.org: No hype required --