"Maciej (Matchek) Bliziński" <[email protected]> writes: > 2013/8/1 Yann Rouillard <[email protected]>: >> Ok, maybe we should try to include python 3 in the reflection to be sure it >> doesn't bring some new problem. This way we could define a consistent policy >> for Python. >> >> If I understand well, we will prefix all python 3 modules with CSWpy33- our >> CSWpy3- ? > > I was thinking CSWpy3-. > > Before we do anything, let's (as always) look closer at what's Debian > doing and why.
They have python3 as a prefix when for 2.x they have a naked python prefix. >> It seems for python 3, they tried to define a stable ABI / API subset: >> http://www.python.org/dev/peps/pep-0384/ > > My current working assumption is that we will have one module location > for all Python 3 minor versions. It's just the question of figuring > out a way the module build scripts to put files where we want them. We want them in /opt/csw/lib/python3.3 and from the upstream build system is what they do anyway. -- Peter _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
