Changes in python_mod_optimize(), python_mod_cleanup() and python_mod_compile()
2010-05-25 21:11:44 Petteri RÃ¤ty napisaÅ‚(a):
> On 05/25/2010 09:35 PM, Arfrever Frehtes Taifersar Arahesis wrote:
> > - Not passing of paths to python_mod_optimize() and python_mod_cleanup() has been
> > deprecated and will be disallowed on 2010-09-01. You should pass paths to Python
> > modules to these functions.
> > - python_mod_compile() has been deprecated and will be banned on 2010-09-01.
> > You should use python_mod_optimize() instead of python_mod_compile().
> 1. Messages to gentoo-dev-announce should also be posted to an on topic
> mailing lists
I don't like crossposting.
> 2. What does disallowed and banned mean in this case? Plenty of ebuilds
> currently pass paths to python_mod_optimize.
Ebuilds, which pass paths to python_mod_optimize() / python_mod_cleanup(),
don't need any changes. Ebuilds, which don't pass paths to python_mod_optimize()
or python_mod_cleanup(), should now pass paths to these functions.
Only small minority of ebuilds don't pass paths to these functions.
python_mod_optimize() without paths hasn't been doing anything for almost 2 years.
python_mod_cleanup() without paths allows for silently incorrect behavior.
Not passing of paths to python_mod_cleanup() is incorrect in many ebuilds.
> If you break the stable tree, you should have the wrath of more people than me.
> It can be done at the dates you say if the tree is in order by then.
I'm not breaking anything. Deprecation warnings won't be changed into calls to
die() until all ebuilds in gentoo-x86 are fixed.
It's possible to deprecate and ban functions or their parts as it was discussed
in "Deprecation of python_version(), python_mod_exists(), python_tkinter_exists(),
distutils_python_version() and distutils_python_tkinter() in EAPI <=2" thread .
Arfrever Frehtes Taifersar Arahesis