On Fri, Nov 20, 2009 at 5:49 AM, Chris Withers ch...@simplistix.co.uk wrote:
Hi Jim,
It would be great if the two recent fixes I committed could make it into a
3.9.4 release some time soon...
What can I do to help this happen?
Assuming I do anything necessary, when could you do this
Jim Fulton wrote:
I need to review the changes before the release. I'll probably reject the
repozo change without an automated test.
Are you serious? You'd rather have a broken tool than one that isn't
broken on the basis that the existing tests aren't part of the test
suite that gets run by
On Fri, Nov 20, 2009 at 9:39 AM, Chris Withers ch...@simplistix.co.uk wrote:
Jim Fulton wrote:
I need to review the changes before the release. I'll probably reject the
repozo change without an automated test.
Are you serious? You'd rather have a broken tool than one that isn't broken
on
[Jim Fulton]
I need to review the changes before the release. I'll probably reject the
repozo change without an automated test.
[Chris Withers]\
Are you serious? You'd rather have a broken tool than one that isn't
broken on the basis that the existing tests aren't part of the test
suite that
Tim Peters wrote:
That's what he said -- and you made him repeat it several times by now.
Yes, I find it hard to believe that someone would deliberately break
something that someone else has taken the trouble to fix (and run the
tests for!)...
I've learned my lesson, I won't try and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
On Fri, Nov 20, 2009 at 5:49 AM, Chris Withers ch...@simplistix.co.uk wrote:
Hi Jim,
It would be great if the two recent fixes I committed could make it into a
3.9.4 release some time soon...
What can I do to help this happen?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
Jim Fulton wrote:
On Fri, Nov 20, 2009 at 5:49 AM, Chris Withers ch...@simplistix.co.uk
wrote:
Hi Jim,
It would be great if the two recent fixes I committed could make it into a
3.9.4 release some time soon...
What can I
On Fri, Nov 20, 2009 at 11:49 AM, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
Jim Fulton wrote:
On Fri, Nov 20, 2009 at 5:49 AM, Chris Withers ch...@simplistix.co.uk
wrote:
Hi Jim,
It would be great if the two recent fixes I
Jim Fulton wrote:
+class RepozoTests(unittest.TestCase):
+
+def test_importability(self):
+from ZODB.scripts import repozo
+
I appreciate your dedication to quality.
That test passes under ZODB 3.9.3 with Python 2.6.
...but it will emit a deprecation warning, which I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
On Fri, Nov 20, 2009 at 11:49 AM, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
Jim Fulton wrote:
On Fri, Nov 20, 2009 at 5:49 AM, Chris Withers
On Fri, Nov 20, 2009 at 1:36 PM, Tres Seaver tsea...@palladion.com wrote:
...
with Zope
2.12 and later now running on Python 2.6, we should just tell people
Sorry, you can't do backups?
No, we should tell them they should use a mostly untested tool to do backups
that doesn't work with
On Nov 20, 2009, at 11:52 AM, Jim Fulton wrote:
If configured, sure.
I would not trust repozo + blob backups.
I don't trust Blobs. A year ago, I reverted all of the code I had for our CMS
that supported Blobs as it was impossible to copy their data in a basic Zope 3
copy/past/move. I think
On 11/20/2009 08:07 PM, Jeff Shell wrote:
On Nov 20, 2009, at 11:52 AM, Jim Fulton wrote:
If configured, sure.
I would not trust repozo + blob backups.
I don't trust Blobs. A year ago, I reverted all of the code I had for our CMS
that supported Blobs as it was impossible to copy their data
13 matches
Mail list logo
