Your message dated Sun, 15 Jun 2008 22:19:12 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#484571: python-configobj: causes syntax error from
python 2.3 due to genexp
has caused the Debian Bug report #484571,
regarding python-configobj: causes syntax error from python 2.3 due to genexp
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
484571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484571
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: python-configobj
Version: 4.5.2-1
Severity: normal
When .py modules are compiled, I get an error from python 2.3 due to this
generator expression appearing in the python-configobj package:
Compiling /var/lib/python-support/python2.3/validate.py ...
File "/var/lib/python-support/python2.3/validate.py", line 627
fun_kwargs = dict((str(key), value) for (key, value) in
fun_kwargs.items())
^
SyntaxError: invalid syntax
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (700, 'testing'), (600, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.24.2 (SMP w/2 CPU cores)
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages python-configobj depends on:
ii python-support 0.7.7 automated rebuilding support for P
python-configobj recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, 2008-06-14 at 23:59 +1000, Andrew McNamara wrote:
> It looks like someone or something else has "fixed" the problem - the
> path /var/lib/python-support/python2.3 no longer even exists on my machine
> (and I didn't remove it).
>
> I'll skip the dpkg output for now, as it's quite long and it looks like
> this one has been fixed. Thanks for your effort.
Since I couldn't find a way to reproduce this with packages which are
currently available, I think it is sane to close the bug, then =).
Thanks for the help, and if you are able to reproduce it again let me
know!
See you,
--
Gustavo Noronha Silva <[EMAIL PROTECTED]>
Debian Project
signature.asc
Description: This is a digitally signed message part
--- End Message ---
