Benji York wrote:
2000--Zope---branches---2.9--2.4\build\lib\python\OFS\tests\test_XMLExportImport.py",
I suspect the following pattern needs to be changed:
ostream = tempfile.NamedTemporaryFile(suffix='.xml')
try:
data = exportXML(connection, oid, ostream)
On 4/30/06, Lennart Regebro <[EMAIL PROTECTED]> wrote:
Also, the ZServer test seems to leave cruft behind. Possibly a thread,
that the gets detected by the zope.server tests, because it will
complain that a thread is left behind by those test, while if I skip
the ZServer tests with -t '!ZServer'
Chris Withers wrote:
I suspect the following pattern needs to be changed:
ostream = tempfile.NamedTemporaryFile(suffix='.xml')
try:
data = exportXML(connection, oid, ostream)
ostream.flush()
sub._importObjectFromFile(ostream.name, 0, 0)
Benji York wrote:
Yep, that looks like it. Either I'll make my first commit to Zope 2
ever :) or if you want to, you can change it to something like this:
import tempfile
import os
fname = 'import_export.xml'
tempdir = tempfile.mkdtemp()
try:
ostream = open(fname, 'wb')
try:
d
Hi All,
Any idea what's causing the svn failrues on the buildbot.
This only seems to be affecting the Windows builds, with the Zope 2 & 3
trunk not currently building...
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_
Hi there,
i18n doesn't actually work for things marked as 'structure' in a page
template in both Zope 2 and Zope 3. Zope 2 does do this with
PlacelessTranslationService (through some tortuous route I won't go
into). I think in practice large systems such as Plone, Silva and CPS
are all transl
Philipp von Weitershausen wrote:
The feature freeze date for the June release is only days away. It was
planned to be May 1st, but due to lots of pending branches, we might let
it slip for a *couple* of days (not more!).
I've compiled a rough list of outstanding tasks for Zope 2.10:
http://www.z
--On 1. Mai 2006 18:46:07 +0200 Martijn Faassen <[EMAIL PROTECTED]> wrote:
Philipp von Weitershausen wrote:
The feature freeze date for the June release is only days away. It was
planned to be May 1st, but due to lots of pending branches, we might let
it slip for a *couple* of days (not more!
On 4/29/06, Florent Guillaume <[EMAIL PROTECTED]> wrote:
> It is up to the release managers (Stephan, Andreas) and the Pope to
> decide the exact feature freeze date, but I would suggest that we start
> merging those branches real soon.
Some crucial branches, namely the 3.3 integration is sched
Martijn Faassen wrote:
Philipp von Weitershausen wrote:
The feature freeze date for the June release is only days away. It was
planned to be May 1st, but due to lots of pending branches, we might let
it slip for a *couple* of days (not more!).
I've compiled a rough list of outstanding tasks fo
10 matches
Mail list logo
