remove the first sentence of this clause ("This License
Agreement shall be governed by and interpreted in all respects by the law of
the State of Virginia, excluding conflict of law provisions.") ?
Is there any reason for you to include this choice of law clause anyway, if
you don't
e, as
well as 2.0, which was not. Cf. README.why-python2 for a more detailed
explanation.
Gregor
* Jérôme Marant <[EMAIL PROTECTED]> [011017 08:31]:
> Matthias Klose <[EMAIL PROTECTED]> writes:
> Quoted from Gregor:
>
> "
> Python package maintainers should then change their packages to build
> python1.5-* and python2.1-* packages (python2.0 if needed),
* Neil Schemenauer <[EMAIL PROTECTED]> [011022 17:47]:
> Anthony Towns wrote:
> > On Mon, Oct 22, 2001 at 10:13:17AM +0200, Gregor Hoffleit wrote:
> > > Say, you would install 2.1.2 in /usr/local.
> >
> > How about we just say "Don't inst
ituation, scripts and packages that
play safe in explicitely stating a Python version have the big advantage
that they will lead to these kinds of problems with underspecified
dependencies.
It's much the same reasoning why libraries have a number in them that
will be increased for incompatible API changes. AFAICS, with the setup
you are suggesting you can never warranty that kind of robustness.
Gregor
* Anthony Towns [011023 17:22]:
> On Tue, Oct 23, 2001 at 02:42:42PM +0200, Gregor Hoffleit wrote:
> > Just to make the discussion a little bit more focussed: I think several
> > issues were mixed up in my original mail:
>
> Sounds like a plan.
>
> > (1) For
, and post all fundamental problems
you have with the content.
If nobody find fundamental show-stoppers that render this unusable,
we're going to submit it to Debian Policy very soon.
Gregor
, and post all fundamental problems
you have with the content.
If nobody find fundamental show-stoppers that render this unusable,
we're going to submit it to Debian Policy very soon.
Gregor
"python" is a real package, no virtual one. I.e. at any given time,
there is only one package "python" on a system (neither python1.5 nor
python2.1 will provide "python").
Gregor
s of Python
(1.6b1, through 2.0 and 2.1) are under a different license (see
below).
Gregor
* Florian Weimer <[EMAIL PROTECTED]> [011107 16:08]:
> Gregor Hoffleit <[EMAIL PROTECTED]> writes:
>
> >> > Python 1.6.1 is essentially the same as Python 1.6, with a few minor
> >> > bug fixes, and with a different license that enables late
package (since the user gets a meaningful
message if something doesn't work due to the lack of the correct Python
version).
Gregor
ode, magic 2000-08-23 (>=2.0.1)
0 lelong 0x0a0deb2aPython bytecode, magic 2001-02-02 (>=2.1.1a1)
0 lelong 0x0a0ded2d Python bytecode, magic 2001-07-17 (>=2.2a2)
(I.e., take the first four bytes of the pyc file and read them as 'long'
in little endian format.) AFAICS, this should suffice for all versions
we have in the distribution.
Gregor
On Fri, Feb 16, 2001 at 04:24:03PM +0100, M.-A. Lemburg wrote:
> Gregor Hoffleit wrote:
> > Is there any reason for you to include this choice of law clause anyway, if
> > you don't live in Virginia ?
>
> I have to make the governing law the German law since that is whe
Python policy, the final
packaging should be coordinated with the C-Python packages, so that we can
re-use as much of the Python library as possible (I don't like to have
jython variants of pure Python packages, adding to the python- and python2-
variants we're already forced to have).
Gregor
On Thu, Apr 26, 2001 at 03:21:32PM -0600, Bruce Sass wrote:
> Here are a couple of files I've found useful and would like to see
> included in the python*-base packages...
Hi Bruce,
would you mind to file an "wishlist" bug report for this ? Just to make sure
that I won't forget it.
Gregor
e).
- Readline support, python-gdbm and python-mpz have been removed, since they
involve GPL code owned by the FSF.
- The SSL module will be packaged separately, since it has to go into
non-US.
Please report any problems or suggestions to me.
Gregor
--
Gregor HoffleitMe
g the transition
process.
What do you think ?
Gregor
On Tue, Jun 26, 2001 at 12:47:28AM +1000, Anthony Towns wrote:
> On Mon, Jun 25, 2001 at 04:36:28PM +0200, Gregor Hoffleit wrote:
> > This would mean that I upload new versions of the Python packages:
> > (1) python2 (python2-base etc.) would be removed
> > (2) python 2.0
the policy of dependencies and paths for the Python
packages at some point.
Gregor
On Mon, Jun 25, 2001 at 05:42:30PM +0200, Radovan Garabik wrote:
> On Mon, Jun 25, 2001 at 05:21:39PM +0200, Gregor Hoffleit wrote:
> >
> > With the default setup, stuff in /usr/lib/python1.5/site-packages would be
> > ignored by 2.0.1. In order to make the transition ea
d don't
> want to include the interpreter, this becomes a more noticable
> issue.
- If we want to support concurrent Python versions and still don't want
to have multiple packages for each Python extension, a setup like the
Debian Emacsen system might be a solution:
Th
ce: idle", and/or to "Provide:
idle", but to no avail:
apt-get always will remove idle, but not install the new idle-python1.5.
I have no idea why.
I don't want to make another empty transitional package "idle" if it's
not necessary. Certainly providing such an package would resolve that
problem, but that's ugly.
Gregor
* Jérôme Marant <[EMAIL PROTECTED]> [010904 11:18]:
> Matthias Klose <[EMAIL PROTECTED]> writes:
>
> ...
> > in June (2.1) and July (2.1.1). Gregor (the python-1.5 and python-2.0
> > maintainer) has put experimental packages at
> > http://people.debian.org
t; > > on alpha debian, python 2.1.1-8:
> > > >
> > > Works for me, no aborts. (i386, python 2.1.1-8)
> > Just compare the platform... :)
> I did. So its a platform specific bug.
Cf. http://bugs.debian.org/106421.
Gregor
Hi,
I will be away from my email from 18 May until 31 May. If something
urgent occurs with one of my packages, please NMU. In the case of
Python, Matthias Klose <[EMAIL PROTECTED]> is your preferred contact of
course.
Gregor
PS: I will be in Alicante, Spain during that time (perhap
mport *
>>>
With python2.1-egenix-mxdatetime installed, it works as well.
Could you tell me which versions of the package you have installed ? Do
you have python2-egenix-mxdatetime installed ?
Gregor
Mit freundlichen Grüßen
Gregor Rosmanek
Infracor Gmbh
Logistik / Gütereingang
Tel.: 02365 / 494405
Fax : 02365 / 496530
eMail : gregor. rosmanek@ infracor.de
the new version of python-cogent needs python-loky[1] which I tried to
package. Unfortunately there is some issue with the build-time test
which times out[2]. Any help is welcome.
Why do you think it's the build-time test?
The build output looks quite strange to me.
It almost seems like it
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099038
My question is why pytest try to create a file in the modules system library ?
My guess is that it's because the tests are executed from the module
installation directory.
If you look at the debci output[1], you'll see lots of paths li
Does a separate package with the elasticsearch8 namespace have to be created
and maintained here or should a meta package be set up?
Unfortunately, elasticsearch8 is required as a dependency for existing packages
in Debian that need to be updated, as well as for new dependent packages.
Do thes
101 - 131 of 131 matches
Mail list logo
