Re: policy 2.3 para 2
On Sat, Feb 09, 2002 at 07:41:31PM +0000, Julian Gilbey wrote:
> I have a suggestion, which may already have been thought of.
>
> Need: a python-module (pure Python) providing package should provide
> byte-compiled versions for all installed python versions (as long as
> there are no version dependency issues)
Actually, it is slightly more complex than this. For starters, forgetting
that not all python modules are compatible with all versions of python,
there is a second need;
Need-2: installing a new version of Python should byte-compile all
pre-installed Python modules for the newly installed Python version.
This makes it a bit tricky because it's hard to know where the "compile all
for all" scripts should go; in the versioned Python packages, in the
"Python" default wrapper, or in the modules themselves. The moment you think
it's obvious, you dig deeper and find it introduces some dependancy nastys.
> Parallel: an emacs-module providing package should provide
> byte-compiled versions for all installed emacs versions (as long as
> there are no version dependency issues)
>
> Why not take the emacsen-common method and code and use this for
> python? It probably won't work for C-extension modules, but it could
> make life easier for pure Python ones.
I'm not 100% sure of the details of the emacsen approach, but doesn't it use
some sort of module-registration database? I can't help but think that it's
a bit sad that you need to introduce _another_ database of installed stuff
when you already have the dpkg database. However, perhaps that's the only
way to get a truely "perfect" solution.
--
----------------------------------------------------------------------
ABO: finger abo@minkirri.apana.org.au for more info, including pgp key
----------------------------------------------------------------------
Reply to: