On Apr 26, 2005, at 2:22, Florent Guillaume wrote:
Tim Peters [EMAIL PROTECTED] wrote:
Technical details of permanent failure:
PERM_FAILURE: SMTP Error (state 9): 553 5.3.0 Spam blocked see:
http://spamcop.net/bl.shtml?64.233.184.203
Yeah this goes to show that you have to be extremely careful in
Great. And the current situation doesn't even catch too much spam. We're
relying on some central spam filtering infrastructure here. Looks like I
got to tune it again...
Am Montag, den 25.04.2005, 17:46 -0400 schrieb Tim Peters:
You should really be using SpamBayes 0.9 wink.
--
gocept gmbh
Howdy,
Am Montag, den 25.04.2005, 16:37 -0400 schrieb Tim Peters:
AFAIK, nobody looks at WinBuilders between releases. It's
traditionally been the job of whoever builds the Windows installer to
sort out whatever troubles WinBuilders has gotten into since the last
release. Certainly most
...
[Tim Peters]
What exactly do you do to run tests? This is exactly what I do:
svn up
python setup.py build_ext -i
python test.py -vv --all
[Christian Theune]
I go to the build directory of the WinBuilders and run bin/test.py
1. Is there a reason to _expect_ that to work? The
On 2005-04-25 06:58:17 -0400, John Snowdon
[EMAIL PROTECTED] said:
Has anyone any thoughts about how to go about shibboleth enabling a
whole host of ZEO instances... without each one having an Apache server
sitting in front of it? Or is there an alternative method out there that
perhaps is not
Howdy,
Am Dienstag, den 26.04.2005, 11:38 -0400 schrieb Tim Peters:
[Christian Theune]
I go to the build directory of the WinBuilders and run bin/test.py
1. Is there a reason to _expect_ that to work? The WinBuilders
README.txt doesn't claim that it should. Would sure be nice
if
Sticking to this thread ...
Now the unit tests look like this:
==
ERROR: testCorrectFactories
(zope.app.publisher.browser.tests.test_directoryreso
urce.Test)
--
Sticking to this thread ...
Now the unit tests look like this:
The Zope trunk test_http_factory and test_webdav_source_factory tests
have been failing on Windows this way since last October (even when
running tests from a checkout tree). See:
http://www.zope.org/Collectors/Zope/1728
[Tim]
2. Which Python do you use to run bin\test.py? I hope you're using
bin\python.exe for that attempt anyway.
[Christian]
The one test.py refers to. (Yep, still tapping around blindly.)
I'm not following. #! lines don't mean anything on Windows, and
that's the only sense in which I
Christian Theune wrote:
Sticking to this thread ...
[...]
--
Ran 5634 tests in 1433.151s
FAILED (failures=3, errors=2)
Any comments? Still hesitating to release the binaries, but I have them
around.
I changed setup.py to add the
Tim Peters wrote:
Someone with setup.py courage needs to step up to the plate then. The
Windows build process is way hard enough to follow already without
adding reams of arbitrary new makefile cruft to paper over setup.py
bugs. Perhaps someone on Linux could volunteer to run Zope trunk
tests
[Tim Peters]
Someone with setup.py courage needs to step up to the plate then. The
Windows build process is way hard enough to follow already without
adding reams of arbitrary new makefile cruft to paper over setup.py
bugs. Perhaps someone on Linux could volunteer to run Zope trunk
tests
Hi!
Tim Peters wrote:
[yuppie]
I did that more than once,
Did what more than once?
Updating setup.py. (Or reminding people to do it themselves if they add
new files and forget to update setup.py.)
but why can't people clean up after themselves?
Which people, cleaning up what? Sorry, I'm not
Tim Peters wrote:
[Tim Peters]
...
I think this gets worse with Zope3 code, and especially when mixed in
with Zope2. Zope3 still uses setup.py for testing from a checkout,
but uses zpkgtools for building a distribution: those two subsystems
have nothing in common, and get out of synch with each
Hi,
Am Dienstag, den 26.04.2005, 12:57 -0400 schrieb Tim Peters:
[Tim]
2. Which Python do you use to run bin\test.py? I hope you're using
bin\python.exe for that attempt anyway.
[Christian]
The one test.py refers to. (Yep, still tapping around blindly.)
I'm not following. #!
[Tim]
2. Which Python do you use to run bin\test.py? I hope you're using
bin\python.exe for that attempt anyway.
[Christian]
The one test.py refers to. (Yep, still tapping around blindly.)
[Tim]
I'm not following. #! lines don't mean anything on Windows, and
[Christian]
I think cygwin
[Tim]
Someone with setup.py courage needs to step up to the plate then. The
[...] possibly work either so long as setup.py neglects to install necessary
files.
[Christian]
Yuppie did
[Tim]
That's not my understanding. My understanding (confirmed by
eyeballing the checkins) is that Yuppie
--On Dienstag, 26. April 2005 23:55 Uhr +0200 Christian Theune
[EMAIL PROTECTED] wrote:
Andreas: Can you please consider a beta2 instead of a rc as the next
step? Thanks.
You mean 2.8 b2? The next scheduled 2.8 release is b2 according to the
posted release
plan *wink*.
-aj
pgpbxpUn0lQjr.pgp
18 matches
Mail list logo
