Re: Proposal: Reorganizing Python for Python 2.0

2001-01-09 Thread D-Man
It sounds good to me. I think the admin should have the option of setting the symlinks to default to 1.5 or 2.0. -D On Tue, Jan 09, 2001 at 03:04:33PM +0100, J?r?me Marant wrote: | [snip proposal for multiple version installation] | -- | Jérôme Marant <[EMAIL PROTECTED]>

Re: Proposal: Reorganizing Python for Python 2.0

2001-01-09 Thread D-Man
solution that's fine as well. -D On Tue, Jan 09, 2001 at 06:31:31PM +0100, J?r?me Marant wrote: | D-Man <[EMAIL PROTECTED]> writes: | | > It sounds good to me. I think the admin should have the option of | > setting the symlinks to default to 1.5 or 2.0. | | Sorry, I can&#

Re: Proposal: Reorganizing Python for Python 2.0

2001-01-10 Thread D-Man
On Wed, Jan 10, 2001 at 08:53:39AM +0100, J?r?me Marant wrote: | D-Man <[EMAIL PROTECTED]> writes: | | > If you have a different solution that's fine as well. | | The whole stuff is handled by alternatives. | See update-alternatives manpage. | Oh, ok. Another part of the

Re: Proposal: Reorganizing Python for Python2 (and fixes for the previous proposal)

2001-01-10 Thread D-Man
On Wed, Jan 10, 2001 at 09:16:51AM -0600, Rob Tillotson wrote: | [EMAIL PROTECTED] (Jérôme Marant) writes: | > And thanks to a small change in the interpreter, the current version | > looks for modules in /usr/lib/python//site-packages and | > then /usr/lib/python/site-package. Other modules

Re: Proposal: Reorganizing Python for Python 2.0

2001-01-10 Thread D-Man
On Wed, Jan 10, 2001 at 12:32:02PM -0800, Neil Schemenauer wrote: | On Wed, Jan 10, 2001 at 11:01:40PM +0100, [EMAIL PROTECTED] wrote: | > What I want is if we allow both Python 1.5 _and_ Python 2.0 to be | > So we need | > ... | | No, we don't. Python already installs its modules into | | $

Re: Our application doesn't work with Debian packaged Python

2001-01-16 Thread D-Man
On Tue, Jan 16, 2001 at 11:44:48AM +0200, Danie Roux wrote: [snip] | | I then went and look at the source rpm. They have this patch in there: | | --- Python-1.5.2/Python/importdl.c.global Sat Jul 17 16:52:26 1999 | +++ Python-1.5.2/Python/importdl.cSat Jul 17 16:53:19 1999 | @@ -441,13 +44

Re: RFC: python-base, debconf and py/pyc files

2001-03-23 Thread D-Man
I think this sounds good. Then users who don't want to use the extra disk space don't have to. There is another tradeoff though. I compared the size of several .py and the corresponding .pyc files from the standard library and noticed that the .pyc file is a little bit larger. If the user li

Re: Python 2.1 out

2001-04-18 Thread D-Man
On Wed, Apr 18, 2001 at 10:25:52PM +0200, Florian Weimer wrote: | Steve Purcell <[EMAIL PROTECTED]> writes: | | > Licenses aside, there are the same technical issues with Python 2.1 | > as with Python 2.0. | | Python 2.1 seems to print some diagnostic messages during run-time; | this might affec

Re: Python 2.1 out

2001-04-19 Thread D-Man
On Thu, Apr 19, 2001 at 12:17:40PM +0200, Florian Weimer wrote: | Gregor Hoffleit <[EMAIL PROTECTED]> writes: | | [Python warning messages] | | > Could you mail an example of such a message ? | | y = None | def fun(): | y = None | def bar(): | y | bar() | | fun() | | result

Re: Status report on python2 transition

2001-07-05 Thread D-Man
On Thu, Jul 05, 2001 at 06:43:08PM +0100, Aquarius wrote: | In article <[EMAIL PROTECTED]> you wrote: | > I just browsed /usr/bin and /usr/sbin, and indeed there are plenty of | > scripts that use "#!/usr/bin/env python". If we consider the possibility | > that somebody installs non-compatible Pyth

Re: jython

2001-07-13 Thread D-Man
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

Re: Status report on python2 transition (possible solution)

2001-07-13 Thread D-Man
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

Re: Status report on python2 transition (possible solution)

2001-07-13 Thread D-Man
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 a

Re: Status report on python2 transition (possible solution)

2001-07-13 Thread D-Man
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 Th

Re: Status report on python2 transition (possible solution)

2001-07-13 Thread D-Man
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

Re: Status report on python2 transition (possible solution)

2001-07-13 Thread D-Man
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 impossi

Re: Status report on python2 transition (possible solution)

2001-07-13 Thread D-Man
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 a

Re: Status report on python2 transition (possible solution)

2001-07-14 Thread D-Man
On Sat, Jul 14, 2001 at 04:05:56PM +1200, Carey Evans wrote: | 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