Re: [Zope-dev] zope-tests - FAILED: 5, OK: 8

2013-07-18 Thread Wichert Akkerman
On Jul 17, 2013, at 12:41 , Marius Gedminas mar...@gedmin.as wrote:
 
 I'm somewhat ashamed to admit that I don't know how to do that.
 
 Normally I get setuptools with sudo apt-get install python-setuptools,
 or by creating a virtualenv.

I have setuptools 0.9.1 deb packages if you need them. One additional thing I 
noticed that you most also take care to never pin setuptools to another version 
than your OS might have installed or buildout will break.

Wichert.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope-tests - FAILED: 14, OK: 7

2013-07-12 Thread Wichert Akkerman

On Jul 12, 2013, at 02:38, Tres Seaver tsea...@palladion.com wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 On 07/11/2013 01:05 PM, Wichert Akkerman wrote:
 
 FWIW I tried to upgrade a few projects to zc.buildout 2.2 today but
 had to revert to a buildout 1.x due to conflicts with an OS-provided 
 pkg-resources sourced from distribute that I could not uninstall.
 
 Patient: Doctor, when I drink iced tea I get a cold stabbing pain in my
 eye!
 
 Doctor:  Take out the spoon!
 
 (In other words, if the system python is hosing you, quit using it).
 
 If the system python provide command-line flags for suppressing
 site-paacakges, you might be able to use them to bootstrap.  Or build a
 virtualenv '--without-setuptools' and use that to boostrap.  Or just
 build your own Python and be done.

The recommendation to compile your own python comes up often, but from an 
operational point of view is not a realistic thing to do. I want to use a 
system Python since I want to get automatic (security) updates from my OS 
instead of having to deal with them manually.

virtualenv might work, but then again using buildout 1.7 which essentially has 
virtualenv built in still seems like a simpler solution.

Wichert.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope-tests - FAILED: 14, OK: 7

2013-07-11 Thread Wichert Akkerman

On Jul 11, 2013, at 16:44 , Tres Seaver tsea...@palladion.com wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 On 07/11/2013 03:55 AM, Patrick Gerken wrote:
 now I have to create a virtualenv with --distribute, then I have to
 upgrade setuptools
 
 We should be upgrading all our projects to zc.buildout 2.2, which drops
 'distribute'.

FWIW I tried to upgrade a few projects to zc.buildout 2.2 today but had to 
revert to a buildout 1.x due to conflicts with an OS-provided pkg-resources 
sourced from distribute that I could not uninstall.

Wichert.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope-tests - FAILED: 86, OK: 5

2013-06-03 Thread Wichert Akkerman

On Jun 3, 2013, at 14:37 , Tres Seaver tsea...@palladion.com wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 On 06/02/2013 09:00 PM, Zope tests summarizer wrote:
 This is the summary for test reports received on the zope-tests list
 between 2013-06-01 00:00:00 UTC and 2013-06-02 00:00:00 UTC:
 
 I'm not sure where we are with these failures.  I can't reproduce the
 exact failures on fresh checkouts, but I believe we are in a weird state
 due to a combination of factors:
 
 - - distribute / setuptools merger
 - - PyPI now HTTPS-only
 - - PyPI CDN caching?
 
 I think we should be aiming to switch our bootstraps over ASAP to pick up
 setuptools 0.7:  it doesn't appear to be simple at the moment to get that
 installed, as there is no 'ez_setup.py' in the beta location:

It also doesn't help that buildout 2 switched to requiring distribute just 
before distributed was merged into setuptools again.

Wichert.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope-tests - FAILED: 1, OK: 13

2013-05-28 Thread Wichert Akkerman

On May 28, 2013, at 08:19, Marius Gedminas mar...@gedmin.as wrote:

 On Tue, May 28, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
 [1]FAILED  winbot / z3c.layer.ready2go_py_265_32
   https://mail.zope.org/pipermail/zope-tests/2013-May/075191.html
 
 Looks like a transient network glitch:
 
Reading http://pypi.python.org/simple/zope.interface/
No local packages or download links found for zope.interface

FWIW I have had a lot of those in my own buildouts since pypi switched to a CDN.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope-tests - FAILED: 10, OK: 12

2013-03-15 Thread Wichert Akkerman
On Mar 15, 2013, at 07:57, Marius Gedminas mar...@gedmin.as wrote:
 
 [8]winbot / zope.app.wsgi_py_265_32
 
 I misunderstood last time.  *** empty log message *** does not mean
 this is a clone of an empty repo.  It's *the actual svn commit message*
 of the last commit: http://zope3.pov.lt/trac/changeset/124092
 
 The actual problem is
 
c:\Python26_32\python.exe bootstrap.py
Downloading 
 http://pypi.python.org/packages/2.6/s/setuptools/setuptools-0.6c11-py2.6.egg
Traceback (most recent call last):
  File bootstrap.py, line 257, in module
import zc.buildout.buildout
  File 
 c:\temp\tmpjpk_wq\zc.buildout-2.0.1-py2.6.egg\zc\buildout\buildout.py, line 
 18, in module
import zc.buildout.easy_install
  File 
 c:\temp\tmpjpk_wq\zc.buildout-2.0.1-py2.6.egg\zc\buildout\easy_install.py, 
 line 61, in module
pkg_resources.Requirement.parse('distribute')
AttributeError: 'NoneType' object has no attribute 'location'
 
 Weird.

That is likely buildout 2 with an older bootstrap.py

Wichert.


___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] ZTK 2.0: Deprecate zope.sequencesort

2013-03-01 Thread Wichert Akkerman

On Mar 1, 2013, at 19:06, Suresh V. suresh...@yahoo.com wrote:

 On Friday 01 March 2013 02:15 PM, Lennart Regebro wrote:
 I'm sorry, it's early in the morning. It is of course:
 
  sorted(sorted(news_stories, key=lambda x: x.publication_date,
reverse=True), key=lambda x: x.category)
 
 
 Won't the two sorteds step over each other?

No: since Python 2.2 sorting is guaranteed to be stable. See 
http://wiki.python.org/moin/HowTo/Sorting/#Sort_Stability_and_Complex_Sorts for 
more information.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] ZTK 2.0: Deprecate zope.sequencesort

2013-02-28 Thread Wichert Akkerman

On Feb 28, 2013, at 14:43 , Stephan Richter stephan.rich...@gmail.com wrote:

 Hi everyone,
 
 I would like to deprecate zope.sequencesort in ZTK 2.0, since it cannot 
 properly ported to Python 3, since it depends heavily on the cmp() way of 
 sorting. I am also not a user of the package and I only tried to port the 
 package for completeness sake.

What does it do? I could not find a single line of documentation for it, which 
makes it likely very few people, if any, are using it.

Wichert.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] [Plone-developers] Relaxing Zope id rules for Zope 4 / Plone 5

2013-02-21 Thread Wichert Akkerman

On Feb 21, 2013, at 09:08 , Hans-Peter Locher hans-peter.loc...@inquant.de 
wrote:

 In my opinion utf-8 urls are
 
 the same kind of evil as having 
 
 tabs and whitespaces in filenames.

Can you explain your reasoning?

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Relaxing Zope id rules for Zope 4 / Plone 5

2013-02-21 Thread Wichert Akkerman

On Feb 20, 2013, at 12:47 , Marius Gedminas mar...@gedmin.as wrote:

 On Wed, Feb 20, 2013 at 09:57:52AM +0100, Wichert Akkerman wrote:
 I want to propose that we do the following:
 
 Allow arbitrary str object ids in Zope 4 based on Dieter's work.
 Configure standard name choosers, normalizers, etc. used to generate
 ids for content to create UTF-8 object ids.
 
 *puts Python 3 porter hat on*
 
 Why UTF-8 byte strings instead of Unicode?

One subtle difference: I suggest byte strings which are set by default to UTF-8 
encoded strings when they are generated, but can be anything.

I have several reasons to not want to use unicode. One reason is that I am 
worried that this will break too much existing code; it is likely to require 
much more invasive changes in both Zope itself and third party packages. A 
second reason is that I feel that using unicode for an id is just wrong: an id 
can be any binary thing and does not need to be text: consider for example the 
unique ID for a user in active directory (ObjectGUID), or it can be text in a 
script that unicode does not support 
(http://www.unicode.org/standard/unsupported.html has a list), or it can come 
from a source that uses an unknown encoding or multiple encodings at the same 
time such as a filesystem or WebDAV users. For examples of the last see the 
crazy hoops Python 3 has to jump through to expose files via a unicode API, and 
even with all its magic tricks it still does not seem to work perfectly. The 
vast majority of object ids are text, but the ability to support other types of 
ids is extremely usef
 ul. So my suggestion would be: use unicode for object titles, descriptions, 
etc. but stick with byte strings for ids.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] [Plone-developers] Relaxing Zope id rules for Zope 4 / Plone 5

2013-02-21 Thread Wichert Akkerman
On Feb 21, 2013, at 09:26 , Christian Ledermann christian.lederm...@gmail.com 
wrote:

 I agree with Hans Peter,
 
 
 
 On Thu, Feb 21, 2013 at 11:09 AM, Wichert Akkerman wich...@wiggy.net wrote:
 
 On Feb 21, 2013, at 09:08 , Hans-Peter Locher hans-peter.loc...@inquant.de 
 wrote:
 
 In my opinion utf-8 urls are
 
 the same kind of evil as having
 
 tabs and whitespaces in filenames.
 
 have you ever tried to type german umlauts or russian characters on an
 english keyboard?

Yes, frequently.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] [Plone-developers] Relaxing Zope id rules for Zope 4 / Plone 5

2013-02-21 Thread Wichert Akkerman

On Feb 21, 2013, at 09:38 , Hans-Peter Locher hans-peter.loc...@inquant.de 
wrote:

 In a distributed application,
 you cannot always ensure that you have each component
 under control. 
 The url is the most basic interface to a web application.
 
 In Plone the id (and therefore the url) is generated from user's title input.
 For a title unicode is perfectly fine and needed (especially in unicode 
 countries like germany).
 
 If Plone/Zope would generate utf-8 ids by default you'll get utf-8 urls from
 the users generating the content immediately.
 
 This will lead to unpredictably errors (as most urls will still work as they 
 don't contain utf-8 but some do)
 in the distributed applications.

What kind of errors are you thinking of?

 Another issue might be that some developer tools might stop working / or only 
 work in latest versions
 
 E.g.
 
 Python's urllib and xmlrpclib
 Selenium IDE
 windmill
 jmeter
 …

All of these will still work fine. One thing to realise is that an UTF-8 URL 
itself is still an ASCII thing: it uses %-quoting for non-ASCII (and some 
other) characters. For example my local test site has a URL which looks like 
http://localhost:8080/Pløne/ in my browser but it really is 
http://localhost:8080/Pl%C3%B8ne/ . To get there Zope uses urllib.quote() 
internally, for example in the implementation of the absolute_url() method.

 In my opinion having utf-8 urls should be possible in Zope/Plone.
 But not by default.

I have no problem with making that configurable.

Wichert.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope-tests - FAILED: 13, OK: 16, UNKNOWN: 2

2013-02-21 Thread Wichert Akkerman

On Feb 22, 2013, at 07:30, Marius Gedminas mar...@gedmin.as wrote:

 On Fri, Feb 22, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
 [1]FAILED (failures=2) : Zope-trunk Python-2.6.8 : Linux
 [2]FAILED (failures=2) : Zope-trunk Python-2.7.3 : Linux
 
 Same old (menu actions are now unicode).

Ah, I might need to merge those fixes to trunk still.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Relaxing Zope id rules for Zope 4 / Plone 5

2013-02-20 Thread Wichert Akkerman
Currently Zope has two rules for object ids: 1) they must be str instances, and 
2) they must only consist of alphanumerics and a few extra characters. I have 
been playing around recently with trying to relax those rules to allow more 
flexible object ids, specifically allowing UTF-8 object ids. That seems to be 
entirely doable, and I made a simple package which monkey-patches Zope to do 
this: https://github.com/wichert/experimental.utf8id . Since all current 
browsers will interpret URLs as UTF-8 strings this will create beautiful URLs 
and gets us out of the ASCII-jail. Based on the result so far I want to suggest 
that we officially allow more flexible object ids for Zope 4.

Dieter Mauer tried something similar five (!!) years ago: 
https://github.com/zopefoundation/Zope/commit/40f1a4af3605204de7d803afe11f6cbbc97e0ccd
 . His approach differs a bit from mine: I added checks to make sure ids are 
valid UTF-8 and still disallow some characters, while he allows everything 
except a slash (/). That has the advantage of easily supporting things like 
binary user ids (for example GUIDs from Active Directory users).

I want to propose that we do the following:

Allow arbitrary str object ids in Zope 4 based on Dieter's work.
Configure standard name choosers, normalizers, etc. used to generate ids for 
content to create UTF-8 object ids.

Wichert.



___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope-tests - FAILED: 11, OK: 15, UNKNOWN: 4

2013-02-20 Thread Wichert Akkerman

On Feb 20, 2013, at 15:48 , Marius Gedminas mar...@gedmin.as wrote:

 On Wed, Feb 20, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
 This is the summary for test reports received on the 
 zope-tests list between 2013-02-18 00:00:00 UTC and 2013-02-19 00:00:00 UTC:
 
 I finally got tired of clicking at the links by hand and wrote a script:
 https://gist.github.com/mgedmin/4995950
 
 It gives me output like this:
 http://zope3.pov.lt/zope-tests-2013-02-20.html
 
 
 [1]UNKNOWN FAILED (failures=2) : Zope-2.13 Python-2.6.8 : Linux
   https://mail.zope.org/pipermail/zope-tests/2013-February/072605.html
 
 Failure in test test_menu (Products.Five.browser.tests.test_menu)
 
 Failed example:
pprint(menu[1])
 Expected:
{'action': u'@@cockatiel_menu_public.html',
...
 Got:
{'action': '@@cockatiel_menu_public.html',
...
 
 Failure in test 
 /home/stefan/autotest/temp/python26-zope213all/src/Products/Five/browser/tests/pages.txt
 
 Failed example:
page.__name__
 Expected:
u'eagle.txt'
 Got:
'eagle.txt'

These are probably my fault. I'll fix that.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] when did transaction lose the ability to be usable as a context manager?

2013-02-06 Thread Wichert Akkerman

On Feb 6, 2013, at 11:54 , Duncan Booth duncan.bo...@suttoncourtenay.org.uk 
wrote:

 Chris Withers ch...@simplistix.co.uk wrote:
 
 Hi All,
 
 I used to do this:
 
 import transaction
 with transaction:
 ...   print 'hello'
 ...
 Traceback (most recent call last):
   File console, line 1, in module
 AttributeError: __exit__
 
 When did that stop working and what should I now do instead?
 
 cheers,
 
 Chris
 
 
 You can use pure hackery to work around this:
 - t.py -
 def __enter__(*args):
print 'enter', args
 
 def __exit__(*args):
print 'exit', args
 
 def fixup():
import sys, types
self = sys.modules[__name__]
mymod = type(__name__, (types.ModuleType,), globals())
sys.modules[__name__] = mymod(__name__)
 fixup()

You can also use the transaction manager directly instead of the bound methods 
transaction lifts out of it:

import transaction
with transaction.manager:
pass

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Changing id generation in OFS CopyContainer

2013-01-11 Thread Wichert Akkerman
I want to use INameChooser to select the id of copied content. This is 
currently not possible since manage_pasteObject does not pass the object to be 
pasted to _get_id. I added a new wichert-ofs-paste-naming branch to extend 
_get_id to make that possible. Are there any objections to merging that change 
to 2.13 and trunk?

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Zope2 git mirror not updating?

2013-01-11 Thread Wichert Akkerman
I noticed that the Zope2 git mirror does not appear to be updating. Looking at 
https://github.com/zopefoundation/Zope/commits/2.13 it doesn't have any commits 
after November 15, while subversion has more recent commits from Hanno and 
Maurits. Did an updating process break? Or did development switch to github but 
the subversion repository was not made readonly?

Wichert.


___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope2 git mirror not updating?

2013-01-11 Thread Wichert Akkerman

On Jan 11, 2013, at 14:10 , Jens Vagelpohl j...@dataflake.org wrote:

 
 On Jan 11, 2013, at 14:07 , Wichert Akkerman wich...@wiggy.net wrote:
 
 I noticed that the Zope2 git mirror does not appear to be updating. Looking 
 at https://github.com/zopefoundation/Zope/commits/2.13 it doesn't have any 
 commits after November 15, while subversion has more recent commits from 
 Hanno and Maurits. Did an updating process break? Or did development switch 
 to github but the subversion repository was not made readonly?
 
 I had already mentioned in a different thread that the Zope and all 
 Products.* packages you see on GitHub are not final migrations, just test 
 migrations. Until a package is clearly marked as migrated in SVN (such as all 
 packages Jim and Tres migrated) the migration is not final and all changes 
 should still be checked into svn.zope.org.

Ok, noted. Perhaps it would make sense to not give write access on github for 
repositories that are not officially migrated to prevent confusion? I'm afraid 
I committed something on both github and svn.zope.org now since I initially 
thought github was the thing to use.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope.formlib's action decorator return Action() object, not the decorated function. Why?

2012-09-16 Thread Wichert Akkerman
On Sep 16, 2012, at 07:28, Marius Gedminas mar...@gedmin.as wrote:

 On Fri, Sep 14, 2012 at 01:44:30PM +0200, Jan-Wijbrand Kolman wrote:
 After years and years of heavily using zope.formlib it suddenly struck
 me that the zope.formlib.form.action decorator returns an Action()
 object instead of the decorated function (this action object is also
 added to the form's actions sequence as a side effect of the decorator).
 
 I know wonder: Why?
 
 (I've no clue.)

Another effect of this is probably that you can use sphinx's autodoc for 
actions which would be unfortunate.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope-tests - FAILED: 21, OK: 19

2012-09-06 Thread Wichert Akkerman

On 09/06/2012 10:58 AM, Marius Gedminas wrote:

On Thu, Sep 06, 2012 at 01:00:01AM +, Zope tests summarizer wrote:

[2]FAILED  winbot / z3c.coverage_py_265_32
https://mail.zope.org/pipermail/zope-tests/2012-September/067652.html


[3]FAILED  winbot / z3c.coverage_py_265_32
https://mail.zope.org/pipermail/zope-tests/2012-September/067651.html


[4]FAILED  winbot / z3c.coverage_py_265_32
https://mail.zope.org/pipermail/zope-tests/2012-September/067639.html

Mea culpa.

How do you redirect the stderr of a process spawned with
suprocess.Popen(shell=False) to /dev/null in a cross-platform manner?


Use NUL if you are running on Windows. You'll need to test the OS 
yourself - there is no cross-platform method as far as I know.


Wichert.



___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] We need to change how code ownership works.

2012-08-20 Thread Wichert Akkerman

On 08/20/2012 12:39 PM, Charlie Clark wrote:
Am 20.08.2012, 12:27 Uhr, schrieb Robert Niederreiter 
r...@squarewave.at:

even the linux kernel guys seem to prefer the benefits of github.

 https://github.com/torvalds/linux


Yes, promotional materials would have nothing to do with the 
commercial nature of the service. Not that I'm against a commercial 
service provider.


In this case also untrue as far as I know: Linus only setup a mirror on 
github to have some way to publish a git tree after the kernel.org 
comprise. He was also very explicit about not willing to use any github 
features.


Wichert.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github

2012-08-19 Thread Wichert Akkerman

On 2012-8-19 12:59, Robert Niederreiter wrote:

On 19.08.2012 12:16, Jens Vagelpohl wrote:

Done by a contributor with some clear gesture from the non-contributor
that code ownership is going into the hands of that contributor.

How does this 'clear gesture' from the non-contributor look like right
now? A patch attached to an email or a bug report? As Lennard pointed
out, how does this differ from a pull request attached to a repository?


A simple solution to allow pull requests but keep the 
submitter-has-signed-policy check is to only allow pull requests made 
from a ZF-owner repository. github allows pull requests from a different 
branch within the same repository which makes this very easy.


Wichert.

--
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github

2012-08-18 Thread Wichert Akkerman

On 2012-8-18 10:39, Jens Vagelpohl wrote:

Hi Hanno,

Legally this must be a fork then and I'm not sure it can be released as 
official Zope Foundation software anymore if you make releases from GitHub.


Doesn't the name zc.buildout imply that it is a Zope Corp project 
instead of a Zope Foundation one? The author has also never been listed 
as the foundation but Jim personally, which seems to imply zc.buildout 
never was Zope Foundation-owned software.


Wichert.

--
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope.i18n plural form support

2012-05-18 Thread Wichert Akkerman

On 05/17/2012 10:42 PM, Thomas Massmann wrote:

Hi,

I added the plural form support (see a corresponding ticket here: 
https://bugs.launchpad.net/zope.i18n/+bug/161985) in a separate 
branch: https://code.launchpad.net/~thomas-massmann/zope.i18n/plural. 
This code was mainly implemented during the 2012 Plonekonf in Munich.


It is already in production since 3 months in a project I'm 
developing right now. Please note that zope.i18nmessageid needs to be 
taken from this branch to work: 
https://code.launchpad.net/~thomas-massmann/zope.i18nmessageid/plural.


Extracting plural messages is supported by xgettext by default. Zope 
tools like i18nduder have to be adjusted (they don't support ungettext 
right now). I already adjusted lingua by Wichert Akkerman 
(https://github.com/tmassman/lingua) - the pull request is still open.


If I remember correctly that pull request is waiting for someone to add 
plural support to translationstring as well. Are you willing to 
implement that?


Wichert.



___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope.i18n plural form support

2012-05-18 Thread Wichert Akkerman

On 05/18/2012 10:07 AM, Thomas Massmann wrote:

Hi,

I can do it. But I'm not that familiar with Pylons/Pyramid right now. 
So this will basically take some time. But, yes ;)


translationstring is a very simple package that doesn't have any 
Pylons/Pyramid dependencies itself. It shouldn't be hard to do if you've 
already handled zope.i18n :)


Wichert.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope 4 release management

2012-02-01 Thread Wichert Akkerman

On 02/01/2012 02:29 PM, Alex Clark wrote:
Actually, they introduced improved Subversion client support late last 
year:


- https://github.com/blog/966-improved-subversion-client-support


Unfortunately it is too unstable to be usable.

Wichert.


___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] [Checkins] SVN: z3c.form/trunk/setup.py Get ready for 2.6.1 release.

2012-01-31 Thread Wichert Akkerman

On Tue 31 Jan 2012 08:24:24 AM CET, David Glick wrote:

On 1/30/12 11:15 PM, Adam GROSZER wrote:

Hello,

I think we need to automate sdist upload, the .mo files are missing
from the release.

Any ideas other than patching setup.py to create the .mo files
automatically?


See zest.releaser [1] and its plugin zest.pocompile [2]


Personally I use a makefile to take care of tasks like that.

Wichert.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope 2 WSGI investigation

2012-01-03 Thread Wichert Akkerman

On 01/03/2012 10:04 AM, Jens Vagelpohl wrote:

On Jan 3, 2012, at 09:34 , Sylvain Viollon wrote:

  We use Paster as well in the stack, and use it to configure the Python 
logging process, you can configure
there a logging to syslog, and after having a central syslog server. I think it 
is more professional like this,
than using a tool in Zope's UI.

Logging to syslog usually leads to problems due to the maximum message size for 
syslog entries. Error log messages with a traceback tend to be cut off and 
information lost.


Don't log the entire error as one syslog entry, but use one syslog entry 
for every line in the error log. That is a standard way to dealing with 
this kind of thing.


Wichert.



___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope 2 WSGI investigation

2012-01-02 Thread Wichert Akkerman

On 01/01/2012 08:39 PM, Martin Aspeli wrote:

Hi,

There are three known WSGI implementations of the Zope 2 publisher.
I've had a look at them and made some notes about what I think
provides the best story:

## Zope 2.13 WSGIPublisher

Pros:

* Allows distributed transaction management with repoze.tm2
* Allows distributed retry with repoze.retry
* Ships with Zope
* Quite simple

Cons:

* Requires repoze.tm2 and repoze.rety


Why is that a con? I use repoze.tm2 and repoze.retry with all my pyramid 
projects and they work beautifully.


Wichert.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Supporting interworking with repository branches on github

2011-11-23 Thread Wichert Akkerman
On 11/24/2011 01:29 AM, Florian Friesdorf wrote:
 On Wed, 23 Nov 2011 09:50:49 -0500, Tres Seavertsea...@palladion.com  wrote:
 Second, it is already feasible to work with modern VCSes against the
 existing SVN repository:  I've been doing it with bzr for literally years
 now;  I know of lots of documentation on using git against SVN as well. Of
 course, Github is more than a VCS, but its main advantage over other
 solutions lies in being able to accept casual contributions from non-core
 developers, which is hardly in scope for the early phases of the Zope4
 effort.
 github enables a peer review process: while everybody who signed the
 plone committer agreement could just commit to the plone repo, we do
 pull-requests and somebody else with commit rights checks the request
 and merges.

We've never had a problem with peer review before. People review the 
commit lists which receive all commits with full diffs and react if they 
see something off. That is a very well working peer review system. I 
don't see that improving with github; in fact I see it becoming worse: 
commit emails no longer get diffs at all, and people are less likely to 
look at a webinterface for a quick review than they are to take a quick 
look at an email. The move from Plone to github certainly made me stop 
all review work, where I reviewed all commits to core code before.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope 4 roadmap

2011-11-22 Thread Wichert Akkerman
On 11/22/2011 11:13 AM, Sylvain Viollon wrote:
 Op 17 nov 2011, om 20:57 heeft Tres Seaver het volgende geschreven:
 Note that there is a counter-trend here among the Pyramid crew:  many
 developers *want* tight integration of authentication, particularly the
 login forms.

I'm not sure I fully agree with that observation. I think the trend is 
that trying to do the UI part of authentication in middleware turned out 
to be a mistake and people are moving away from that. But everything 
else does not need tighter integration.
 And there is a major issue with this is that for the moment your 
 authentication depends from where you are in your Zope 2 application. Maybe 
 in some part of the application the authentication will be done using LDAP, 
 and not in some other: you can have a acl_users only for some part of the 
 application, and users there are available locally and not globally. That is 
 because the authentication is done after the traversing. If you want to do 
 this in a WSGI middleware, you will have to do the traversing in a WSGI 
 middleware before, otherwise lot of people won't be able to migrate theirs 
 applications to Zope 4, because the paradigm changed.

Realistically though: how often is that used? Is that enough to warrant 
the extra complexity?

WIchert.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Undelivered Mail Returned to Sender

2011-11-09 Thread Wichert Akkerman
On 11/09/2011 09:57 AM, Chris Withers wrote:
 Any idea what mx1.emailsrvr.com doesn't like?
 Is it Bejni's address, the email in question or that isn't coming from 
 server1.simplistix.co.uk?

The first - it looks like zope.com email isn't configured correctly.

Wichert.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope.testrunner and nose count doctests differently

2011-11-03 Thread Wichert Akkerman
On 11/03/2011 11:54 AM, Matthew Wilkes wrote:
 On 2011-11-03, at 0025, Chris Withers wrote:

 I'm experimenting with using nose as an alternative to zope.testrunner
 so I can take advantage of the junit and cobertura compatible xml output
 offered.
 Using http://pypi.python.org/pypi/collective.xmltestreport might be easier? 
 Not sure if it gives you everything you need, but works well for us Plonies.

It doesn't do coverage in a way jenkins can handle iirc. I have to run 
bin/coverage bin/test to get coverage data.


___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope-tests - FAILED: 13, OK: 40

2011-10-31 Thread Wichert Akkerman
On 10/31/2011 07:21 AM, Tres Seaver wrote:
 These
 are all failures in the following zopeapp test::

 -  zope/app/applicationcontrol/tests/test_zope_version.py 
  def test_WrongLocale(self):
  Demonstrate bug 177733
  currentPath = os.path.dirname(os.path.abspath(__file__))
  if isSVNAvailable() and isSVNCheckout(currentPath):
  zv = ZopeVersion(currentPath)
  zv.getZopeVersion()
  # check that we don't get a 'Development/Unknown' version
  self.assert_(zv.result.startswith('Development/Revision: '))
 - --

 I have no theory for how that test could suddenly start failing (nor
 even what it is really supposed to test).  It doesn't fail on my
 machine on any version of Python.

Different version of subversion installed perhaps?

Wichert.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Missing Zope2 tarballs

2011-10-12 Thread Wichert Akkerman
On 10/12/2011 10:45 AM, Jens Vagelpohl wrote:
 On Oct 11, 2011, at 18:38 , Wichert Akkerman wrote:
 I have a buildout that needs
 http://www.zope.org/Products/Zope/2.7.8/Zope-2.7.8-final.tgz still..
 Jim sent me a tarball containing just the binary files from underneath 
 /Products, such as .tgz, .exe, etc. As a first try, I have stitched them into 
 the old.zope.org tree using rewrite rules in order to avoid rewriting links 
 all over the HTML documents. Can you try your buildouts and let me know if 
 they work?

Seems to work fine. Thanks!

Wichert.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Missing Zope2 tarballs

2011-10-11 Thread Wichert Akkerman
On 2011-10-11 17:14, Alex Clark wrote:
 On 10/11/11 3:17 AM, Jens Vagelpohl wrote:

 On Oct 11, 2011, at 03:33 , Alex Clark wrote:

 Hi,

 Anyone notice these missing tarballs?

 - http://old.zope.org/Products/Zope/2.9.12/Zope-2.9.12-final.tgz/
 - http://old.zope.org/Products/Zope/2.10.13/Zope-2.10.13-final.tgz/
 - http://old.zope.org/Products/Zope/2.11.4/Zope-2.11.4-final.tgz/

 Hi Alex,

 With the help of Jim, who produced a tarball containing the spidered content 
 of old.zope.org, the site has been converted to a static site. There will 
 inevitably be issues here and there. I'll take a look to see if I can find 
 the original files from the old app server.


 Thanks Jens, I know I occasionally need to build old Plone sites, as far
 back as 2.1 but also sometimes 2.5.x and 3.{0,1,2}.x all of which use
 the old tarballs ranging from Zope 2.8 - 2.11 (I think). Building these
 sites will require at least the final from each series to continue
 working. Ultimately, I'd love to be able to access all the old tarballs
 e.g. similar to:

I have a buildout that needs 
http://www.zope.org/Products/Zope/2.7.8/Zope-2.7.8-final.tgz still..

Wichert.

-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] direction

2011-07-04 Thread Wichert Akkerman
On 2011-7-4 11:59, Marius Gedminas wrote:
 On Sun, Jul 03, 2011 at 06:10:48PM +0200, Wichert Akkerman wrote:
 On 2011-7-3 17:48, Martin Aspeli wrote:
 FWIW, we have a high-performance, high-load application in production on
 Plone 4 with collective.beaker relying heavily on sessions, and I'm not
 aware of any problems with it. We use the memcached backend across two
 physical servers and a large number of Zope clients.

 In my experience it depends highly on the memcache client library you
 use with beaker. With some the results are disastrous, with other it is
 stable. Where possible I have switched to cookie-based sessions to
 prevent stability problems.

 Aren't all sessions cookie-based?

 Did you mean you switched to secure cookies instead of server-side state?

I meant the cookie-backend, which indeed securely stores all data in a 
cookie instead of keeping any state serverside.

Wichert.


-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] direction

2011-07-03 Thread Wichert Akkerman
On 2011-7-3 17:48, Martin Aspeli wrote:
 FWIW, we have a high-performance, high-load application in production on
 Plone 4 with collective.beaker relying heavily on sessions, and I'm not
 aware of any problems with it. We use the memcached backend across two
 physical servers and a large number of Zope clients.

In my experience it depends highly on the memcache client library you 
use with beaker. With some the results are disastrous, with other it is 
stable. Where possible I have switched to cookie-based sessions to 
prevent stability problems.

Wichert.


-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] versions on zope.org and launchpad.net

2011-06-29 Thread Wichert Akkerman
On 2011-6-29 03:02, Johannes Raggam wrote:
 On Tue, 2011-06-28 at 18:17 -0400, Tres Seaver wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 06/28/2011 01:28 PM, Johannes Raggam wrote:

 there is a different version set on zope.org and launchpad.

 on http://www.zope.org/Products/Zope/swpackage_releases
 there are zope 2.8.12, 2.9.12, 2.10.13 and 2.11.8 available, where on
 launchpad they are not.
 [...]
   - PyPI is the canonical download location for the current releases:
 launchpad should just be pointing there.
 thats the case since Zope 2.12. older releases aren't there.
 i think that launchpad should have all releases available, which are
 listed on zope.org.

My question would be: why launchpad? Is anyone expecting launchpad to be 
a canonical resource for Zope releases? As far as I know none of our 
documentation refers to launchpad for downloads and launchpad has never 
been used for anything other than it's bugtracker.

I would agree that it would be nice to have a single location that lists 
historic releases, I would expect that to be on zope.org instead of 
launchpad or some other random third party website.

Wichert.

-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Test fixture concepts

2011-04-20 Thread Wichert Akkerman
On 2011-4-20 21:59, Martijn Faassen wrote:
 On 03/29/2011 02:43 PM, Wichert Akkerman wrote:
 On 3/29/11 14:40 , Stephan Richter wrote:

 Yeah, Marius led me recently to that path too. Write a narrative in text 
 files
 and use doc strings of functions to do edge cases (or when you don't have 
 time
 for the narrative). I am getting used to it. I still much prefer the sort of
 output comparison that doctests/manuel gives me over the assertion language
 that unittest.TestCase requires.

 FWIW unittest2 has much nicer output if you use the new assert methods.

 py.test has very nice output if you use the Python 'assert' statement.
 There are no assert methods to remember.

That sounds nice. I have used Catch 
(https://github.com/philsquared/catch) a lot for C++ testing recently 
which also uses a single assert statement instead of a miriad of assert* 
functions, and it has been a very pleasant experience.

Wichert.

-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] CSRF protection for z3c.form

2011-04-04 Thread Wichert Akkerman
On 2011-4-4 18:22, Roger wrote:
 Hi Laurence, Stephan

 Just because you can write login forms with
 z3c.form this package has nothing to do with
 authentication. That's just a form framework!

 Authentication is defently not a part
 of our z3c.form framework and should not
 become one.

 Why do you think authentication has something
 to do with the z3c.form library? Did I miss
 something?

CSRF has nothing to do with authentication. It has to do with securing 
forms on websites.

Wichert.

-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] z3c.schema

2011-03-31 Thread Wichert Akkerman
On 3/31/11 08:23 , Jan-Jaap Driessen wrote:
 Hi,

 I added nl translations to z3c.schema, could someone grant me
 ('janjaapdriessen') pypi access so I can release this as 0.7.1?

Can you reply to my comment on your translation commit? I don't think 
the current language used in z3c.schema is very user friendly.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Test fixture concepts

2011-03-29 Thread Wichert Akkerman
On 3/29/11 14:40 , Stephan Richter wrote:
 On Tuesday, March 29, 2011, Jim Fulton wrote:
 so I may forgo them.

 Which is a mistake. You should create separate tests.  I typically put
 large tests, dealing with main use cases where there is a definite
 flow of activity in '.test' files.  I do these in separate files
 because they're easier to write that way.  I use a '.test' suffix to
 avoid the pretense that these are documentation.  I put edge-case
 tests in small docstrings in testing modules.  I'm not really
 religious about using doctests for this, but I find small edge-case
 doctests easier to read than traditional unit tests. It's possible
 that I'd like py.test tests as much.

 Yeah, Marius led me recently to that path too. Write a narrative in text files
 and use doc strings of functions to do edge cases (or when you don't have time
 for the narrative). I am getting used to it. I still much prefer the sort of
 output comparison that doctests/manuel gives me over the assertion language
 that unittest.TestCase requires.

FWIW unittest2 has much nicer output if you use the new assert methods.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Anyone want to do Google Summer of code mentoring for PSF?

2011-03-21 Thread Wichert Akkerman
On 2011-3-20 17:47, Hanno Schlichting wrote:
 Sure. I didn't mean to exclude this. Pyramid allows you to do a very
 explicit configuration without any scanning. If you write an
 application and have full control over all its parts, this works.

 Things get complicated, once you reuse libraries which in turn have
 other library dependencies with configuration actions. Ignore the
 naming for the moment. You could call these application components,
 arguing that a library shouldn't have any hard configuration
 requirements.

 Currently we have an explicit approach via providing a configure.zcml
 in each library, which causes all relevant parts to be imported and
 hooked up. One library can include the ZCML of another library or a
 subpackage of its own. Either each library provides a similar central
 place, which imports all its modules with configuration actions, or
 you use the scanning approach to avoid the explicit mechanism.

 Also, If there's an existing mechanism that does what I want and I'm
 just ignorant of, I'd be happy to learn about it.  If such a thing
 exists or can be cobbled together from existing ideas, I'd like to
 elevate it either as part of the ZCA or as a best-practice tool that
 stands independent of any particular application framework.

 I think venusian, the venusian actions and the configuration machinery
 of Pyramid come pretty close to this. Personally I think we could
 extract these and roll them back into the ZTK.

Pyramid's config.include sounds like exactly that.

Wichert.

-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Anyone want to do Google Summer of code mentoring for PSF?

2011-03-21 Thread Wichert Akkerman
On 3/21/11 10:17 , Jan-Wijbrand Kolman wrote:
 On 3/20/11 16:12 PM, Wichert Akkerman wrote:
 Pyramid only does so if you tell it to do so by using config.scan(). You
 are not obliged to do that, and I have several pyramid projects which do
 not do any scanning. Not doing scanning has the advantage of making
 configuration more explicit, and it speeds application startup immensely.

 Just to get this clear for me: if you're not scanning, the information
 left by the class decorators would be inert? So, you'd have to do the
 registrations yourself, right?

Yes.

 - you may have some draft files in your tree that are not ready for use
  and never referenced anywhere, but a scan will still process them.

 This is true.

I ran into this with .html.py files generated by Chameleon as well. My 
Zope startup has lots of these:

/Users/wichert/Library/eggs/zope.configuration-3.6.0-py2.6.egg/zope/configuration/config.py:605:
 
UserWarning: File 'sessions.pt.pyc' has an unrecognized extension in 
directory 
'/Users/wichert/Work/syslab/euphorie/Develop/trunk/buildout/src/Euphorie/euphorie/client/templates'


 - scanning can take a long time, making application (re)start slow for
  non-trivial projects

 At what point is an application not trivial anymore? In applications I
 build so far, startup time has not been an issue at all. But maybe my
 applications are still on the trivial-end of the spectrum ;)

If your application takes 5 seconds to start I'ld call it non-trivial :)

 - problems in the scanning process tend to be very hard debug. If a
  view is not processed during scanning figuring out why can be
  painful, and there are little to no tools to help you. This is
  especially true for more complex scanning environments such as the
  plone/dexterity/z3cform stack; as an example I spent over an hour
  yesterday trying to figure out why a form was not picked up while
  other views in the same python file worked fine.

 I think this can be true. In my experience not relying on implicitly or
 guessed configuration parameters helps a little here. What in this
 specific example was the reason for the view not being picked up?

A missing zcml include for meta.zcml of plone.directives.form, while 
it's configure.zcml was included correctly.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Anyone want to do Google Summer of code mentoring for PSF?

2011-03-20 Thread Wichert Akkerman
On 3/20/11 16:00 , Hanno Schlichting wrote:
 On Sun, Mar 20, 2011 at 3:28 PM, Jim Fultonj...@zope.com  wrote:
 - The mechanism shouldn't require something to grok/analyze the
   code.  The mechanism should be explicit. This is implied by
   pythonic.  I remember Grok being more implicit than skimming the
   links above suggest. Perhaps Grok has has become more explicit than
   I remember.

 Both Grok and Pyramid (or martian and venusian really) do a scan of
 the code to find the registration hints.

Pyramid only does so if you tell it to do so by using config.scan(). You 
are not obliged to do that, and I have several pyramid projects which do 
not do any scanning. Not doing scanning has the advantage of making 
configuration more explicit, and it speeds application startup immensely.

Scanning is needed if you want to mix configuration and code in one 
place. That may not be the right model for everyone.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Anyone want to do Google Summer of code mentoring for PSF?

2011-03-20 Thread Wichert Akkerman
On 3/20/11 16:03 , Wichert Akkerman wrote:
 On 3/20/11 16:00 , Hanno Schlichting wrote:
 On Sun, Mar 20, 2011 at 3:28 PM, Jim Fultonj...@zope.com   wrote:
 - The mechanism shouldn't require something to grok/analyze the
code.  The mechanism should be explicit. This is implied by
pythonic.  I remember Grok being more implicit than skimming the
links above suggest. Perhaps Grok has has become more explicit than
I remember.

 Both Grok and Pyramid (or martian and venusian really) do a scan of
 the code to find the registration hints.

 Pyramid only does so if you tell it to do so by using config.scan(). You
 are not obliged to do that, and I have several pyramid projects which do
 not do any scanning. Not doing scanning has the advantage of making
 configuration more explicit, and it speeds application startup immensely.

Let me try to argue this better. Downsides of scanning are:

- it scans your tests, which can result in unexpected behaviour you
   may not expect (at least for venusian, not sure if this is true for
   martian).
- you may have some draft files in your tree that are not ready for use
   and never referenced anywhere, but a scan will still process them.
- scanning can take a long time, making application (re)start slow for
   non-trivial projects
- problems in the scanning process tend to be very hard debug. If a
   view is not processed during scanning figuring out why can be
   painful, and there are little to no tools to help you. This is
   especially true for more complex scanning environments such as the
   plone/dexterity/z3cform stack; as an example I spent over an hour
   yesterday trying to figure out why a form was not picked up while
   other views in the same python file worked fine.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope.testbrowser and WebTest (round 2)

2011-01-31 Thread Wichert Akkerman
On 2011-1-31 07:02, Wolfgang Schnerring wrote:
 * Brian Sutherlandbr...@vanguardistas.net  [2011-01-30 16:04]:
 I've finally finished refactoring my WebTest/testbrowser branches,
 basically doing this:

  - Integrate with WebTest. zope.testbrowser.webtest.Browser is a new
Browser implementation that uses webtest.TestApp to drive a WSGI
application. This allows simple and direct testing of WSGI 
 applications.

  - Re-write the test application as a pure WSGI application using WebOb.
Run the existing tests using the WebTest based Browser

  - Move zope.app.testing based Browser into zope.app.testing (leaving
backwards compatibility imports in-place).

 This is a very big change, so I would appreciate anyone who would take a
 look at these branches before I merge:

 Michael Howitz and I recently polished the integration of
 zope.testbrowser and wsgi_intercept to accomplish pretty much the same
 things you mentioned. (I'm aware that you two exchanged some emails
 about it, but don't know any details).

 So I'm curious: What are the differences bewteen WebTest and
 wsgi_intercept? Is one preferable to the other?

If I remember correctly WebTest wraps the WSGI app object directly and 
does not require monkeypatching urllib. To send requests to the app 
under testing you call WebTest post/get methods, which directly call the 
WSGI app.

Wichert.

-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] [Checkins] SVN: zope.testbrowser/tags/3.10.3/src/zope/testbrowser/tests made room for more tests

2011-01-24 Thread Wichert Akkerman
On 1/24/11 14:03 , Michael Howitz wrote:
 Log message for revision 119869:
made room for more tests


 Changed:
A   zope.testbrowser/tags/3.10.3/src/zope/testbrowser/tests/
A   zope.testbrowser/tags/3.10.3/src/zope/testbrowser/tests/__init__.py
A   zope.testbrowser/tags/3.10.3/src/zope/testbrowser/tests/helper.py
A   zope.testbrowser/tags/3.10.3/src/zope/testbrowser/tests/test_browser.py
A   
 zope.testbrowser/tags/3.10.3/src/zope/testbrowser/tests/test_doctests.py
D   zope.testbrowser/tags/3.10.3/src/zope/testbrowser/tests.py

I'm assuming that this should not have happened in a tag. Can you please 
revert these changes and redo them in trunk or a branch?

Wichert.


___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] ConnectionStateError

2011-01-12 Thread Wichert Akkerman
On 1/12/11 14:34 , Godefroid Chapelle wrote:
 I also wonder what was the reason to deprecate ``zope.thread``. I see it
 was used by ``zope.component`` to hold thread-safe siteinfo.

It has been obsoleted by 
http://docs.python.org/library/threading.html#threading.local

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 40 OK, 4 Failed

2010-12-21 Thread Wichert Akkerman
On 2010-12-22 00:22, Stephan Richter wrote:
 On Tuesday, December 21, 2010, Tres Seaver wrote:
 I didn't look at the RML failures.  I'm not even sure we should be
 running them, at least not every night, as I doubt the package is at all
 widely used (but I'm willing to be shouted down ;).

 I am frequently getting bug reports from users. And it had 742 downloads since
 July. That is not a huge number, but more than other packages that are not
 part of the standard Plone/Zope 2/Bluebream dependency tree.

If only those bugreports would get some response :)

Wichert.


-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 40 OK, 4 Failed

2010-12-21 Thread Wichert Akkerman
On 2010-12-22 11:13, Stephan Richter wrote:
 On Tuesday, December 21, 2010, Wichert Akkerman wrote:
 I am frequently getting bug reports from users. And it had 742 downloads
 since July. That is not a huge number, but more than other packages that
 are not part of the standard Plone/Zope 2/Bluebream dependency tree.

 If only those bugreports would get some response :)

 You having an outstanding one to me? :-) I have addressed all the ones in my
 inbox in July. :-) I could find some time in the next days to do another round
 of bug fixing.

I added three tickets on launchpad in October :). A big problem for me 
appears to be that z3c.rml implements an older version of RML, so a lot 
of the directives in the RML documentation fail (at least of the few I 
wanted to use). And since z3c.rml silently ignores unsupported tags it 
took me quite some time to determine that the problem was not in my RML.

Wichert.


-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Draft of new aggregator

2010-12-01 Thread Wichert Akkerman
On 12/1/10 09:04 , Jens Vagelpohl wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 12/1/10 08:59 , Wichert Akkerman wrote:
 On 2010-12-1 07:43, Christian Theune wrote:
 Here's the draft we ended up with yesterday:
 http://dpaste.com/281566/

 Can you move the non-OK results above the list of reports received? That
 way you have the most important information first.

 - -1 on moving. Maybe the non-OK entries could be copied into an
 additional section at the top instead.

 If I understood Christian right he wants to keep the full list of
 entries sorted so everyone knows where to find their items of interest
 quickly. I think that's valuable, the full list should stay as it is.

It does mean that you always have to scroll down 3 pages before you see 
anything important.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Draft of new aggregator

2010-11-30 Thread Wichert Akkerman
On 2010-12-1 07:43, Christian Theune wrote:
 On 11/30/2010 06:04 PM, Jens Vagelpohl wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 11/30/10 16:06 , Christian Theune wrote:
 Hi,

 here's a shot at a new format of the aggregated mails.

 My focus on this draft was:

 - allow dealing with *lots* of results every day more easily
 - allow having a graphical overview of how broken something is
  (group builders by prefix)
 - have a stable sorting so you can quickly pin-point whether something
  that you're interested in is broken
 - reduce the noise

 Looks good to me, much better than what we have now. I'm guessing the
 URLs will be fixed to point to http://mail.zope.org... instead of
 file:///tmp/mail.zope.org..., right?

 Yeah. I just mirrored the data to my local machine to get faster results
 ...

 Here's the draft we ended up with yesterday:
 http://dpaste.com/281566/

Can you move the non-OK results above the list of reports received? That 
way you have the most important information first.

Wichert.

-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] I want some Python 3 C coding style guidance.

2010-11-25 Thread Wichert Akkerman
On 11/25/10 11:31 , Lennart Regebro wrote:
 Which style do you prefer? I'll make zope.hookable, zope.i18nmessage
 and zope.proxy use the same style if we can agree on one.

The second. #ifdefs in code make code hard to follow and tend to lead to 
problems. FWIW the Linux kernel tree has a similar policy: they hide all 
differences behind macros and helper functions.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] [Checkins] SVN: zopetoolkit/doc/source/releaseteam/ minutes of ztk releaseteam meeting 11/09

2010-11-18 Thread Wichert Akkerman
On 11/18/10 11:16 , Jan-Wijbrand Kolman wrote:
 +The ZTK would like to use distribute by default.

Is the distribute project still alive? The reason I ask is that my 
recent experience is that bugs reported in setuptools are fixed very 
quickly, while there is no response from the distribute team.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] SVN: zopetoolkit/doc/source/releaseteam/ minutes of ztk releaseteam meeting 11/09

2010-11-18 Thread Wichert Akkerman
On 11/18/10 16:50 , Tres Seaver wrote:
 I'm -1 on preferring 'distribute' in any overt way in the ZTK.  Folks
 who want it can already use it when bootstrapping a buildout::

+1 (on your -1)

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] PAS CookieAuthHelper and insufficient privileges

2010-10-12 Thread Wichert Akkerman
On 10/12/10 02:21 , Laurence Rowe wrote:
 I'm currently implementing single sign on across Plone sites but have
 run into a bit of an issue with the CookieAuthHelper.

 Unauthorized accesses are redirected to its login_path attribute even
 when a user is already logged in. Plone works around this with a
 require_login script that traverses to insufficient_privileges (rather
 than login_form) when the user is not anonymous.
 http://dev.plone.org/plone/browser/Plone/trunk/Products/CMFPlone/skins/plone_login/require_login.py

The result is still nasty since it means the unauthorized error will 
always consider the user to be unauthenticated. I've implemented a 
workaround in NuPlone to fix that, see 
http://svn.plone.org/svn/collective/NuPlone/trunk/plonetheme/nuplone/skin/error.py
 
. Perhaps something based on that will work for you as well.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 42 OK, 8 Failed

2010-10-07 Thread Wichert Akkerman
On 10/7/10 08:52 , Jens Vagelpohl wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 10/6/10 18:33 , Tres Seaver wrote:
 +1 for dropping the test:  if we aren't going to try to fix it to pass,
 then scrap it.  Note that I actually feel the same way about *all* the
 every-day failures:  the value of the every-day mail drops sharply when
 there are any expected failures.

 For me personally the value has dropped so far that I am mostly ignoring
 those emails. They are hard to parse to begin with and there are just
 too many buildbot entries.

Likewise. I've redirected all test-mails to /dev/null for a long time.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 42 OK, 8 Failed

2010-10-07 Thread Wichert Akkerman
On 10/7/10 11:09 , Patrick Gerken wrote:
 On Thu, Oct 7, 2010 at 10:50, Wichert Akkermanwich...@wiggy.net  wrote:
 On 10/7/10 08:52 , Jens Vagelpohl wrote:
 For me personally the value has dropped so far that I am mostly ignoring
 those emails. They are hard to parse to begin with and there are just
 too many buildbot entries.

 Likewise. I've redirected all test-mails to /dev/null for a long time.

 Which projects do you not want to see in this summary mail?

Perhaps more important is brevity. If the mail was a simple thing with a 
maximum of 15 lines or so where you can immediately see if something is 
wrong or not it would be much better. Something like:

PROBLEMS


ZTK 1.0/python2.4: win32 5 errors, 2 failures
GROK 1.1/python2.6: linux 2 errors


and simply don't list things that do not have problems.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 42 OK, 8 Failed

2010-10-07 Thread Wichert Akkerman
On 10/7/10 11:26 , Hanno Schlichting wrote:
 On Thu, Oct 7, 2010 at 11:22 AM, Wichert Akkermanwich...@wiggy.net  wrote:
 Perhaps more important is brevity. If the mail was a simple thing with a
 maximum of 15 lines or so where you can immediately see if something is
 wrong or not it would be much better. Something like:

 PROBLEMS
 

 ZTK 1.0/python2.4: win32 5 errors, 2 failures
 GROK 1.1/python2.6: linux 2 errors

 +1 for a brief summary, the direct links to the build results are
 still important though and should be somewhere in the mail

Make it a multipart/alternative mail and use links in the html version 
so you can click on things without having to waste extra space on links?

 and simply don't list things that do not have problems.

 I'd still list those at the bottom. We have a rather high variability
 in the number of jobs run. I'd like to see if some jobs didn't run at
 all and didn't sent any mails.

That would be a problem that should be at the top.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 42 OK, 8 Failed

2010-10-07 Thread Wichert Akkerman
On 10/7/10 11:35 , Patrick Gerken wrote:
 On Thu, Oct 7, 2010 at 11:28, Wichert Akkermanwich...@wiggy.net  wrote:
 On 10/7/10 11:26 , Hanno Schlichting wrote:
 +1 for a brief summary, the direct links to the build results are
 still important though and should be somewhere in the mail

 Please don't forget we also have a page that links to all buildbots
 and display latest status too.

 http://docs.zope.org/zopetoolkit/process/buildbots.html

That's certainly a hell of a lot better than those emails! It would be 
even nicer if there was a page with just the status information; as it 
is now I have to scroll two pages down to get to the useful data.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] z3c.recipe.i18n

2010-10-06 Thread Wichert Akkerman
On 10/6/10 09:53 , yuppie wrote:
 Hi!


 Jan-Wijbrand Kolman wrote:
 This afternoon I merged the gary-0.8.0 branch for z3c.recipe.i18n. The
 recipe now uses and depends on zc.buildout-1.5.1 features. I'd like to
 release this merge as 0.8.0 as this make it possible to move grok and
 the groktoolkit over to zc.buildout-1.5.1. I guess this is also useful
 in the light of moving the ZTK itself to zc.buildout 1.5.1 at some point.

 Unless there are objections of course :)

 +1

 But could you please make it more explicit that 0.8.0 drops support for
 zc.buildout 1.4? Your CHANGES.txt note is not clear about that and maybe
 install_requires should specify the new requirement explicitly.

I'ld even go so far as to say install_requires must specify such a 
requirement.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Extending Zope2 bin/instance run

2010-09-09 Thread Wichert Akkerman
On 9/3/10 18:21 , Tres Seaver wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Wichert Akkerman wrote:
 I have noticed that now that we are almost exclusively using eggs to
 distribute our software using bin/instance run has become difficult:
 often the script you want to run is located inside an egg which makes to
 path to it hard to predict. This is not the most user friendly command:

 bin/instance run eggs/my.package-*/my/package/script.py

 If a user is using a shared egg directory from zc.buildout or something
 else the egg can be anywhere on the filesystem, making it next to
 impossible to explain to users.

 I am considering to modify bin/instance run to check if its first
 argument is a filesystem path, and if not consider the argument to be a
 dotted name of a callable which should be invoke. That way backwards
 compatibility remains, but you can now also do this:

 bin/instance run my.package.script.main

 What about using something like the EntryPoint syntax:

   $ bin/instance run my.package.script:main

 We could even add a new entry point class for it, and allow:

   $ bin/instance run egg:my.package#some_name

I've opted for a third alternative: use an entry point to define the 
extra commands. If you do this in setup.py:

entry_points=
   [zopectl.command]
   mycommand = mypackage.commands:func
   

you can do:

 $ bin/instance mycommand [args]

The advantage of this approach is that it makes for more user friendly 
commands that do not needlessly expose implementation details to the
commandline.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Extending Zope2 bin/instance run

2010-09-05 Thread Wichert Akkerman
On 2010-9-4 00:43, Chris Withers wrote:
 On 03/09/2010 17:21, Tres Seaver wrote:
 I am not sure if this is best done in plone.recipe.zope2instance or
 Zope2.Startup.zopectl. They have differing versions of ZopeCmd. Perhaps
 the plone.recipe.zope2instance code should be merged into Zope2's
 original as well?

 I don't know anything about the code in plone.recipe.zope2instance.

 Yes, and please remember that Plone is not the only consumer of Zope 2,
 and neither is plone.recipe.zope2instance the only way to deploy Zope...

there is absolutely nothing Plone-specific about plone, and people are 
using it for non-Plone systems as well.

Wichert.

-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Extending Zope2 bin/instance run

2010-09-05 Thread Wichert Akkerman
On 2010-9-5 16:03, Wichert Akkerman wrote:
 On 2010-9-4 00:43, Chris Withers wrote:
 On 03/09/2010 17:21, Tres Seaver wrote:
 I am not sure if this is best done in plone.recipe.zope2instance or
 Zope2.Startup.zopectl. They have differing versions of ZopeCmd. Perhaps
 the plone.recipe.zope2instance code should be merged into Zope2's
 original as well?

 I don't know anything about the code in plone.recipe.zope2instance.

 Yes, and please remember that Plone is not the only consumer of Zope 2,
 and neither is plone.recipe.zope2instance the only way to deploy Zope...

 there is absolutely nothing Plone-specific about plone, and people are
 using it for non-Plone systems as well.

.. about plone.recipe.zope2instance that is. Obviously Plone itself is 
quite Plone-specific :)

Wichert.


-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Extending Zope2 bin/instance run

2010-09-03 Thread Wichert Akkerman
I have noticed that now that we are almost exclusively using eggs to 
distribute our software using bin/instance run has become difficult: 
often the script you want to run is located inside an egg which makes to 
path to it hard to predict. This is not the most user friendly command:

   bin/instance run eggs/my.package-*/my/package/script.py

If a user is using a shared egg directory from zc.buildout or something 
else the egg can be anywhere on the filesystem, making it next to 
impossible to explain to users.

I am considering to modify bin/instance run to check if its first 
argument is a filesystem path, and if not consider the argument to be a 
dotted name of a callable which should be invoke. That way backwards 
compatibility remains, but you can now also do this:

   bin/instance run my.package.script.main

I am not sure if this is best done in plone.recipe.zope2instance or 
Zope2.Startup.zopectl. They have differing versions of ZopeCmd. Perhaps 
the plone.recipe.zope2instance code should be merged into Zope2's 
original as well?

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Extending Zope2 bin/instance run

2010-09-03 Thread Wichert Akkerman
On 9/3/10 10:27 , Hanno Schlichting wrote:
 On Fri, Sep 3, 2010 at 9:50 AM, Wichert Akkermanwich...@wiggy.net  wrote:
 I have noticed that now that we are almost exclusively using eggs to
 distribute our software using bin/instance run has become difficult: often
 the script you want to run is located inside an egg which makes to path to
 it hard to predict. This is not the most user friendly command:

   bin/instance run eggs/my.package-*/my/package/script.py

 You could also expose your script as a console_script and thus get it into 
 bin/.

But then I'ld have to figure out where the zope2.conf is and run all the 
undocumented Zope startup magic, all of which bin/instance gets for free.

 I am considering to modify bin/instance run to check if its first argument
 is a filesystem path, and if not consider the argument to be a dotted name
 of a callable which should be invoke. That way backwards compatibility
 remains, but you can now also do this:

   bin/instance run my.package.script.main

 I don't see any reason why we shouldn't do this.

Ok.

 I am not sure if this is best done in plone.recipe.zope2instance or
 Zope2.Startup.zopectl. They have differing versions of ZopeCmd. Perhaps the
 plone.recipe.zope2instance code should be merged into Zope2's original as
 well?

 The code in the zope2instance recipe has diverged both in
 implementation and semantics from the original Zope2 code. I tried to
 push back some of that in 2.11 while porting the Windows service
 support code over. But there's again a lot of other changes.

 Given that this code is completely untested except for people actually
 using it on different platforms I'm not personally going to merge the
 codebase any further. But anyone else is free to do so given they test
 the modified code under all supported platforms and especially
 Windows.

I can't test under Windows, so how can we proceed to make any changes at 
all there?

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Developer meeting today at 15:00 UTC

2010-08-31 Thread Wichert Akkerman
On 8/31/10 10:32 , Hanno Schlichting wrote:
 Hi.

 On Tue, Aug 31, 2010 at 10:23 AM, Christian Theunec...@gocept.com  wrote:
 our weekly meeting is coming up today at 15:00 UTC.

 I won't make it to todays meeting, so some notes upfront.

 - Supporting Python 2.7

 I thought the current plan is to try to support Python 2.7 for ZTK 1.1
 (which will then be Python 2.5 - 2.7). Currently 1.0 beta is still
 blocked on test issues. Before we don't get these tests fixed, there
 is no point in branching off the ZTK trunk to a 1.0 branch and
 allowing feature development to happen. If we cannot get the tests
 fixed on the current list of supported systems, adding whole new ZTK
 version set will only make matters much worse.

It does bring up an interesting question: if not all supported systems 
can be supported, should support for some systems be dropped?

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] RFC: ETag support for zope.browserresource

2010-08-11 Thread Wichert Akkerman
On 2010-8-11 18:00, Marius Gedminas wrote:
 On Tue, Aug 10, 2010 at 11:54:21PM +0300, Marius Gedminas wrote:
 Option #3:

IResourceETag(request).computeETag(path, timestamp, data)

 Feels a bit ad-hoc.

 The more I think about this, the more I think it's best to configure
 etag policy by providing an adapter on the request.

I would suggest request and context, so it is more generally useful. I 
suspect plone.caching already has such an adapter.

Wichert.

-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] docs.zope.org

2010-08-04 Thread Wichert Akkerman
On 8/4/10 17:38 , Jens Vagelpohl wrote:
 IMHO trying to come up with some kind of programmatic algorithm to judge
 a bit of documentation as good enough to show is insane. I'm  not
 going to attempt it.

Fair enough.

 Maybe shitty (for some definition of shitty, as someone else would
 say) package docs will compel the maintainers to improve them.

I doubt it, considering the exposure of shitty docs on pypi does not 
seem to have had any impact (aside from scaring away potential users).

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] docs.zope.org automation

2010-08-02 Thread Wichert Akkerman
On 8/2/10 13:40 , Martijn Faassen wrote:
 On 07/31/2010 07:22 PM, Jens Vagelpohl wrote:

 Here's a followup on a docs.zope.org automation task I took over during
 one of the Zope developer IRC metings[1]. The task was to provide
 individual package documentation, if it exists, directly underneath
 docs.zope.org, e.g.:

 http://docs.zope.org/zope.event/

 Really cool!

 Wouldn't it be good to put this under /package/zope.event to avoid
 potential naming conflicts? I realize they're rare, but I can imagine
 that a project foo could exist that wants to expose its documentation
 separately from project foo. Perhaps Zope would be a good example. :)

Perhaps we should encourage people to upload documentation to 
packages.python.org ?

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] docs.zope.org automation

2010-08-02 Thread Wichert Akkerman
On 8/2/10 16:46 , Martin Aspeli wrote:
 On 2 August 2010 22:40, Jens Vagelpohlj...@dataflake.org  wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 8/2/10 16:36 , Stephan Richter wrote:
 On Monday, August 02, 2010, Jens Vagelpohl wrote:
 'll have to look at that. Currently, the documentation builder does not
 do any introspection on the package itself, mostly because I do not want
 to fully install the package and pull in all dependencies. Maybe there's
 a simple way that does not require full installation.

 I agree. This does not build the package:

 python setup.py --long-description

 Thanks for the hint, I'll try that. Can you give me a sample package
 where the long description is supposed to be the main documentation? And
 what's the output from that? If it's ReST I'd have to find a way to
 convert it to HTML on the fly...sigh

 z3c.form, I'd guess. :)

Doesn't z3c.form have sphinx documentation?

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Class advisors in Python 3

2010-07-30 Thread Wichert Akkerman
On 7/30/10 13:31 , Baiju M wrote:
 Hi,

 Does class advisors like 'implements' and 'adapts' are going to work
 in Python 3 ? If not, should we discourage its usage now ?

Regardless if they work or not I would love to have a decorator version 
of them.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] chinese text and zope.index

2010-07-26 Thread Wichert Akkerman
On 7/26/10 14:52 , Manabu TERADA wrote:
 Hi

 I think zope.index will not work for indexing simplified or traditional
 Chinese.  That is my observation of zope.index when I was working on
 Plone4 CJK indexing.  However by looking at SVN record of zope.indexing,
 I see some changes.  It could be working on Chinese, now.

I'm afraid it doesn't work at all.

 I feel that zope.index should be fixed to work on CJK as well.
 However, I have not get at it.  When will be the due date for the new
 zope.index which works CJK indexing. (It should not that hard to fix it.)

I'ld like to have it working today if at all possible :). I have no idea 
how to go about fixing it though.

 PS:
 I don't think it is good idea to use CJKSplitter on a new project.  None
 is maintaining CJKSplitter any more.  Moreover, CJKSplitter will not
 work on Japanese, and some problem on indexing English.

I looked at cjktools as well, but could not find a splitter in there. 
That might be due to my lack of understanding of CJK languages though.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] chinese text and zope.index

2010-07-25 Thread Wichert Akkerman
Does anyone have the text index from zope.index working for simplified 
or traditional Chinese? The default pipeline is ships with effectively 
makes sure I never get a search result. I tried to drop the splitter 
from http://www.zope.org/Members/panjunyong/CJKSplitter in. This worked 
a bit better in that I got search results, but there seems to be little 
relation between my query and the result.

Wichert.

-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Help review #181754

2010-07-21 Thread Wichert Akkerman
On 2010-7-21 07:32, Wolfgang Schnerring wrote:
 * Wichert Akkermanwich...@wiggy.net  [2010-07-20 19:28]:
 On 2010-7-20 18:15, Christian Theune wrote:
 At least, WRT this bug, I don't think it's a good idea to ask explicitly
 for bad requests to go to the application as the test layer should model
 real server behaviour as closely as possible. And again it wouldn't make
 sense anyway as you can't pass an unparsable request to the application.

 I'm not sure I agree. Like everything else servers have bugs, so it
 can't hurt to test how your application would behave given certain
 server bugs.

 I don't think it is usually a productive assumption that lower layers
 fail to uphold their end of the contract. Maybe an
 extrapolation/hyperbole illustrates my opinion: Cosmic rays might also
 flip bits in your computer's RAM or disk, but I don't think it's
 worthwile to test how your application reacts when the python
 interpreter (or whoever, really) presents it with mangled data
 structures or objects or whatnot.

And for some situations you do want to explicitly test for such things. 
It all depends on how critical your app is. I'm not sure I'm not the 
only one who has tested code with randomly broken/bit-flipped input to 
test robustness.

Wichert.

-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Help review #181754

2010-07-20 Thread Wichert Akkerman
On 2010-7-20 17:39, Christian Theune wrote:
 Hi,

 I just rejected issue
 https://bugs.edge.launchpad.net/zope.app.testing/+bug/181754

 There might be room for different oppinions and if anyone would like to
 veto the decision, I'd welcome a discussion.

Your rejection contains an assumption that the request won't make it to 
the application. Is that assumption testable?

Wichert.


-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Help review #181754

2010-07-20 Thread Wichert Akkerman
On 2010-7-20 18:15, Christian Theune wrote:
 At least, WRT this bug, I don't think it's a good idea to ask explicitly
 for bad requests to go to the application as the test layer should model
 real server behaviour as closely as possible. And again it wouldn't make
 sense anyway as you can't pass an unparsable request to the application.

I'm not sure I agree. Like everything else servers have bugs, so it 
can't hurt to test how your application would behave given certain 
server bugs.

Wichert.


-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] ZEO TempStorage: Odd behavior on ZEO restart

2010-07-15 Thread Wichert Akkerman
On 7/15/10 17:03 , Dragos Chirila wrote:
 Hi Sebastian,

 Why don’t you consider to use memcached for caching the results instead
 of using sessions? By using this, Zeo server/Zeo clients restart wont
 affect cached data.

or plone.memoize, using either a RAMCache or memcached as backend.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] [Checkins] SVN: Zope/branches/2.12/ - LP #143533: Instead of showing 0.0.0.0 as server name when no

2010-07-14 Thread Wichert Akkerman
On 7/14/10 16:19 , Jens Vagelpohl wrote:
 Log message for revision 114741:
- LP #143533: Instead of showing 0.0.0.0 as server name when no
  specific listening IP is configured for the HTTP server, do a
  socket lookup to show the current server's fully qualified name.

Can I object to this change? I would much rather always see the IP 
address than just the hostname since that is a lot more information.  If 
we change this can we please make it show both IP and hostname?

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] [Checkins] SVN: Zope/branches/2.12/ - LP #143533: Instead of showing 0.0.0.0 as server name when no

2010-07-14 Thread Wichert Akkerman
On 7/14/10 16:43 , Jens Vagelpohl wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 7/14/10 16:28 , Wichert Akkerman wrote:
 On 7/14/10 16:19 , Jens Vagelpohl wrote:
 Log message for revision 114741:
 - LP #143533: Instead of showing 0.0.0.0 as server name when no
   specific listening IP is configured for the HTTP server, do a
   socket lookup to show the current server's fully qualified name.

 Can I object to this change? I would much rather always see the IP
 address than just the hostname since that is a lot more information.  If
 we change this can we please make it show both IP and hostname?

 Hi Wichert,

 The IP makes no sense, because 0.0.0.0 is strictly speaking correct as
 the IP value, since the process is listening on all interfaces. At that
 point we have no progress at all. 0.0.0.0 doesn't tell the viewer
 anything about what server it came from, either.

I don't mind doing this for a SERVER_NAME in the response, but looking 
at the diff from the commit email you also changed the startup message 
from Zope 2 with this change. That is the bit I find problematic: I want 
to be able to immediately see if the Zope instance is bound to a 
specific IP address or ANY/0.0.0.0.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] [Checkins] SVN: Zope/branches/2.12/ - LP #143533: Instead of showing 0.0.0.0 as server name when no

2010-07-14 Thread Wichert Akkerman
On 7/14/10 17:14 , Jens Vagelpohl wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 7/14/10 17:00 , Andreas Jung wrote:
 Wichert Akkerman wrote:

 I don't mind doing this for a SERVER_NAME in the response, but looking
 at the diff from the commit email you also changed the startup message
 from Zope 2 with this change. That is the bit I find problematic: I want
 to be able to immediately see if the Zope instance is bound to a
 specific IP address or ANY/0.0.0.0.

 +1

 http://svn.zope.org/?rev=114752view=rev

 http://svn.zope.org/?rev=114753view=rev

Thanks!

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Python 2.7 and the ZTK - three test failures

2010-07-06 Thread Wichert Akkerman
On 2010-7-5 23:08, Hanno Schlichting wrote:
 Hi there,

 with Python 2.7 final being released, I ran the ZTK tests against it.

 zope.exceptions, zope.formlib and zope.proxy all have one test output
 related failure.

We seem to have a lot of problems with doctests breaking due to changes 
in exception formatting. Perhaps a policy to check exceptions using a
try/except or self.assertRaises instead of relying on exact formatting 
would be useful?

Wichert.


-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope.i18messageid

2010-07-02 Thread Wichert Akkerman
On 2010-7-2 19:49, Tres Seaver wrote:
 The change here is to remove 'standard=True' from the feature
 constructor.  Developers who want the feature enabled can then build the
 egg via:

$ python setup.py --with-codeoptimization bdist_egg

 We could then update the zc.recipe.egg:custom recipe to allow specifying
 features to be installed for a given egg.

That would be a very welcome change for SQLAlchemy as well: it has an 
optional C extension to speed of marshalling data from SQL responses.

Wichert.

-- 
Wichert Akkerman wich...@wiggy.net   It is simple to make things.
http://www.wiggy.net/  It is hard to make things simple.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope.sendmail and critical transaction errors.

2010-06-24 Thread Wichert Akkerman
On 6/24/10 09:46 , Jens Vagelpohl wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 6/24/10 09:30 , Chris Withers wrote:
 Tres Seaver wrote:
 The misconfiguration of the mail host in transactional mode *does* cause
 the server to go into a lockdown mode (because errors are not supposed
 to be raised in 'tpc_finish').  There is *no* database corruption, but
 the transaction manager can't know that, and so it deliberately refuses
 to commit more transactions until the admin un-futzes the problem (in
 this case, by fixing the mailhost configuration) and restarts the server.

 Yeah, what he said...

 It's not as easy as that, though. Mailhost misconfiguration is just one
 reason why errors may be raised during the actual sending. The receiver
 address may be wrong, which is where I tend to see it. This is not a
 condition I could reasonably test for in my code before attempting to
 send though the MailHost.

What might be interesting is a MailHost for non-bulk mail sending which 
does the SMTP HELO/MAIL FROM/RCPT TO bits immediately and only delays 
the DATA command until transaction commit time. That will allow you to 
detect almost all SMTP configuration problems and address errors in your 
code while still getting transaction support.

Personally I've updated all my code to sending mail directly and not 
using zope.sendmail. Being able to catch and handle errors is much more 
useful to me than preventing extremely rare duplicate emails.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] z3c.form release

2010-05-17 Thread Wichert Akkerman
On 5/15/10 09:59 , Martin Aspeli wrote:


 On 15 May 2010 15:39, Wichert Akkerman wich...@wiggy.net
 mailto:wich...@wiggy.net wrote:

 On 5/10/10 17:24 , Wichert Akkerman wrote:
   I fixed a few issues in z3c.form today. Can anyone make a 2.3.4
 release?


 Since I got no reaction I'll repeat this request: can someone please
 make a new z3c.form release? Looking at the pypi page there is no
 shortage of people with the ability to do so..


 And now you're one of those people. ;-)'

Thanks, I've kicked out 2.3.4.

Can you update whatever bit on good-py pins z3c.form to 2.3.3 to 2.3.4? 
I couldn't find where that was coming in from.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] z3c.form release

2010-05-17 Thread Wichert Akkerman
On 5/17/10 15:14 , Gediminas Paulauskas wrote:
 2010/5/17 Wichert Akkermanwich...@wiggy.net:
 On 5/15/10 09:59 , Martin Aspeli wrote:


 On 15 May 2010 15:39, Wichert Akkermanwich...@wiggy.net
 mailto:wich...@wiggy.net  wrote:

  On 5/10/10 17:24 , Wichert Akkerman wrote:
 I fixed a few issues in z3c.form today. Can anyone make a 2.3.4
  release?


  Since I got no reaction I'll repeat this request: can someone please
  make a new z3c.form release? Looking at the pypi page there is no
  shortage of people with the ability to do so..


 And now you're one of those people. ;-)'

 Thanks, I've kicked out 2.3.4.

 Not sure how the http://pypi.python.org/pypi/z3c.form page looked
 before, but for some reason not only it is not rendered as ReST
 content, but is double-escaped (i.e. full of gt; strings) as well.

It was like that before as well, no idea why. Can you submit a ticket to 
the z3c.form tracker on Launchpad?

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] z3c.form issue tracker

2010-05-15 Thread Wichert Akkerman
On 5/10/10 20:16 , Tres Seaver wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Wichert Akkerman wrote:
 Where should bugreports for z3c.form be submitted? Its documentation
 does not list an issue tracker, and there is no z3c.form project on
 launchpad.

 I just created one:

   https://bugs.launchpad.net/z3c.form

Thanks!

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] z3c.form release

2010-05-15 Thread Wichert Akkerman
On 5/10/10 17:24 , Wichert Akkerman wrote:
 I fixed a few issues in z3c.form today. Can anyone make a 2.3.4 release?


Since I got no reaction I'll repeat this request: can someone please 
make a new z3c.form release? Looking at the pypi page there is no 
shortage of people with the ability to do so..

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] z3c.form issue tracker

2010-05-10 Thread Wichert Akkerman
Where should bugreports for z3c.form be submitted? Its documentation 
does not list an issue tracker, and there is no z3c.form project on 
launchpad.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] z3c.form release

2010-05-10 Thread Wichert Akkerman
I fixed a few issues in z3c.form today. Can anyone make a 2.3.4 release?

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Hanno, please update the ZTK

2010-05-03 Thread Wichert Akkerman
On 5/3/10 12:20 , Martijn Faassen wrote:
 Hanno Schlichting wrote:
 Good evening :)

 If you have a specific issue with me, you might contact me in private.
 But with your follow-ups this turned into a more general issue.

 No, I think this needs to be public as the ZTK is a public project that
 I care about. And you're not playing your proper part in it. You're not
 going to listen to me (otherwise the fork would never have happened; you
 had an issue with listening to me), so I'm informing the rest of the
 community. Maybe you'll listen to them. The fork is counterproductive.
 And it's just annoying me. It's time for this annoyance to disappear.

Can we please not rehash an old discussion or make this personal? This 
has all been discussed too often already.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Hanno, please update the ZTK

2010-05-03 Thread Wichert Akkerman
On 5/3/10 12:34 , Martijn Faassen wrote:
 Hi there,

 Hanno Schlichting wrote:
 I expect us to define the process around package releases and updating
 the ZTK. It's not entirely clear to me who should and who is allowed
 to update the ZTK definition. We'll figure things out and once we have
 I'll stick to the rules.

 My few cents:

 I think everybody should be allowed to update the ZTK definition. They
 should follow certain guidelines (run tests, and such. Maybe updating a
 changelog is a good idea too). Stability can be taken care of by
 branching and tagging. I.e. the same guidelines as we have for other
 pieces of code can be a good starting point.

 To get back to the discussion that caused the fork. We have implicit,
 but I think widely understood and accepted, rules about backwards
 compatibility. So we don't expect someone to rip out half the code of a
 Python package just like that. Generally we expect the tests to continue
 to run. Similarly we shouldn't just drop things from the ZTK without
 special action (this involves removing tests too!). We started to try to
 spell some of that out here long ago:

 http://docs.zope.org/zopetoolkit/about/coreextra.html

 But I'd hate it if the ZTK trunk became some kind of bureaucratic maze,
 as it'd stop me from getting work done.

I suggest that we wait impatiently for the ZTK steering committee to 
come up with a useful policy instead of trying to do their work when 
none of us volunteered for the task.

Wichert.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Hanno, please update the ZTK

2010-05-03 Thread Wichert Akkerman
On 5/3/10 12:52 , Martijn Faassen wrote:
 Wichert Akkerman wrote:
 I suggest that we wait impatiently for the ZTK steering committee to
 come up with a useful policy instead of trying to do their work when
 none of us volunteered for the task.

 I don't understand your suggestion. Could you rephrase it?

 I'm a ZTK user, and I'm dissatisfied. I'm complaining. What's more, I'm
 actually offering constructive suggestions. Are you?

A ZTK steering group was created to help define and manage the ZTK. You 
did not volunteer for that, and neither did I. Hanno did, so why not let 
him do his job instead of distracting him by rehashing a discussion that 
already happened on this list.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Hanno, please update the ZTK

2010-05-03 Thread Wichert Akkerman
On 5/3/10 13:07 , Martijn Faassen wrote:
 Wichert Akkerman wrote:
 On 5/3/10 12:51 , Martijn Faassen wrote:
 Wichert Akkerman wrote:
 Can we please not rehash an old discussion or make this personal? This
 has all been discussed too often already.
 As far as I know, I've *never* discussed this fork on this list, but I
 might be wrong; feel free to dig the archives. But that doesn't matter:
 the fork is still there. So: wtf, Wichert?

 Perhaps you haven't, but others have discussed the reason the fork was
 cerated and why it still exists. Since then many things have happened
 including the creation of the ZTK steering group, of which Hanno is a
 member.

 The ZTK steering group was created about a year ago, so I'm not sure
 what you're trying to suggest here.

Sorry, my mistake. I meant the ZTK release manage group, not the now 
defunct ZTK steering group,

 I must say it totally baffles me that the ZTK was acceptable to Zope 2
 until january, and became unacceptable at that point. All answers are
 probably in that mailing list thread, but I can't be bothered to look it
 up. Please just make the fork go away.

The needed steps to do that can be found in the list archives.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Hanno, please update the ZTK

2010-05-03 Thread Wichert Akkerman
On 5/3/10 15:41 , Martijn Faassen wrote:
 Lennart Regebro wrote:
 On Mon, May 3, 2010 at 13:22, Martijn Faassenfaas...@startifact.com  wrote:
 Wichert Akkerman wrote:
 Sorry, my mistake. I meant the ZTK release manage group, not the now
 defunct ZTK steering group,

 Well, if it's defunct or not is up to the members of the steering
 group. The steering group created itself, and may disband itself if it
 so wishes. It has all the right in the world to continue existing,
 even if the idea is that the ZTK oversight will be done by the release
 manager team instead.

 If it's defunct someone better update the documentation.

 The creation of the release manager team was only recently concluded.

 Two weeks ago. Process started a month ago.

If we're going to make cheap shots: that's still a lot faster than the 
grok release cycle.

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope.test.doctest made into monkey-patches (Was: Circular dependency hell.)

2010-04-20 Thread Wichert Akkerman
On 4/20/10 13:37 , Stephan Richter wrote:
 On Tuesday 20 April 2010, Lennart Regebro wrote:
 It replaces the custom doctest.py with monkey-patches.
 I will report these to the Python bugtracker as well, although I have
 no hope of getting them into Python 2.7. But that doesn't matter much.

 :)

 Fantastic. I really hate the improper counting of the Python version. :-)

 BTW, I also like your splitting of the test runner and the testing
 infrastructure. The zope.testing testrunner is really good and deserves its
 own life. I hope that more people will pick it up.

You may want to move it outside the zope.* namespace to encourage that :)

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Unauthorized handling in Zope2

2010-04-20 Thread Wichert Akkerman
On 4/20/10 09:51 , yuppie wrote:
 Hi!


 Wichert Akkerman wrote:
 v is the html as generated by my view. Reraising the exception transfers
 control to the bare except in
 ZPublisher.Publish.publish_module_standard, which generates the standard
 site error page and returns that.

 Could it be that your v is unicode?

Indeed it is: Chameleon returns a unicode response it seems.

 Please let me know if the attached patch fixes the issue.

I'm afraid it doesn't. The result is this:

   Site Error

   An error was encountered while publishing this resource.

   Unauthorized

   Sorry, a site error occurred.
   Traceback (innermost last):

   Module ZPublisher.Publish, line 238, in publish_module_standard
   Module Products.PDBDebugMode.runcall, line 83, in pdb_publish
   Module ZPublisher.Publish, line 165, in publish
   Module plone.app.linkintegrity.monkey, line 21, in 
zpublisher_exception_hook_wrapper
   Module ZPublisher.Publish, line 116, in publish
   Module ZPublisher.BaseRequest, line 609, in traverse
   Module ZPublisher.HTTPResponse, line 720, in unauthorized
   Unauthorized: unprintable Unauthorized object

Wichert.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


  1   2   3   4   >