Re: [gentoo-portage-dev] [RFC] Naming Conventions

[Brian Harring]

On Sat, Jul 22, 2006 at 04:25:01PM -0700, Zac Medico wrote:
> Chris White wrote:
> > 1) Create aliases to the new functions, then at some
> > yet-to-be-determined point, kill the aliases and bomb on the scripts
> > (this suffers from procrastination).
> >
> > 2) Make an official release with the new function names and no aliases,
> > as well as the soon to come docs.  I sort of like this method because
> > those with official portage tools can adjust their scripts, and simply
> > alter the depend atoms for >= (new API versions) and <= (old versions),
> > effectively forcing/preventing upgrades.
>
> I vote for #1 because it's smoother and easier (which is good for me especially because I do releases).  The disruptive change proposed in #2 seems like it would cause unnecessary problems with no practical advantage over #1.

Suggest you mark the aliases funcs in some way in the code so that 
they can be spotted via scanning.

Use a convience func; 

def alias_func(alias_name, alised_func):
	def f(alias_name, aliased_func, *a, **kw):
		import warnings
		warnings.warn("don't use %s, use %s" % (alias_name, alias_func.__name__)
		return aliased_func(*a, **kw)
	return f

pkgsplit = alias_func('pkgsplit', PkgSplit)

upshot, you can puke warnings via it, and you've got something to scan 
the actual namespace for; makes it quite a bit easier to switch off 
the aliases.
~harring