- 06 Dec, 2005 6 commits
-
-
Andreas Jung authored
-
Philipp von Weitershausen authored
The reason for that is because zpkg and distutils can't deal with arbitrary data files that don't belong to a certain package.
-
Philipp von Weitershausen authored
-
Philipp von Weitershausen authored
-
Philipp von Weitershausen authored
-
Andreas Jung authored
-
- 05 Dec, 2005 5 commits
-
-
Jim Fulton authored
-
Florent Guillaume authored
exits.
-
Andreas Jung authored
-
Florent Guillaume authored
brings it in line with BTreeFolder.
-
- 02 Dec, 2005 12 commits
-
-
Tres Seaver authored
-
Chris Withers authored
-
Chris Withers authored
-
Chris Withers authored
- change SimpleItem.py to use python logging module - log at error when standard_error_message can't be rendered - give more useful info about errors rendering standard_error_message to the browser. - all conflict errors are counted and logged at info - logging makes it clear where the conflict has been resolved and where it hasn't - errors seen by the user are rendered with standard_error_message and are sent to the error_log which will likely copy them to the event log, depending on the users setup. - also checking in a functional test for generating write conflict errors. (I'll be committing to CHANGES.TXT shortly, I just wanted to keep the merges simpler)
-
Chris Withers authored
- remove unused import. - change SimpleItem.py to use python logging module - log at error when standard_error_message can't be rendered - give more useful info about errors rendering standard_error_message to the browser. - all conflict errors are counted and logged at info - logging makes it clear where the conflict has been resolved and where it hasn't - errors seen by the user are rendered with standard_error_message and are sent to the error_log which will likely copy them to the event log, depending on the users setup. - also checking in a functional test for generating write conflict errors. (I'll be committing to CHANGES.TXT shortly, I just wanted to keep the merges simpler)
-
Chris Withers authored
- all conflict errors are counted and logged at info, as they were before Florent's change - logging makes it clear where the conflict has been resolved and where it hasn't - errors seen by the user are rendered with standard_error_message and are sent to the error_log which will likely copy them to the event log, depending on the users setup. - also checking in a functional test for generating write conflict errors. (I'll be committing to CHANGES.TXT shortly, I just wanted to keep the merges simpler)
-
Andreas Jung authored
-
Chris Withers authored
- log at error when standard_error_message can't be rendered - give more useful info about errors rendering standard_error_message to the browser.
-
Andreas Jung authored
-
Andreas Jung authored
-
Chris Withers authored
-
Andreas Jung authored
-
- 01 Dec, 2005 8 commits
-
-
Tres Seaver authored
-
Tres Seaver authored
-
Tres Seaver authored
We now check ownership and proxy roles if an executable object is on the stack. Note that we have removed the C implementation of 'checkPermission'.
-
Florent Guillaume authored
Improved logging of ConflictErrors. Now a log is made at level BLATHER with traceback for any conflict retried. In addition, a log is made at level ERROR for a conflict that can't be retried anymore and is returned to the browser as an error. Nothing is logged anymore at level INFO.
-
Florent Guillaume authored
with traceback for any conflict retried. In addition, a log is made at level ERROR for a conflict that can't be retried anymore and is returned to the browser as an error. Nothing is logged anymore at level INFO.
-
Tres Seaver authored
-
Tres Seaver authored
-
Tres Seaver authored
-
- 30 Nov, 2005 9 commits
-
-
Florent Guillaume authored
-
Florent Guillaume authored
-
Florent Guillaume authored
-
Martijn Pieters authored
of a re-index.
-
Martijn Pieters authored
of a re-index.
-
Martijn Pieters authored
indexes do; this way one can simply re-catalog a site upgraded from a Zope 2.7 instance.
-
Tres Seaver authored
o The new tests are amphibious: they exercise both the Python and the C implementations, ensuring that they remain in sync.
-
Tres Seaver authored
o The new tests are amphibious: they exercise both the Python and the C implementations, ensuring that they remain in sync.
-
Tres Seaver authored
o The new tests are amphibious: they exercise both the Python and the C implementations, ensuring that they remain in sync.
-