plone/plone.api — Issue #15: `strict=True` and its `KeyError`
Author: dnouri
Created: 2012-02-27 16:41:57+00:00
State: open

I think `strict=True` is a poor choice of name in the context of `create` and `move`. I initially thought it was to check security. Anyway I have the feeling it may mean a number of things to different people.

Also, `KeyError` is a poor choice to denote that an ID was already taken. The stack behind a call to `api.create` or `api.move` is huge, and `KeyError` very common. Thus, you'll end up with `KeyError`s that do not mean "ID already taken".