, people can either use the complete Zope packge
or simpleTAL.
Any opinions?
Ciao,
- --
.~.Bastian Kleineidam . calvin (at) debian.org
/V\
/( )\ GnuPG SchlÃssel http://kampfwurst.net/gpgkey.txt
^^-^^
F: Was hat vier Beine und einen Arm?
A: Ein glÃcklicher Pitbull-Terrier
-BEGIN
s. You can look up bugs quickly at
http://bugs.debian.org/
Thanks anyway for your report, and welcome to the Debian information
djungle 8)
ciao, Bastian
- --
.~.Bastian Kleineidam . calvin (at) debian.org
/V\
/( )\ GnuPG Schlüssel http://kampfwurst.net/gpgkey.txt
^^-^^
Oh no! N
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, May 13, 2003 at 11:40:45PM -0400, Matt Zimmerman wrote:
> > Yup, ok. I will see if I can identify packages using rexec or Bastion
> > and provide patches for them instead of disabling modules.
>
> Were you able to make any progress with this?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, May 09, 2003 at 04:03:28PM +0200, Martin SjÃgren wrote:
> Why would we need the python documentation to build our own
> documentation?
What do you mean with "our own"?
> Tell me about it! Look at the build-dependencies for src:pyopenssl,
> tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, May 09, 2003 at 10:26:57AM +0200, Alexandre Fayolle wrote:
> * file a bug report against the python packages, requesting a
> python-doc-tools package to be added to the debian archive
I'suggest not a new package, but inclusion in pythonX.Y-doc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Apr 18, 2003 at 12:25:08PM +0200, Tim Dijkstra wrote:
> On Fri, 18 Apr 2003 11:22:11 +0200
> Luca - De Whiskey's - De Vitis <[EMAIL PROTECTED]> wrote:
> > file:///usr/share/doc/python/python-policy.txt.gz (that is shipped
> > with the "python"
ng on either of the library packages. The user can decide
which pythoncard version to use for the samples.
python2.2-pythoncard Depends: python2.2
python2.3-pythoncard Depends: python2.3
pythoncard-doc Depends: python2.2-pythoncard | python2.3-pythoncard
Greetings,
- --
Bastian Kleineidam
of disabling modules.
Cheers, Bastian
- --
Bastian Kleineidam
Atombombe  Plutonium  Fat Man  Do it Yourself  Tim Taylor
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+MBnOeBwlBDLsbz4RAvkdAKDJwrV2OBbeoaO4jkKYNlsCfPapeQCeMa/x
KjqJsBk60KpWPQ2GL/nstRI=
=DgqG
-END PGP SIGNATURE-
=mailman.1041875417.12807.clpa-moderators%40python.org
I suggest to disable the above two modules in python2.2 (which is in
woody), even if existing applications can break. What do you think?
Cheers, Bastian
- --
Bastian Kleineidam
Atombombe  Plutonium  Fat Man  Do it Yourself  Tim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Nov 10, 2002 at 12:55:36PM +0200, Kai Hendry wrote:
> test.py is:
> import re
> p = re.compile('[a-z]+')
> print p
>
> The first error message is from python2.1, python2.2 and last
> python2.3 from SID.
>
> [EMAIL PROTECTED]:/tmp$ vim test.py
umption that i should know?
Yeah, he should probably mailed you of his efforts. But anyway,
are you going to upload a new python-tal version or use the already-uploaded
one?
Cheers,
Bastian
--
Bastian Kleineidam
reflexionsniveau AT web.de
calvin AT users.sf.net
calvin AT debian.org
pgp
more, just
wanted to let you know that python-register can even be used for mailman.
cu, Bastian
--
Bastian Kleineidam
reflexionsniveau AT web.de
calvin AT users.sf.net
calvin AT debian.org
pgpTUg90KUxD0.pgp
Description: PGP signature
nding feedback/ideas whatever, I can code something up to do this. I
> probably favor using python-apt (if it can actualy do it) or grep-dctrl to
> do the package lookup stuff, but can do it manually if this is a problem.
Dont code anything like that. I'd rather fix those hacky&#x
mpiling of .py[co] files
* add a new command "python-compile" to compile single python
files
* Added a separate section in python-register.1 for python programs;
also give an example.
-- Bastian Kleineidam <[EMAIL PROTECTED]> Fri, 13 Sep 2002 22:17:45 +0200
cu,
enable some more possibilities and
use-cases.
cu, Bastian
--
Bastian Kleineidam
reflexionsniveau AT web.de
calvin AT users.sf.net
calvin AT debian.org
pgpcTbxIp8fVL.pgp
Description: PGP signature
filing a bug against python-unit asking for
> its removal ?
It would be nice to still have the example files somewhere, eg included
in the python2.X-examples packages.
cu, Bastian
--
Bastian Kleineidam
reflexionsniveau AT web.de
calvin AT users.sf.net
calvin AT debian.org
depend on the
> required python versions.
If I understand you, python-numeric should have
Depends: python, python2.2-numeric
This wont work for python != 2.2.
Cheers, Bastian
--
Bastian Kleineidam
reflexionsniveau AT web.de
calvin AT users.sf.net
calvin AT debian.org
pgp3UTHPWT9m
t breaks. So I give in my packages exactly the Python versions
I can test and verify.
[*] I got bitten by the list.append(a,b) --> list.append((a,b)) change,
and the variable scope changes for local variables.
Cheers, Bastian
--
Bastian Kleineidam
reflexionsniveau AT web.de
hon files and does run with all recent Python versions.
You should depend on exactly the Python versions you support, not on
"python". For example
Depends: python1.5 | python2.1 | python2.2
And if you dont compile any Python packages, why do you still have to
build-dep
; change.
Mailman should put his modules in /usr/lib/python/site-packages.
Of course packagers can put their stuff in /usr/share//
or /usr/lib/ and use their own Python-version-compile
script, but then they are on their own.
cu,
--
Bastian Kleineidam
reflexionsniveau AT web.de
calvin AT users.sf.net
calvin AT debian.org
pgptPkq1aVP47.pgp
Description: PGP signature
al" package.
What I meant is to include the script into the Python
sources, not in the "python" binary package.
Currently, I have no valid GPG key in the Debian keyring,
so I cant upload anything.
Tschööö, Bastian
--
Bastian Kleineidam · [EMAIL PROTECTED] · GPG key ID 32EC6F3E
pgp86PQhM1Fr6.pgp
Description: PGP signature
On Fri, Aug 23, 2002 at 11:29:12PM -0500, Graham Wilson wrote:
> what is python-central?
See http://people.debian.org/~calvin/python-central/
doko wanted to include the script into the upcoming Python
releases, which I think is the best way to spread this.
Cheers,
--
Bastian Kleineidam · [EM
On Fri, Aug 23, 2002 at 03:26:00PM +0200, Jérôme Marant wrote:
> Any reason to keep 2.1 ?
It would make the transition somewhat easier for NMUs, as you
would only have to update the dependencies.
Tschööö, Bastian
--
Bastian Kleineidam · [EMAIL PROTECTED] · GPG key ID 32EC6F3E
pgp3TDIVlr
starter (just woke up) but what would the apt
> line look like?
deb http://ftp-master.debian.org/~doko/python ./
deb-src http://ftp-master.debian.org/~doko/python ./
Greetings,
--
.~.
/V\ Bastian Kleineidam · Kampfesser mit schwarzem Gürtel.
/( )\
^^-^^
pgpOgpkHpw6iM.pgp
Description: PGP signature
-central
* added sanity checking of debian package name
-- Bastian Kleineidam <[EMAIL PROTECTED]> Sat, 3 Aug 2002 13:11:25 +0200
Greetings,
--
.~.
/V\ Bastian Kleineidam · Python programming lizard.
/( )\
^^-^^
pgp2M188tRr5c.pgp
Description: PGP signature
Missing depends on libstdc++4:
Setting up python2.3 (2.2.90-1) ...
/usr/bin/python2.3: error while loading shared libraries:
libstdc++.so.4: cannot open shared object file: No such file or directory
Greetings,
--
.~.
/V\ Bastian Kleineidam · Debian Linux bug squasher
> files be compiled in the postinst script or can they be distributed with
> the package?
The tradeoff decision between postinst compilation (consumes CPU) and .pyc,
.pyo inclusion (consumes HD space) is up to you.
I prefer postinst compilation.
So long,
--
.~.
/V\ Bastian Kleinei
want this to happen or
> not.
> Roughly 5 people and a month or two's work should cover it.
I filed a feature request at SF.
http://sourceforge.net/tracker/index.php?func=detail&aid=574465&group_id=5470&atid=355470
Greetings,
--
.~.
/V\ Bastian K
Hi,
On Wed, Jun 26, 2002 at 10:09:43PM -0700, Sean 'Shaleh' Perry wrote:
> Do you think there would be opposition to using say docbook?
Lets find out.
http://sourceforge.net/tracker/index.php?func=detail&aid=574465&group_id=5470&atid=355470
Greetings,
--
.~.
/
On Sun, Jun 23, 2002 at 12:07:43PM +0200, Florent Rougon wrote:
> Bastian Kleineidam <[EMAIL PROTECTED]> wrote:
> Which python2.1 do you have? It is the same in woody and sid (2.1.3-3)
> and doesn't seem to contain such a file:
python2.1 (2.1.3-3) from sid
py2texi.el is a
Hi,
I was surprised to see emacs21 in the build depends of python2.1.
Seems that the only thing is the py2texi.el utility that requires
emacs.
As I dont know any Lisp, is there anyone out there to convert this
beast to Python or Perl? I dont like to install emacs to compile
python :)
Greetings
Hi,
On Fri, May 24, 2002 at 10:26:41AM +1000, Donovan Baarda wrote:
> For those that _really_ want to run foo with python2.2, they can run
> 'foo-python2.2' instead. I think using 'alternatives' is overkill for this
> reason, and the symlink is a good idea.
'python2.2 /usr/bin/foo' would work too
On Wed, May 22, 2002 at 01:09:02PM -, Moshe Zadka wrote:
> Situation:
> python2.1, python2.2, python2.2-foo and python-foo are all installed.
> python2.1 is the default.
> All dependancies are resolved, right?
>
> #!/usr/bin/python
> import foo
>
> equivalent to
>
> #!/usr/bin/python2.1
> i
Hi Moshe,
On Wed, May 22, 2002 at 12:09:11PM -, Moshe Zadka wrote:
> > a) python2.1-foo: python foo.py module for 2.1
Depends: python2.1
> > b) python2.2-foo: python foo.py module for 2.2
Depends: python2.2
> > c) python-foo: /usr/bin/foo binary with #!/usr/bin/python
> >Depends: python2
On Wed, May 22, 2002 at 11:01:14AM -, Moshe Zadka wrote:
> [please CC me, I'm not on the list]
NP.
> Hypothetical situation:
> Source package: contains foo.py (python module, works with every python
> version under the sun) and foo (a script whose first line is
> "import foo"). I want to prop
On Sun, Apr 28, 2002 at 04:30:49PM -0500, dman wrote:
>
> I did a google search and a search using the engine on debian.org but
> I can't find the Official Python Policy document anywhere. I did find
> Neil's draft version 0.1 proposal with no trouble, but I'm looking for
> the final (current) ve
Yeah,
finally got around to update this package. Thanks to Donovan Baarda
for his improvements!
Please test this one if you want to build Python packages or modules.
URL: http://people.debian.org/~calvin/python-central/
Package: python-central
Architecture: any
Description: register utility for
Hi Donovan,
On Sat, Feb 23, 2002 at 10:38:17AM +1100, Donovan Baarda wrote:
> Did you see my analysis and modified "register-python-package" script? I
> posted it under a misleading subject by mistake (responded to another thread
> that migrated onto it).
Sorry, sometimes I have lag in responding
Hi,
On Thu, Feb 21, 2002 at 12:17:45PM +1100, Donovan Baarda wrote:
> Adam has a very valid point that *.pyo and *.pyc files could be included
> inside the deb, instead of compiled and removed by the pre/postinst scripts.
I agree, this is allowed. If you want to have a TMDA package with .py[co]
On Mon, Feb 18, 2002 at 12:48:02PM -0500, Matt Zimmerman wrote:
> Good plan; why not do that for python? How about a
>
> /usr/sbin/python-pkgtool --install
> /usr/sbin/python-pkgtool --remove
Look at http://people.debian.org/~calvin/python-central/
Should we have a vote for the binary name? Cu
, not in
/usr/lib/python/
* display usage for wrong or missing options
* man page updated
-- Bastian Kleineidam <[EMAIL PROTECTED]> Thu, 14 Feb 2002 13:33:52 +0100
pgphArxZdh8qL.pgp
Description: PGP signature
Hello.
The first version of the python-central package is online at
http://people.debian.org/~calvin/python-central/
It provides support for installing pure Python modules independent
of the Python version (see Python Policy 2.2.3).
I made a patch for the python1.5 package which uses this script
On Sat, Feb 09, 2002 at 07:41:31PM +, Julian Gilbey wrote:
> I have a suggestion, which may already have been thought of.
For Python Policy 2.2.3, see
http://lists.debian.org/debian-python/2002/debian-python-200201/msg00019.html
I am working on this. I have the previous version online at
http:
Hello Pythoneers,
another version of the dh_purepython script is online at
http://people.debian.org/~calvin/purepython/.
It provides support for Section 2.2.3 of the Python Policy
which adresses version-independent Python modules.
I would be pleased to hear any comments and/or suggestions from y
On Thu, Jan 10, 2002 at 09:28:30PM +0300, Mikhail Sobolev wrote:
> On Thu, Jan 10, 2002 at 06:29:58PM +0100, Bastian Kleineidam wrote:
> > On Thu, Jan 10, 2002 at 05:25:43PM +, Luigi Ballabio wrote:
> > > on alpha debian, python 2.1.1-8:
> > >
> > Works
On Thu, Jan 10, 2002 at 05:25:43PM +, Luigi Ballabio wrote:
>
> Greetings,
> on alpha debian, python 2.1.1-8:
>
> >>> import math
> >>> math.exp(-720)
>
> aborts the interpreter with a floating point exception. The strange thing
> is, exp(-700) and exp(-750) both work.
Works for me,
Hi Python folks,
I have put together a dh_purepython debhelper script to help
the installation of pure Python packages.
Still missing:
1) All Python X.Y versions need to be preinstalled. What happens
when you install an new Python version? Hmm, we have to
register those pure python packag
Hi,
because my old GPG key expired and the new one looks to
take a while to get in the keyring I wanted to ask if
someone can sponsor an upload of a new linkchecker release.
You will find the new linkchecker 1.3.13 package at
http://people.debian.org/~calvin/debian/
The linkchecker*.changes file
Hi.
On Mon, Dec 17, 2001 at 08:14:46PM -0600, Joe Reinhardt wrote:
> What is the best way to use the setup.py in the debian/rules?
Added lines marked with "+++"
+++ PYTHON=python2.1
+++ PACKAGE=scipy
> configure: configure-stamp
> configure-stamp:
> dh_testdir
> # Add here commands t
Anthony Towns wrote:
Uh, yes, they are equivalent.
Ah, yes, given that the Python-Policy only allows one default
Python interpreter, not more than one.
Greetings, Bastian
Hi.
Harry Henry Gebel wrote:
'Depends: python (>= 2.1), python (<< 2.2)' as an error; so I used
'Depends: python (>= 2.1)' and 'Conflicts: python (>= 2.2)'
No, this is not equivalent! The Conflict means that I cannot install
happydoc and python2.2 simultaneously, and this is not desired.
I know t
Jérôme Marant wrote:
I said previously that the upgrade when OK. This is true, but I hadn't look
further at that moment.
My upgrade had some errors:
File "/usr/lib/python2.1/test/nocaret.py", line 2
[x for x in x] = x
SyntaxError: can't assign to list comprehension
SyntaxError: from __futu
Anthony Roach wrote:
So when there is a Debian package for Python 2.1, will I have to have a
python21-scons that depends on python << 2.2, python >= 2.1? I'm assuming I do,
because Python 2.1 will use /usr/lib/python2.1 rather than
/usr/lib/python2.0.
Exactly. With Python 2.1 you will have to make
Anthony,
Anthony Roach wrote:
1) Should I byte compile the scons script?
No. I assume its a shell script called /usr/bin/scons. There is no need
to byte-compile it.
2) Since the SCons.* modules work fine in all versions of Python supported by
all current versions of Debian, can I put them in som
>What might be a problem is where we put 3rd party modules.
In /usr/lib/pythonx.x/site-packages/
Bastian
Hi,
it seems there are some points to _not_ precompile Python files.
- packages get bigger (they get substantially bigger, more than twice
the size if they have lots of .py files)
- compatibility: I found the official wrapup
Third party extensions built for Python 1.5.x or 1.6
cannot be use
>I recently created a debian file for my project (see http://subterfugue.org),
>and discovered just now why including .pyc and .pyo files directly doesn't
>work optimally.
Where is the problem? Python bytecode should be platform
independent! So it is safe to include .pyc and .pyo files. There is no
u will run into problems sooner or later and you have to
update your software as the internal format changes. You can look
at the discussions about bdist_rpm and the RPM versions, thats
pretty much the same.
Bastian Kleineidam
58 matches
Mail list logo
