Jens Vagelpohl wrote:
On 18 Dec 2005, at 06:46, Alan Milligan wrote:
I'm reconsidering the way we RPM package byte-code compiled python, and
although I suspect optimised python is a bit of an anacronysm, I thought
I'd check with the list ;)
If one was to start Zope with python -O, then it
Summary of messages to the zope-tests list.
Period Sun Dec 18 12:01:01 2005 UTC to Mon Dec 19 12:01:01 2005 UTC.
There were no messages.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or
On Mon, Dec 19, 2005 at 06:50:19AM -0500, Jim Fulton wrote:
| There is a drawback: Debugging becomes a lot harder and sometimes
| impossible because you get no or faulty line number information in
| tracebacks and when using pdb.
|
| That isn't true. Line numbers are included and valid.
|
|
Sidnei da Silva wrote:
On Mon, Dec 19, 2005 at 06:50:19AM -0500, Jim Fulton wrote:
| There is a drawback: Debugging becomes a lot harder and sometimes
| impossible because you get no or faulty line number information in
| tracebacks and when using pdb.
|
| That isn't true. Line numbers are
On Mon, Dec 19, 2005 at 07:12:44AM -0500, Jim Fulton wrote:
| Sidnei da Silva wrote:
| On Mon, Dec 19, 2005 at 06:50:19AM -0500, Jim Fulton wrote:
| | There is a drawback: Debugging becomes a lot harder and sometimes
| | impossible because you get no or faulty line number information in
| |
I get always connection closed unexpectedly when using svn update.
Andreas
pgpFnXKQRqPEQ.pgp
Description: PGP signature
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
On 19 Dec 2005, at 12:00, Sidnei da Silva wrote:
On Mon, Dec 19, 2005 at 06:50:19AM -0500, Jim Fulton wrote:
| There is a drawback: Debugging becomes a lot harder and sometimes
| impossible because you get no or faulty line number information in
| tracebacks and when using pdb.
|
| That isn't
The following usecase is not handled correctly by Zope:
When you call a PythonScript returning a Python unicode string then
the ZPublisher/HTTPResponse code will convert the unicode response string
using HTTPResponse.default_encoding to a Python string. The default encoding
is configurable
Another usecase where Zope does not play nicely:
You can create a ZPT with XHTML content where the content is
encoded as UTF-8 (which the corresponding encoding declaration within the
XML preamble). When you redefine the zpublisher_default_encoding Zope might
convert the UTF8 body of the ZPT to
The Zope2 unit tests have been failing for some time on
buildbot.zope.com. Looks like a Five-related problem:
http://buildbot.zope.org/Zope%20trunk%202.4%20Linux%20zc-buildbot/builds/109/test/0
--
Benji York
Senior Software Engineer
Zope Corporation
Jens Vagelpohl wrote:
On 19 Dec 2005, at 12:23, Andreas Jung wrote:
I get always connection closed unexpectedly when using svn update.
Andreas
That %$£@ BerkeleyDB backend was geborken again. svnadmin recover fixed
it.
Thanks!
Jim
--
Jim Fulton mailto:[EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benji York wrote:
The Zope2 unit tests have been failing for some time on
buildbot.zope.com. Looks like a Five-related problem:
http://buildbot.zope.org/Zope%20trunk%202.4%20Linux%20zc-buildbot/builds/109/test/0
The failing test is a functional
[Benji York]
The Zope2 unit tests have been failing for some time on
buildbot.zope.com. Looks like a Five-related problem:
http://buildbot.zope.org/Zope%20trunk%202.4%20Linux%20zc-buildbot/builds/109/test/0
[Tres Seaver]
The failing test is a functional test, not a unit test; I don't run
Jim Fulton wrote:
This is really just a matter of knowing how to write the test.
Generally, when you want to show a dict sample, the way to do it
is with:
from zope.testing/doctestunit import pprint
pprint(thisdict)
This formats the dictionary nicely and, most importantly,
sorts the
Tim Peters wrote:
I'm not sure what it is testing, either; CC'ing Phillip, whose
fingerprints are on it, according the 'svn blame', for clarification.
These tests have always failed, and Phillip doesn't know why.
Because they were failing, he changed them to run at level 2. That's
not
[resending this from the right address, the original posting got
swallowed by Mailman]
Tres Seaver wrote:
Benji York wrote:
The Zope2 unit tests have been failing for some time on
buildbot.zope.com. Looks like a Five-related problem:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp von Weitershausen wrote:
Tres Seaver wrote:
Benji York wrote:
The Zope2 unit tests have been failing for some time on
buildbot.zope.com. Looks like a Five-related problem:
[Tim]
I opened a Collector issue on this about a month ago (I always run
with `--all`, so these failures are old news to me):
http://www.zope.org/Collectors/Zope/1947
[Philipp]
Rereading that issue again, it's totally surprising to see that there's no
failure on
Windows, which makes
Tres Seaver wrote:
Well, if you look closer you find that it uses pprint.pformat which always
outputs
the same on all machines (because it provides output sorted by the
dictionary key).
I see that in the implementation; it isn't documented as part of
pprint's contract, however.
Yes
Tim Peters wrote:
I wouldn't know where to start (having tried to debug this problem in the
past).
Anyone got an idea?
For a start, disabuse yourself of the illusion that it acts
differently on Windows than on Linux ;-)
Yup, sorry, misread the issue. Speed kills... :)
Philipp
Philipp von Weitershausen wrote:
...
Actually, I put this particular test (functional.txt) on level=2 because
it would fail when run together with other Five tests. It passes fine
when run by itself. This test exists identically in Five 1.2 (based on
Zope 2.8) where it passes just fine when run
Jim Fulton wrote:
Obviously, some other test isn't cleaning up after itself.
Yes, that was obvious to me too. It was confusing that the same test would pass
on Five
1.2, though, and I couldn't find any obvious differences. As trial and error
usually
takes time, I left the issue to be resolved
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp von Weitershausen wrote:
Tres Seaver wrote:
Well, if you look closer you find that it uses pprint.pformat which always
outputs
the same on all machines (because it provides output sorted by the
dictionary key).
I see that in the
Tres Seaver wrote:
Well, if you look closer you find that it uses pprint.pformat which always
outputs
the same on all machines (because it provides output sorted by the
dictionary key).
I see that in the implementation; it isn't documented as part of
pprint's contract, however.
...
[Philipp]
Well, if you look closer you find that it uses pprint.pformat which
always outputs the
same on all machines (because it provides output sorted by the
dictionary key).
[Tres Seaver]
I see that in the implementation; it isn't documented as part of
pprint's contract, however.
Tim Peters wrote:
... a good lecture on pprint vs. dicts
Thanks, I'll be more careful about using pprint for dicts then.
Philipp
This message was sent using IMP, the Internet Messaging Program.
Tim Peters wrote:
...
[Philipp]
Well, if you look closer you find that it uses pprint.pformat which
always outputs the
same on all machines (because it provides output sorted by the
dictionary key).
[Tres Seaver]
I see that in the implementation; it isn't documented as part of
[Tim]
Looks like Jim's suggested
from zope.testing.doctestunit import pprint
inherits this insecurity.
[Jim]
No, it doesn't.
from zope.testing.doctestunit import pprint
pprint({z: 1, m: 2})
{'m': 2,
'z': 1}
Note both the sorting and the wrapping.
See below.
Cool! I
Tim Peters wrote:
...
Well, I understand why that works, but it's not part of pprint's
contract either.
What contract. :)
Aren't you always telling me to read the source?
Note that, in Python 2.4, you can now pass a width to pprint without creating
a separate pretty printer:
from pprint
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Tim Peters wrote:
...
Well, I understand why that works, but it's not part of pprint's
contract either.
What contract. :)
The documented behavior, e.g. from '$ pydoc pprint' or the online
equivalent,
On Mon, December 19, 2005 17:44, Andreas Jung wrote:
--On 9. Dezember 2005 10:11:42 -0500 Jim Fulton [EMAIL PROTECTED] wrote:
I forgot a very important need:
- Common approach to Unicode
We need to migrate Zope 2 to use a similar strategy. We need
volunteers to brainstorm how this can
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Tim Peters wrote:
...
Well, I understand why that works, but it's not part of pprint's
contract either.
What contract. :)
The documented behavior, e.g. from '$ pydoc pprint' or the online
equivalent,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Tim Peters wrote:
...
Well, I understand why that works, but it's not part of pprint's
contract either.
What contract. :)
The
...
[Tim]
Well, I understand why that works, but it's not part of pprint's
contract either.
[Jim]
What contract. :)
pprint's docs.
Aren't you always telling me to read the source?
Indeed, if you hadn't, you wouldn't have known that forcing width=1
forces dict sorting ;-) It's common as
Philipp von Weitershausen wrote:
Jim Fulton wrote:
Obviously, some other test isn't cleaning up after itself.
Yes, that was obvious to me too. It was confusing that the same test would
pass on Five
1.2, though, and I couldn't find any obvious differences. As trial and error
usually
On 12/19/05, Philipp von Weitershausen [EMAIL PROTECTED] wrote:
Now I see what you mean by contract. You're right, I guess it isn't
documented then, but
perhaps it should be.
That's never been part of the contract and, as Tres notes, it's
inconsistent. The implmentation will only sort when
Perhaps the backend should be switched from bdb to fsfs (native
subversion backend type) ? I know it does away with a lot of these,
issues.
- Rocky
Jim Fulton wrote:
Jens Vagelpohl wrote:
On 19 Dec 2005, at 12:23, Andreas Jung wrote:
I get always connection closed unexpectedly when
Rocky Burt wrote:
Perhaps the backend should be switched from bdb to fsfs (native
subversion backend type) ? I know it does away with a lot of these,
issues.
Yup, when someone has time to do it. AFAIK, it will involve
dumping the repository and reloading it. Past experience suggests that
On 19 Dec 2005, at 20:02, Jim Fulton wrote:
Rocky Burt wrote:
Perhaps the backend should be switched from bdb to fsfs (native
subversion backend type) ? I know it does away with a lot of these,
issues.
Yup, when someone has time to do it. AFAIK, it will involve
dumping the repository and
Jens Vagelpohl wrote:
On 19 Dec 2005, at 20:02, Jim Fulton wrote:
Rocky Burt wrote:
Perhaps the backend should be switched from bdb to fsfs (native
subversion backend type) ? I know it does away with a lot of these,
issues.
Yup, when someone has time to do it. AFAIK, it will involve
On 19 Dec 2005, at 21:27, Jim Fulton wrote:
IMHO the process is straightforward and easy (except for the time
it will take),
That fact alone adds complication, as that down time needs to be
scheduled.
OK, well, the only complication is setting a date really. Someone
decides and
On 19 Dec 2005, at 21:37, Jens Vagelpohl wrote:
BTW, thanks for volunteering for this! It will be great not to
fool with the Berkeley DB anymore. :)
Umh, more like force-volunteered now ;) Which is fine, but in
return I'd like someone else (maybe you?) to herd the cats and come
up with a
Jens Vagelpohl wrote:
On 19 Dec 2005, at 21:27, Jim Fulton wrote:
IMHO the process is straightforward and easy (except for the time
it will take),
That fact alone adds complication, as that down time needs to be
scheduled.
OK, well, the only complication is setting a date really.
Jens Vagelpohl wrote:
On 19 Dec 2005, at 21:37, Jens Vagelpohl wrote:
BTW, thanks for volunteering for this! It will be great not to
fool with the Berkeley DB anymore. :)
Umh, more like force-volunteered now ;) Which is fine, but in return
I'd like someone else (maybe you?) to herd the
On 19 Dec 2005, at 21:44, Jim Fulton wrote:
Umh, more like force-volunteered now ;) Which is fine, but in
return I'd like someone else (maybe you?) to herd the cats and
come up with a time frame where this can be done, and
communicating it. I'll do everything on the technical side.
Hi guys,
I am running on Zope 2.7.6 with Plone 2.0.5. I am currently building a
dynamic application using MySQL as the backend database. I'd like to be
able to change a ZPT's state based on a parameter passed by the db.
For example, I have a ZPT that displays information for a particular
[Jim]
...
The whole repository is only about 800 megs. There are over 8 gigs
free. Are the dump file or the file-based repo much larger in
size the the Berkeley database?
FYI, if you don't want to read the code ;-), the book says an FSFS
repository is slightly smaller than the same thing
Jens Vagelpohl wrote:
On 19 Dec 2005, at 21:44, Jim Fulton wrote:
Umh, more like force-volunteered now ;) Which is fine, but in
return I'd like someone else (maybe you?) to herd the cats and
come up with a time frame where this can be done, and
communicating it. I'll do everything on
On 19 Dec 2005, at 22:08, Tim Peters wrote:
[Jim]
...
The whole repository is only about 800 megs. There are over 8 gigs
free. Are the dump file or the file-based repo much larger in
size the the Berkeley database?
FYI, if you don't want to read the code ;-), the book says an FSFS
Jens Vagelpihl has graciously offered to convert the subversion
repository to use a file-system back end.
The repsository will be inaccessable for some portion of
December 25.
Jim
--
Jim Fulton mailto:[EMAIL PROTECTED] Python Powered!
CTO (540) 361-1714
Jim Fulton wrote:
Jens Vagelpihl has graciously offered to convert the subversion
repository to use a file-system back end.
Jim groans, That's Jens Vagelpohl.
Thanks again Jens!
Jim
--
Jim Fulton mailto:[EMAIL PROTECTED] Python Powered!
CTO (540) 361-1714
Jim Fulton wrote:
Jens Vagelpihl has graciously offered to convert the subversion
repository to use a file-system back end.
Yay! I'll reserve further adulation until it comes back up intact. :)
--
Benji York
Senior Software Engineer
Zope Corporation
On 19 Dec 2005, at 22:38, Sebastien Douche wrote:
On 12/19/05, Jens Vagelpohl [EMAIL PROTECTED] wrote:
That %$£@ BerkeleyDB backend was geborken again. svnadmin recover
fixed it.
Hi Jens!
Does Zope server use svn server ? I had many problems with it (with
the need to recover it each time).
Mike,
this is not a task for zpt but for a python script.
I would suggest you write a script that gets all courses with a given
db-state and check them to be in the corresponding workflow state.
If not change the workflow state.
this script you call regularly (daily, hourly, when ever the db
Chris McDonough identified a persistence problem with the routine(s) that
manage sessions variables. (Thanks Chris) I have put the correction in
place which resolved some (but not all) of the problems.
There are still problems which are apparently due conflicts in accessing
the session
The interaction between sessions, conflicts, and persistence is a bit
confusing. I am still trying to understand the code in depth.
One thing is for sure, request.SESSION and/or request['SESSION'] must be
persistent for things to work. Mutable objects in the session variable
set
The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2337
Blamelist: andreasjung,chrisw,jim,poster
BUILD FAILED: failed test
sincerely,
-The Buildbot
The Buildbot has detected a failed build of Zope branches 2.9 2.4 Linux
zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2338
Blamelist: andreasjung,chrisw,jim,poster
BUILD FAILED: failed test
sincerely,
-The Buildbot
The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2339
Blamelist: andreasjung
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
The Buildbot has detected a failed build of Zope branches 2.9 2.4 Linux
zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 2340
Blamelist: andreasjung
BUILD FAILED: failed test
sincerely,
-The Buildbot
Hi,
for next release we plan to replace several parts with the corresponding
components from Zope 3 (e.g. ZPT´). Philipp is working on a proposal on
that issue. In addition I would like to get rid of some old stuff that is
no longer maintained and buggy:
- ZopeTutorial (could be ripped off
+1 on the lot if you are looking for votes.
On Tue, 20 Dec 2005, Andreas Jung wrote:
Hi,
for next release we plan to replace several parts with the corresponding
components from Zope 3 (e.g. ZPT´). Philipp is working on a proposal on
that issue. In addition I would like to get rid of
62 matches
Mail list logo
