[Python-modules-team] Bug#767554: Bug#769853: /769854: unblock: python-persistent and python-zodb
Hi,
Julien Cristau writes:
> On Fri, Dec 12, 2014 at 12:44:08 +0900, Arnaud Fontaine wrote:
>
>> I have attached the debdiff with the packages currently in unstable,
>> would you consider unblocking these changes if I upload the packages to
>> unstable?
>>
> Yes, I would.
Thanks! I have just uploaded both packages to unstable. Compared to my
previous debdiff, I have just merged the work done by Gediminas for the
next version of ZODB (basically only patch filenames are different and
the changelog entry has been modified accordingly), but the content of
python-zodb binary package is exactly the same.
I have attached debdiffs for both packages in case of.
Adam D. Barratt writes:
> Control: tags 769854 + confirmed moreinfo
> Control: tags 769853 + confirmed moreinfo
>
> If the upload can be made soon, that should be fine. Please remove the
> "moreinfo" tags once the packages are in unstable.
Done.
Cheers,
--
Arnaud Fontaine
diff -Nru python-persistent-4.0.8/debian/changelog python-persistent-4.0.8/debian/changelog
--- python-persistent-4.0.8/debian/changelog 2014-11-14 18:30:25.0 +0900
+++ python-persistent-4.0.8/debian/changelog 2014-12-10 17:41:09.0 +0900
@@ -1,3 +1,13 @@
+python-persistent (4.0.8-3) unstable; urgency=medium
+
+ * Team upload.
+ * Revert change in previous upload in favor of removing persistent
+module from python-zodb and make it depend upon this package (with
+upstream ACK). Closes: #767554.
++ d/control: Add Breaks/Replaces against python-zodb << 1:3.9.7-4~.
+
+ -- Arnaud Fontaine Wed, 10 Dec 2014 17:33:13 +0900
+
python-persistent (4.0.8-2) unstable; urgency=medium
* Team upload.
diff -Nru python-persistent-4.0.8/debian/control python-persistent-4.0.8/debian/control
--- python-persistent-4.0.8/debian/control 2014-11-14 18:31:01.0 +0900
+++ python-persistent-4.0.8/debian/control 2014-12-10 17:37:40.0 +0900
@@ -22,7 +22,8 @@
Package: python-persistent
Architecture: any
Depends: ${misc:Depends}, ${python:Depends}, ${shlibs:Depends}
-Conflicts: python-zodb (<< 3.11.0~)
+Breaks: python-zodb (<< 1:3.9.7-4~)
+Replaces: python-zodb (<< 1:3.9.7-4~)
Description: Automatic persistence for Python objects
This package contains a generic persistence implementation for Python. It
forms the core protocol for making objects interact "transparently" with
diff -Nru zodb-3.9.7/debian/changelog zodb-3.9.7/debian/changelog
--- zodb-3.9.7/debian/changelog 2014-11-17 12:10:50.0 +0900
+++ zodb-3.9.7/debian/changelog 2014-12-16 17:16:27.0 +0900
@@ -1,3 +1,29 @@
+zodb (1:3.9.7-4) unstable; urgency=medium
+
+ * Team upload.
+ * Revert change in previous upload in favor of removing persistent
+module from this package and make it depend upon python-persistent
+(with upstream ACK). Closes: #767554.
++ d/control: Add Depends against python-persistent.
++ d/rules: Delete persistent module from final package.
++ d/p/persistent-module-4.x-compat.patch: persistent 4.x uses bytes
+ instead of repr() but ZODB < 4.0.0a4 still uses repr() which is
+ incompatible.
++ d/tests/all: Remove persistent from the list of tests being ran.
++ d/tests/control: zope.testing.doctest has been removed in
+ python-zope.testing 4.0.0 and tests cannot be ran anymore. So update
+ Depends accordingly even though << 4.0.0~ is only in stable instead of
+ backporting many patches. Fix this issue properly when packing NUR
+ after the release of Jessie.
+ * d/p/test-spurious-failure-under-python27.patch: Fix python2.7 tests.
+
+ [ Gediminas Paulauskas ]
+ * d/p/new-transaction.patch: Fix test failure with new transaction.
+ * d/p/testUtils.patch: Fix test failure with python2.7 (>= 2.7.6).
+ * d/tests: Switch to zope.testrunner.
+
+ -- Arnaud Fontaine Tue, 16 Dec 2014 17:12:06 +0900
+
zodb (1:3.9.7-3) unstable; urgency=medium
* Team upload.
@@ -237,4 +263,3 @@
* Initial release (Closes: #158552, #159072, #188435)
-- Fabio Tranchitella Thu, 18 Aug 2005 21:49:17 +
-
diff -Nru zodb-3.9.7/debian/control zodb-3.9.7/debian/control
--- zodb-3.9.7/debian/control 2014-11-17 12:09:52.0 +0900
+++ zodb-3.9.7/debian/control 2014-12-16 16:40:16.0 +0900
@@ -19,13 +19,12 @@
Depends: ${pydeb:Depends},
${python:Depends},
${misc:Depends},
- ${shlibs:Depends}
+ ${shlibs:Depends},
+ python-persistent
Provides: ${pydeb:Provides},
${python:Provides},
- python-persistent
Suggests: ${pydeb:Suggests}
-Conflicts: zope3,
- python-persistent
+Conflicts: zope3
Description: Zope Object Database (ZODB)
The Zope Object Database is an object-oriented database for Python that
provides a high-degree of transparency. Applications can take advantage of
diff -Nru zodb-3.9.7/debian/patches
[Python-modules-team] Bug#767554: Bug#769853/769854: unblock: python-persistent and python-zodb
Hi,
Julien Cristau writes:
> I don't think that's ok. Can't you remove the conflicting files from
> python-zodb, and make it depend on python-persistent?
Thanks for the suggestion. I talked with upstream authors and this
should be fine. However, python-persistent in the archive (4.x) is
incompatible with ZODB < 4.0.0a4 and thus with the version available in
the archive (3.9.7). Therefore, I had to backport some patches from
upstream so that python-zodb could depend on python-persistent.
With these patches, all the unit tests of python-zodb pass when being
ran with python-persistent and python-zodb installed (even though, they
only ran with python-zope.testing from stable, due to change in the unit
tests framework only from zope.testing 4.x).
Here are the changelog entries for both packages:
python-persistent (4.0.8-3) unstable; urgency=medium
* Team upload.
* Revert change in previous upload in favor of removing persistent
module from python-zodb and make it depend upon this package (with
upstream ACK). Closes: #767554.
+ d/control: Add Breaks/Replaces against python-zodb << 1:3.9.7-4~.
-- Arnaud Fontaine Wed, 10 Dec 2014 17:33:13 +0900
zodb (1:3.9.7-4) unstable; urgency=medium
* Team upload.
* Revert change in previous upload in favor of removing persistent
module from this package and make it depend upon python-persistent
(with upstream ACK). Closes: #767554.
+ d/control: Add Depends against python-persistent.
+ d/rules: Delete persistent module from final package.
+ d/p/fix_persistent_module_4.x_incompatibilities.patch: persistent 4.x
uses bytes instead of repr() but ZODB < 4.0.0a4 still uses repr() which
is incompatible.
+ d/tests/all: Remove persistent from the list of tests being ran.
+ d/tests/control: zope.testing.doctest has been removed in
python-zope.testing 4.0.0 and tests cannot be ran anymore. So update
Depends accordingly even though << 4.0.0~ is only in stable instead of
backporting many patches. Fix this issue properly when packing NUR
after the release of Jessie.
* d/p/debian/patches/fix_unit_tests.patch: Fix python2.7 tests failures.
-- Arnaud Fontaine Fri, 12 Dec 2014 11:47:47 +0900
I have attached the debdiff with the packages currently in unstable,
would you consider unblocking these changes if I upload the packages to
unstable?
Regards,
--
Arnaud Fontaine
diff -Nru python-persistent-4.0.8/debian/changelog python-persistent-4.0.8/debian/changelog
--- python-persistent-4.0.8/debian/changelog 2014-11-14 18:30:25.0 +0900
+++ python-persistent-4.0.8/debian/changelog 2014-12-10 17:41:09.0 +0900
@@ -1,3 +1,13 @@
+python-persistent (4.0.8-3) unstable; urgency=medium
+
+ * Team upload.
+ * Revert change in previous upload in favor of removing persistent
+module from python-zodb and make it depend upon this package (with
+upstream ACK). Closes: #767554.
++ d/control: Add Breaks/Replaces against python-zodb << 1:3.9.7-4~.
+
+ -- Arnaud Fontaine Wed, 10 Dec 2014 17:33:13 +0900
+
python-persistent (4.0.8-2) unstable; urgency=medium
* Team upload.
diff -Nru python-persistent-4.0.8/debian/control python-persistent-4.0.8/debian/control
--- python-persistent-4.0.8/debian/control 2014-11-14 18:31:01.0 +0900
+++ python-persistent-4.0.8/debian/control 2014-12-10 17:37:40.0 +0900
@@ -22,7 +22,8 @@
Package: python-persistent
Architecture: any
Depends: ${misc:Depends}, ${python:Depends}, ${shlibs:Depends}
-Conflicts: python-zodb (<< 3.11.0~)
+Breaks: python-zodb (<< 1:3.9.7-4~)
+Replaces: python-zodb (<< 1:3.9.7-4~)
Description: Automatic persistence for Python objects
This package contains a generic persistence implementation for Python. It
forms the core protocol for making objects interact "transparently" with
diff -Nru zodb-3.9.7/debian/changelog zodb-3.9.7/debian/changelog
--- zodb-3.9.7/debian/changelog 2014-11-17 12:10:50.0 +0900
+++ zodb-3.9.7/debian/changelog 2014-12-12 12:00:34.0 +0900
@@ -1,3 +1,24 @@
+zodb (1:3.9.7-4) unstable; urgency=medium
+
+ * Team upload.
+ * Revert change in previous upload in favor of removing persistent
+module from this package and make it depend upon python-persistent
+(with upstream ACK). Closes: #767554.
++ d/control: Add Depends against python-persistent.
++ d/rules: Delete persistent module from final package.
++ d/p/fix_persistent_module_4.x_incompatibilities.patch: persistent 4.x
+ uses bytes instead of repr() but ZODB < 4.0.0a4 still uses repr() which
+ is incompatible.
++ d/tests/all: Remove persistent from the list of tests being ran.
++ d/tests/control: zope.testing.doctest has been removed in
+ python-zope.testing 4.0.0 and tests cannot be ran anymore. So update
+
[Python-modules-team] Bug#767554: python-persistent and python-zodb: error when trying to install together
Hi, > Arnaud Fontaine wrote (26 Nov 2014 09:03:09 GMT) : >> Really sorry about that. FTR, I have not uploaded anything yet because >> the release team would prefer to avoid the Conflicts if possible and >> make python-zodb depends upon python-persistent instead. AFAIK, it does >> not seem to be an issue but I have just sent an email to upstream author >> to confirm it's not going to be an issue... > > Any answer from them? Yes, sorry about the lag. The upstream said there should be no problem for python-zodb to Depends on python-persistent (and thus remove persistent module from python-zodb). Barry: if that's ok, I will upload python-persistent with the Breaks/Replaces and upload python-zodb without persistent module? Cheers, -- Arnaud Fontaine signature.asc Description: PGP signature ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#767554: python-persistent and python-zodb: error when trying to install together
Hello, Andreas Beckmann writes: > Followup-For: Bug #767554 > Control: found -1 767554 4.0.8-2 > > The Conflicts does not work ... without the proper epoch ... you need > > Conflicts: python-zodb (<< 1:3.11.0~) > > > Selecting previously unselected package python-persistent. > Unpacking python-persistent (from .../python-persistent_4.0.8-2_amd64.deb) > ... > dpkg: error processing > /var/cache/apt/archives/python-persistent_4.0.8-2_amd64.deb (--unpack): >trying to overwrite '/usr/lib/python2.7/dist-packages/persistent/dict.py', > which is also in package python-zodb 1:3.9.7-2 > Errors were encountered while processing: >/var/cache/apt/archives/python-persistent_4.0.8-2_amd64.deb Really sorry about that. FTR, I have not uploaded anything yet because the release team would prefer to avoid the Conflicts if possible and make python-zodb depends upon python-persistent instead. AFAIK, it does not seem to be an issue but I have just sent an email to upstream author to confirm it's not going to be an issue... Cheers, -- Arnaud Fontaine signature.asc Description: PGP signature ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#767554: python-persistent and python-zodb: error when trying to install together
Hi, Gediminas Paulauskas writes: >> If that's ok with you, I'm going to upload both packages to fix this bug: >> >> * python-persistent: >> Conflicts: python-zodb (<< 3.11.0~) >> >> * python-zodb: >> Conflicts: python-persistent >> > > Since ZODB3 before the split included persistent, it should provide it: > > Provides: python-persistent > > One package that Build-Depends on python-persistent but should be > installable with only python-zodb is zope.component. Thank you very much for pointing this out. I will upload now with the Provides then. Cheers, -- Arnaud Fontaine signature.asc Description: PGP signature ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#767554: python-persistent and python-zodb: error when trying to install together
Barry Warsaw writes: > On Nov 12, 2014, at 05:50 PM, Arnaud Fontaine wrote: > >>From upstream point of view, ZODB3 (aka python-zodb in Debian) used to >>include persistent, BTrees, ZODB and ZEO modules. However, since ZODB3 >>3.11.0a1, upstream has split it up into 4 distinct packages (one for >>each module), bump the version to 4.0 and made ZODB3 a "metapackage" >>depending on all of them. > > It looks like Debian still has zodb 3.9.7, right? Unfortunately, yes. >>As of fixing this RC bug for Jessie: Among the four, only persistent >>package is currently available in Debian, so there is no way to get rid >>of ZODB3 (at least for Jessie). Barry: If persistent >= 4.0 Debian >>package is useful on its own to anyone (and thus should not be removed >>From testing), then can I add a Conflict on both packages and upload >>them to fix this bug? > > IIRC, I needed to update python-persistent for the Python 3 zope.component > transition, as it's a build-dep. There are no other reverse dependencies that > I know of. > > I think a Conflicts is the right way to handle this for now, given where we > are in the Jessie release cycle. Arnaud, thanks for handling this! If that's ok with you, I'm going to upload both packages to fix this bug: * python-persistent: Conflicts: python-zodb (<< 3.11.0~) * python-zodb: Conflicts: python-persistent Cheers, -- Arnaud Fontaine signature.asc Description: PGP signature ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#767554: python-persistent and python-zodb: error when trying to install together
Hello, Andreas Beckmann writes: > Package: python-persistent,python-zodb > Version: 4.0.8-1 > Severity: serious > User: trei...@debian.org > Usertags: edos-file-overwrite > Control: found -1 1:3.9.7-2 First of all, thanks for finding and reporting such issues, it's greatly appreciated! > Selecting previously unselected package python-zodb. > Preparing to unpack .../python-zodb_1%3a3.9.7-2_amd64.deb ... > Unpacking python-zodb (1:3.9.7-2) ... > dpkg: error processing archive > /var/cache/apt/archives/python-zodb_1%3a3.9.7-2_amd64.deb (--unpack): >trying to overwrite '/usr/lib/python2.7/dist-packages/persistent/wref.py', > which is also in package python-persistent 4.0.8-1 > Errors were encountered while processing: >/var/cache/apt/archives/python-zodb_1%3a3.9.7-2_amd64.deb > > This is a serious bug as it makes installation fail, and violates > sections 7.6.1 and 10.1 of the policy. An optimal solution would > consist in only one of the packages installing that file, and renaming > or removing the file in the other package. Depending on the > circumstances you might also consider Replace relations or file > diversions. If the conflicting situation cannot be resolved then, as a > last resort, the two packages have to declare a mutual > Conflict. Please take into account that Replaces, Conflicts and > diversions should only be used when packages provide different > implementations for the same functionality. > > Here is a list of files that are known to be shared by both packages > (according to the Contents file for sid/amd64, which may be > slightly out of sync): > > usr/lib/python2.7/dist-packages/persistent/__init__.py > [...] From upstream point of view, ZODB3 (aka python-zodb in Debian) used to include persistent, BTrees, ZODB and ZEO modules. However, since ZODB3 3.11.0a1, upstream has split it up into 4 distinct packages (one for each module), bump the version to 4.0 and made ZODB3 a "metapackage" depending on all of them. As of fixing this RC bug for Jessie: Among the four, only persistent package is currently available in Debian, so there is no way to get rid of ZODB3 (at least for Jessie). Barry: If persistent >= 4.0 Debian package is useful on its own to anyone (and thus should not be removed From testing), then can I add a Conflict on both packages and upload them to fix this bug? Cheers, -- Arnaud Fontaine signature.asc Description: PGP signature ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#752741: Should depend upon python-six >= 1.4.1
Hello, Could you please also add a versioned depends against python-prettytable (>= 0.7 && < 0.8)? Cheers, -- Arnaud Fontaine ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#752741: Should depend upon python-six >= 1.4.1
Package: python-cliff Version: 1.6.1-1 Severity: important Hello, Since 1.6.0, cliff requires six >= 1.4.1. Could you please explicitly add this to Depends? Thanks. Cheers, -- Arnaud Fontaine ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#739476: ImportError: cannot import name ScopedSession
Source: elixir Severity: grave Tags: upstream Hello, When trying to import elixir module, I get the following traceback which makes elixir completely unusable: import elixir Traceback (most recent call last): File "", line 1, in File "/usr/lib/pymodules/python2.7/elixir/__init__.py", line 29, in from elixir.entity import Entity, EntityBase, EntityMeta, EntityDescriptor, \ File "/usr/lib/pymodules/python2.7/elixir/entity.py", line 17, in from sqlalchemy.orm import MapperExtension, mapper, object_session, \ ImportError: cannot import name ScopedSession Also, considering that a security bug, #670919, which is almost two years old has never been fixed and there has been no upstream release since 11/2009 (actually around the time a declarative layer has been implemented in sqlalchemy AFAIU), I'm wondering whether this package should be kept in the archive at all. What do you think? -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Regards, -- Arnaud Fontaine ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#732148: genshi: Rebuild docs at build time
Hello, Barry Warsaw writes: > I see that you're shipping a -doc package, and it looks like > you're not rebuilding docs from a quick scan of rules. > > Please re-build docs at build-time, don't ship pre-built > output of sources. Could you please elaborate? Cheers, -- Arnaud Fontaine ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#689285: Not properly fixed
Hi, Enrico Zini writes: > I see no reason to release Wheezy with turbogears, at all. > > It is hardly supported upstream, it is obsolete, and it does not have > many users. > > Also, I have no motivation whatsoever to support it for Wheezy's > lifetime. > > My plan to solve this bug is therefore to file RM bugs for it and all > that depends on it, both for wheezy and for sid. > > The affected packages are: > >python-tgmochikit python-turbogears python-turbomail > > I'll do it in a week unless some of the other comaintainers step up > and say that they take responsibility for supporting TG during > Wheezy's lifetime. Please go ahead as I don't mind at all if you get rid of turbomail. Cheers, -- Arnaud Fontaine pgpx6mNQX7Jcv.pgp Description: PGP signature ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
Re: [Python-modules-team] Package Trac 0.12 as well
>>>>> Al Nikolov writes: Hi, Sorry for the late reply. >> nor do we have a suitable version of Genshi in Debian. Trac 0.12 >> seems to need Genshi trunk, while Debian has the latest official >> release 0.5.1. We have to wait until Genshi 0.6 is out. I fear, >> this won't happen before Squeeze freeze and the quality of the >> Trac 0.12 package would be qustionable without sufficient testing >> time. > According to http://genshi.edgewall.org/ticket/369 the Genshi > trunk considered to be quite stable for 0.6.0 release (but haven't > even tagged though). I'm not aware of genshi' maintainers plans to > package it (this is why i'm putting them to CC). Probably guys > need our help as well? According to this ticket, it states that it "can be used in production, __at least in the context of Trac__", but as it hasn't been released yet, it may still contain regressions or bugs[0]. Therefore, I am not sure it would be a good idea to upload genshi 0.6 to unstable just for Trac 0.12 (which has not been released either) because it would affect all users... Maybe I can upload it to experimental for now, so you can upload trac to experimental as well. In case genshi 0.6 has not been released before the freeze, then I could upload it to unstable anyway if there hasn't been any complain from users with the package in experimental. What do you think? Regards, Arnaud Fontaine [0] http://genshi.edgewall.org/query?status=assigned&status=new&status=reopened&group=status&milestone=0.6 ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#525563: python-markdown: Please package release 2.0
Hello, I maintain python-cheetah and currently packaging the last version (namely 2.2.2). However, this version depends on python-markdown >= 2.0.1, thus could you please package the last upstream release so I could upload python-cheetah 2.2.2? Thanks. Cheers, Arnaud Fontaine pgprpk8ed2DDx.pgp Description: PGP signature ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#547198: badly quoted js issue
>>>>> Stefano Zacchiroli writes: Hi, > Uhm, I'm not terribly at ease at applying the patch given that > there are various approaches to fix the issue and that upstream > has not yet voiced his opinion about which approach he > prefers. Some questions: > - did you try both the patches or just one? - I see from your > patch that you did not apply the part of the patch that concerns > tests, why so? Well, the upstream author has not answered at all to this bug. I have only tried the second version so far. If the upstream author does not do anything in the next weeks, would you consider applying this patch? (If somebody complains about a breakage in the module, I guess it won't be so complicated to fix it or remove it, isn't it?) I did not apply the tests part of the patch as I think it is not really useful but after thinking again about it, it was silly, feel free to include it as well ;). Cheers, Arnaud Fontaine pgpmUfDUDGwsM.pgp Description: PGP signature ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#547198: badly quoted js issue
Package: python-toscawidgets
Version: 0.9.7.2-1.1
Severity: normal
Tags: patch upstream
Forwarded: http://toscawidgets.org/trac/tw/ticket/30
Hello,
While trying to use AutoComplete from tw.jquery, I had the issue
reported there[0]. Applying this "patch" seems to fix the issue. I have
attached to this email a patch for the Debian package.
Regards,
Arnaud Fontaine
-- System Information:
Debian Release: squeeze/sid
APT prefers experimental
APT policy: (990, 'experimental'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.31-rc6
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages python-toscawidgets depends on:
ii python-formencode1.2.2-1 validation and form generation Pyt
ii python-simplejson2.0.9-1 Simple, fast, extensible JSON enco
ii python-support 1.0.3 automated rebuilding support for P
ii python-webob 0.9.6.1-1.1 Python module providing WSGI reque
python-toscawidgets recommends no packages.
Versions of packages python-toscawidgets suggests:
ii python-cheetah2.2.1-1text-based template engine and Pyt
ii python-genshi 0.5.1-1Python XML-based template engine
ii python-kid0.9.6-1simple Pythonic template language
-- no debconf information
diff -urN python-toscawidgets-0.9.7.2.orig/debian/patches/00list python-toscawidgets-0.9.7.2/debian/patches/00list
--- python-toscawidgets-0.9.7.2.orig/debian/patches/00list 2009-09-17 17:57:59.0 +0100
+++ python-toscawidgets-0.9.7.2/debian/patches/00list 2009-09-17 16:55:33.0 +0100
@@ -1 +1,2 @@
force-init_py
+fix-js-quote
diff -urN python-toscawidgets-0.9.7.2.orig/debian/patches/fix-js-quote python-toscawidgets-0.9.7.2/debian/patches/fix-js-quote
--- python-toscawidgets-0.9.7.2.orig/debian/patches/fix-js-quote 1970-01-01 01:00:00.0 +0100
+++ python-toscawidgets-0.9.7.2/debian/patches/fix-js-quote 2009-09-17 17:19:39.0 +0100
@@ -0,0 +1,173 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## force-init_py.dpatch by srlindermann:
+## http://toscawidgets.org/trac/tw/ticket/30
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: avoid removal of apparently useless __init__.py by pysupport
+
+...@dpatch@
+--- a/ToscaWidgets-0.9.7.2/tw/core/js.py 2009-04-27 19:31:51.0 +0100
b/ToscaWidgets-0.9.7.2/tw/core/js.py 2009-09-17 16:56:04.0 +0100
+@@ -1,7 +1,7 @@
+ """
+ Python-JS interface to dynamically create JS function calls from your widgets.
+
+-This moudle doesn't aim to serve as a Python-JS "translator". You should code
++This module doesn't aim to serve as a Python-JS "translator". You should code
+ your client-side code in JavaScript and make it available in static files which
+ you include as JSLinks or inline using JSSources. This module is only intended
+ as a "bridge" or interface between Python and JavaScript so JS function
+@@ -11,9 +11,10 @@
+
+ import logging
+ from itertools import imap
++import re
+ import simplejson.encoder
+
+-__all__ = ["js_callback", "js_function", "js_symbol", "encode"]
++__all__ = ["js_callback", "js_function", "js_symbol"]
+
+ log = logging.getLogger(__name__)
+
+@@ -31,40 +32,56 @@
+ >>> w = Widget("foo")
+ >>> args = {'onLoad': js_callback(js_function('jQuery')(w).click(js_symbol('onClick')))}
+ >>> print encode(args)
+-{"onLoad": function(){jQuery(\\"foo\\").click(onClick)}}
++{"onLoad": function(){jQuery("foo").click(onClick)}}
+ >>> print encode({'args':args})
+-{"args": {"onLoad": function(){jQuery(\\"foo\\").click(onClick)}}}
+-
+-
++{"args": {"onLoad": function(){jQuery("foo").click(onClick)}}}
+
++Technical note: simplejson does not support arbitrary js injection, which
++is needed in this module. We work around this by inserting distinct
++tokens into the JSON encoding stream that can later be replaced with the
++objects' js representations.
++
+ """
+ def __init__(self, *args, **kw):
+-self.pass_through = (_js_call, js_callback, js_symbol, js_function)
+ super(TWEncoder, self).__init__(*args, **kw)
+
+ def default(self, obj):
+-if isinstance(obj, self.pass_through):
++if hasattr(obj, 'get_js_repr'):
+ return self.mark_for_escape(obj)
+ elif hasattr(obj, '_id'):
+ return str(obj.id)
+ return super(TWEncoder, self).default(obj)
+
+ def encode(se
[Python-modules-team] Bug#547195: python-toscawidgets: please add tw.dynforms module
Package: python-toscawidgets Version: 0.9.7.2-1 Severity: wishlist Hello, Could you please add tw.dynforms to ToscaWidgets debian package as it greatly extends ToscaWidgets? Cheers, Arnaud Fontaine pgpKRwljjLLKj.pgp Description: PGP signature ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
Re: [Python-modules-team] python-twill should depend on python-setuptools ?
> "Bernd" == Bernd Zeimetz <[EMAIL PROTECTED]> writes: Hello, Yep, I know about this bug since two days but don't have time yet to fix it (because of my exams). I will upload it at the end of the week. Bernd> my favourite way to fix this problem is by replacing Bernd> setuptools with distutils. setuptools is a here Arnaud, if it's ok for you I'll change the package. I don't really see the point of using distutils instead of setuptools? ;) I was thinking about to add only python-setuptools in Depends. ++ Arnaud ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
