File "product/TimerService/timerserver/TimerServer.py", line 71, in run
    s.send('GET / HTTP/1.1\r\n\r\n')
TypeError: a bytes-like object is required, not 'str'

py3: No more im_class attribute in Python3. API change but Interactor not used/recommended anymore (ERP5 object)...

And _mysql/mysqldb API (_mysql.connection.query()) converts the query string to
bytes() (additionally, cursor.execute(QUERY, ARGS) calls query() after
converting everything to bytes() too).

python-modernize -w -f dict_six product/

The implements syntax used under Python 2.X does not work under 3.X, since it
depends on how metaclasses are implemented and this has changed. Instead it
now supports a decorator syntax (also under Python 2.X).

Applied thanks to 2to3 `zope.fixers` package.

And Zope4 now mandates it to be a string ({Shared.DC.ZRDB.TM.TM,ITransactionManager}.sortKey()).

Stricter than six.ensure_{text,str}().

Standard library was reorganized (urlparse => urllib, httplib => http...) in PEP
3108. install_aliases() from `future` egg provides module aliases so that
imports work on both python2 and python3.

This will allow to propagate the CSP configuration on officejs.com

Only ZEXP Export/Import is possible. These modules (namely OFS.XMLExportImport
and Shared.DC.xml.*) were heavily monkey-patched anyway and are only used for
BusinessTemplates.

* ERP5Type/XMLExportImport.py  => ERP5Type/XMLExportImport/__init__.py
* OFS/XMLExportImport.py       => ERP5Type/XMLExportImport/__init__.py
* Shared/DC/xml/{xyap,ppml}.py => ERP5Type/XMLExportImport/{xyap,ppml}.py

See merge request !1589

Instead of doing what loading zope.conf does (which is different
across zope versions), use the ZConfig configuration callback.

The old name was Zuite_viewZeleniumTestLauncher which is an violation
to erp5-Guideline.Form.Report.Dialog.Is.Postfixed.With.Dialog

ErrorLog is not allowed prefix, this was flagged by coding style test,
since the script is not used it's better to remove it

We were installing erp5_upgrader with its test dependencies, so it was
installing erp5_full_text_mroonga_catalog. We were also installing
erp5_full_text_myisam_catalog, so we ended up with two full text
business template installed (and the order of this installation was not
deterministic).
This was problematic, because we were installing all the test dependencies
of erp5_upgrader, but we don't really need them here and one goal of
CodingStyleTest is to install only the dependencies of tested business
templates, as a way to verify that dependencies are correctly specified.

This new approach hooks at another level, to install a full text business
template only if the tested business template has a dependency to the
virutal "erp5_full_text_catalog" bt, but no dependency to a concrete bt
(which happens for example in erp5_base) and to install erp5_upgrader
without its test dependencies.

As a result, we also run without erp5_base unless it's an explicit
dependency.

This also reverts commit ab44309f (
full_text_myisam_catalog: skip coding style test) that is no longer
needed with this new approach.

Some other documents from erp5_core import RoundingModel, all this can
not be in erp5_base