D-Man <[EMAIL PROTECTED]> writes:
> Yes. Maybe each extension should just depend on a single version of
> python and need to be rebuilt for each new python release.
It makes things considerably simpler, from my point of view.
Then, of course, we need unique package names for each package.
Somet
D-Man <[EMAIL PROTECTED]> writes:
> Say, ..., is there a way for a python script to find out where the
> python binary executing it is? If so, then the "real" script could be
> run via os.system by the Debian script that uses #! deb_py_ver.
sys.executable, which comes from argv[0] in Py_Main(),
On Sat, Jul 14, 2001 at 01:07:21PM +1200, Carey Evans wrote:
| D-Man <[EMAIL PROTECTED]> writes:
| > Sure, but also consider older packages. For example, we are now
| > moving to 2.0 (or 2.1) for the "default" python. We still want to
| > provide 1.5.2 versions of all the other packages, so the
D-Man <[EMAIL PROTECTED]> writes:
> It might be more convenient, unless a user, for some strange reason,
> wants to only have an older version of python.
In which case they won't have anything else installed that depends on
"python", and they'll just install "python-2.1", for example, and
never s
On Sat, Jul 14, 2001 at 01:30:17AM +0200, Carel Fellinger wrote:
| On Fri, Jul 13, 2001 at 07:05:17PM -0400, D-Man wrote:
| ...
| > Ok, sure, replace the space separator between the versions with a
| > different ASCII separator.
|
| Won't do either, as this would make it impossible to pass default
On Sat, Jul 14, 2001 at 11:27:55AM +1200, Carey Evans wrote:
| D-Man <[EMAIL PROTECTED]> writes:
|
| > o all core (the interpreter) python packages will be versioned
| > ex
| > python-1.5.2
| > python-2.0
| > python-2.1.1
| >
| > Each of these will contain /usr/b
On Fri, Jul 13, 2001 at 07:05:17PM -0400, D-Man wrote:
...
> Ok, sure, replace the space separator between the versions with a
> different ASCII separator.
Won't do either, as this would make it impossible to pass default
options like:
#!/usr/bin/python -u
I know, this also doesn't work with
D-Man <[EMAIL PROTECTED]> writes:
> o all core (the interpreter) python packages will be versioned
> ex
> python-1.5.2
> python-2.0
> python-2.1.1
>
> Each of these will contain /usr/bin/pythonX.Y.Z and "provide"
> 'python'.
It might be more convenient to ha
On Fri, Jul 13, 2001 at 06:27:20PM -0400, David M. Cooke wrote:
| At some point, D-Man <[EMAIL PROTECTED]> wrote:
| > On Fri, Jul 13, 2001 at 11:30:28PM +0200, Carel Fellinger wrote:
| > | On Fri, Jul 13, 2001 at 03:25:20PM -0400, D-Man wrote:
| > | ...
| > | > o The #! line should look something
On Fri, 13 Jul 2001, D-Man wrote:
> On Fri, Jul 13, 2001 at 11:30:28PM +0200, Carel Fellinger wrote:
> | On Fri, Jul 13, 2001 at 03:25:20PM -0400, D-Man wrote:
> | ...
> | > o The #! line should look something like
> | > #!/usr/bin/deb_py_ver 1.5.2 -
> |
> | I can't get things like this t
At some point, D-Man <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 13, 2001 at 11:30:28PM +0200, Carel Fellinger wrote:
> | On Fri, Jul 13, 2001 at 03:25:20PM -0400, D-Man wrote:
> | ...
> | > o The #! line should look something like
> | > #!/usr/bin/deb_py_ver 1.5.2 -
> |
> | I can't get th
On Fri, Jul 13, 2001 at 11:30:28PM +0200, Carel Fellinger wrote:
| On Fri, Jul 13, 2001 at 03:25:20PM -0400, D-Man wrote:
| ...
| > o The #! line should look something like
| > #!/usr/bin/deb_py_ver 1.5.2 -
|
| I can't get things like this to work. It seems one parameter at
| most is al
On Fri, Jul 13, 2001 at 03:25:20PM -0400, D-Man wrote:
...
> o The #! line should look something like
> #!/usr/bin/deb_py_ver 1.5.2 -
I can't get things like this to work. It seems one parameter atmost is
allowed there. That's why I proposed this symlink trick the other day.
Then the fi
Last night I had an idea for organizing multiple python versions in
Debian.
o all core (the interpreter) python packages will be versioned
ex
python-1.5.2
python-2.0
python-2.1.1
Each of these will contain /usr/bin/pythonX.Y.Z and "provide"
'python'.
/u
On Fri, Jul 13, 2001 at 11:44:33AM +0200, Radovan Garabik wrote:
| To add to the multiple python versions confusion:
| jython recently appeared in debian.
| To make things correctly, it should be possible to
| use it as replacement of python, and also it should be
| possible to have both python an
On Thu, Jul 12, 2001 at 04:55:59PM -0600, Bruce Sass wrote:
...
> I'm a little confused...
> A solution to the problem has already been proposed in previous
> discussions on this list -- and I though it had already (at least)
> started to be implemented...
Sorry, I just recently subscribed to this
To add to the multiple python versions confusion:
jython recently appeared in debian.
To make things correctly, it should be possible to
use it as replacement of python, and also it should be
possible to have both python and jython installed
simultaneously.
and, of course, C modules and many pur
On Wed, Jul 11, 2001 at 05:30:03PM +0200, Gregor Hoffleit wrote:
> On Wed, Jul 04, 2001 at 09:00:06PM -0500, Chris Lawrence wrote:
> > My semi-well-thought-out solution:
> > - python-* should provide a "Standard" Python for each Debian
> > release. 2.1.1 seems a sensible target for woody. These
18 matches
Mail list logo
