daniel 6b9e710437 use a FULL_VERSION variable in Python Makefiles ...

The goal is to shuffle things around allowing us to use this variable in
the packing lists. This should reduce a little bit of churn going
forward given some files get bumped with every point release.

For example in Python 3.9 we make the following update:

-lib/python3.9/lib2to3/Grammar3.9.10.final.0.pickle
+lib/python3.9/lib2to3/Grammar${FULL_VERSION}.final.0.pickle

-lib/python3.9/lib2to3/PatternGrammar3.9.10.final.0.pickle
+lib/python3.9/lib2to3/PatternGrammar${FULL_VERSION}.final.0.pickle

ok kmos@ (MAINTAINER), sthen@

2022-01-23 21:32:07 +00:00

..

2.7

use a FULL_VERSION variable in Python Makefiles

2022-01-23 21:32:07 +00:00

3.8

use a FULL_VERSION variable in Python Makefiles

2022-01-23 21:32:07 +00:00

3.9

use a FULL_VERSION variable in Python Makefiles

2022-01-23 21:32:07 +00:00

3.10

use a FULL_VERSION variable in Python Makefiles

2022-01-23 21:32:07 +00:00

Makefile

Hook Python 3.10 into build and add the necessary bit to python.port.mk

2021-11-01 14:17:16 +00:00

Makefile.inc

use a FULL_VERSION variable in Python Makefiles

2022-01-23 21:32:07 +00:00

python.port.mk

fix conflict markers in comments

2021-11-03 19:08:27 +00:00