Garbage-collecting memcache.Client instance does that automatically.

Docstrings are not to annotate what code is doing.

Concurrency handling is not required, because a single MemcachedDict should
not be accessed outside a Zope transaction, which is itself bound to a
specific thread.
Pickling a connection is not needed, ERP5Type.Core.MemcachedPlugin is all
we need to serialise.

Simplifies code creating a new connection.

Doc's mention about expiration time is precisely that server's code is
supposed to do just that internally.

See commit 4718f5e1

A ZopeLite patch was added to prevent loading of zcml files, which is wrong
for ERP5: CMF products were not properly initialized.

Code is also simpler now that we call OFS.Application.initialize(), which is
not significantly slower.

We keep patch not to register help though because this is quite expensive:
we should even consider always disable help because they seems to cause many
conflicts during Zope cluster startup.

A monkey-patch to unittest is updated for Python 2.7, so that tests aren't run
when they shouldn't (e.g. --save without --load).

app() creates a new transactional connection to ZODB, which triggers
scary (although innocuous in this case) connection pool warnings.
Instead, use getSite provided in ERP5 product and filled when
traversing site's portal. Retrieved acl_users object is different, but
this should not matter.
Also, to prevent import loop and to keep this change minimal, do a
local import.

line breaks are too special and generates weird layout (like when adjust is used)

the bt5 erp5_odt_style is required, because the script Base_getODTStyleSheet is used by test_include_img

add expectedFailure to be fixed later. The libreoffice version should be checked because in some case, the test is passing