Merge branch 'master' of git.labocleo.org:lodel2

Conflicts:
	examples/em_test.pickle
	plugins/webui/run.py

AUTHORS

@@ -0,0 +1,5 @@
+Arnaud Corider
+Roland Haroutiounian
+Mathieu Orban
+Hélène Prieto
+Yann Weber

COPYING

@@ -0,0 +1,674 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<http://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<http://www.gnu.org/philosophy/why-not-lgpl.html>.

Doxyfile

@@ -824,7 +824,12 @@ FILE_PATTERNS          = *.c \
                          *.ucf \
                          *.qsf \
                          *.as \
-                         *.js
+                         *.js \
+			 *.m4 \
+			 *.patch \
+			 *.ac \
+			 *.am \
+			 *.in
 
 # The RECURSIVE tag can be used to specify whether or not subdirectories should
 # be searched for input files as well.

INSTALL

@@ -0,0 +1,370 @@
+Installation Instructions
+*************************
+
+Copyright (C) 1994-1996, 1999-2002, 2004-2013 Free Software Foundation,
+Inc.
+
+   Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved.  This file is offered as-is,
+without warranty of any kind.
+
+Basic Installation
+==================
+
+   Briefly, the shell command `./configure && make && make install'
+should configure, build, and install this package.  The following
+more-detailed instructions are generic; see the `README' file for
+instructions specific to this package.  Some packages provide this
+`INSTALL' file but do not implement all of the features documented
+below.  The lack of an optional feature in a given package is not
+necessarily a bug.  More recommendations for GNU packages can be found
+in *note Makefile Conventions: (standards)Makefile Conventions.
+
+   The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation.  It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions.  Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+   It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring.  Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.
+
+   If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release.  If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+   The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'.  You need `configure.ac' if
+you want to change it or regenerate `configure' using a newer version
+of `autoconf'.
+
+   The simplest way to compile this package is:
+
+  1. `cd' to the directory containing the package's source code and type
+     `./configure' to configure the package for your system.
+
+     Running `configure' might take a while.  While running, it prints
+     some messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package, generally using the just-built uninstalled binaries.
+
+  4. Type `make install' to install the programs and any data files and
+     documentation.  When installing into a prefix owned by root, it is
+     recommended that the package be configured and built as a regular
+     user, and only the `make install' phase executed with root
+     privileges.
+
+  5. Optionally, type `make installcheck' to repeat any self-tests, but
+     this time using the binaries in their final installed location.
+     This target does not install anything.  Running this target as a
+     regular user, particularly if the prior `make install' required
+     root privileges, verifies that the installation completed
+     correctly.
+
+  6. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.  There is
+     also a `make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get
+     all sorts of other programs in order to regenerate files that came
+     with the distribution.
+
+  7. Often, you can also type `make uninstall' to remove the installed
+     files again.  In practice, not all packages have tested that
+     uninstallation works correctly, even though it is required by the
+     GNU Coding Standards.
+
+  8. Some packages, particularly those that use Automake, provide `make
+     distcheck', which can by used by developers to test that all other
+     targets like `make install' and `make uninstall' work correctly.
+     This target is generally not run by end users.
+
+Compilers and Options
+=====================
+
+   Some systems require unusual options for compilation or linking that
+the `configure' script does not know about.  Run `./configure --help'
+for details on some of the pertinent environment variables.
+
+   You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment.  Here
+is an example:
+
+     ./configure CC=c99 CFLAGS=-g LIBS=-lposix
+
+   *Note Defining Variables::, for more details.
+
+Compiling For Multiple Architectures
+====================================
+
+   You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory.  To do this, you can use GNU `make'.  `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script.  `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.  This
+is known as a "VPATH" build.
+
+   With a non-GNU `make', it is safer to compile the package for one
+architecture at a time in the source code directory.  After you have
+installed the package for one architecture, use `make distclean' before
+reconfiguring for another architecture.
+
+   On MacOS X 10.5 and later systems, you can create libraries and
+executables that work on multiple system types--known as "fat" or
+"universal" binaries--by specifying multiple `-arch' options to the
+compiler but only a single `-arch' option to the preprocessor.  Like
+this:
+
+     ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+                 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+                 CPP="gcc -E" CXXCPP="g++ -E"
+
+   This is not guaranteed to produce working output in all cases, you
+may have to build one architecture at a time and combine the results
+using the `lipo' tool if you have problems.
+
+Installation Names
+==================
+
+   By default, `make install' installs the package's commands under
+`/usr/local/bin', include files under `/usr/local/include', etc.  You
+can specify an installation prefix other than `/usr/local' by giving
+`configure' the option `--prefix=PREFIX', where PREFIX must be an
+absolute file name.
+
+   You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files.  If you
+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
+PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files still use the regular prefix.
+
+   In addition, if you use an unusual directory layout you can give
+options like `--bindir=DIR' to specify different values for particular
+kinds of files.  Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.  In general, the
+default for these options is expressed in terms of `${prefix}', so that
+specifying just `--prefix' will affect all of the other directory
+specifications that were not explicitly provided.
+
+   The most portable way to affect installation locations is to pass the
+correct locations to `configure'; however, many packages provide one or
+both of the following shortcuts of passing variable assignments to the
+`make install' command line to change installation locations without
+having to reconfigure or recompile.
+
+   The first method involves providing an override variable for each
+affected directory.  For example, `make install
+prefix=/alternate/directory' will choose an alternate location for all
+directory configuration variables that were expressed in terms of
+`${prefix}'.  Any directories that were specified during `configure',
+but not in terms of `${prefix}', must each be overridden at install
+time for the entire installation to be relocated.  The approach of
+makefile variable overrides for each directory variable is required by
+the GNU Coding Standards, and ideally causes no recompilation.
+However, some platforms have known limitations with the semantics of
+shared libraries that end up requiring recompilation when using this
+method, particularly noticeable in packages that use GNU Libtool.
+
+   The second method involves providing the `DESTDIR' variable.  For
+example, `make install DESTDIR=/alternate/directory' will prepend
+`/alternate/directory' before all installation names.  The approach of
+`DESTDIR' overrides is not required by the GNU Coding Standards, and
+does not work on platforms that have drive letters.  On the other hand,
+it does better at avoiding recompilation issues, and works well even
+when some directory options were not specified in terms of `${prefix}'
+at `configure' time.
+
+Optional Features
+=================
+
+   If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+   Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System).  The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+   For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+   Some packages offer the ability to configure how verbose the
+execution of `make' will be.  For these packages, running `./configure
+--enable-silent-rules' sets the default to minimal output, which can be
+overridden with `make V=1'; while running `./configure
+--disable-silent-rules' sets the default to verbose, which can be
+overridden with `make V=0'.
+
+Particular systems
+==================
+
+   On HP-UX, the default C compiler is not ANSI C compatible.  If GNU
+CC is not installed, it is recommended to use the following options in
+order to use an ANSI C compiler:
+
+     ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
+
+and if that doesn't work, install pre-built binaries of GCC for HP-UX.
+
+   HP-UX `make' updates targets which have the same time stamps as
+their prerequisites, which makes it generally unusable when shipped
+generated files such as `configure' are involved.  Use GNU `make'
+instead.
+
+   On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
+parse its `<wchar.h>' header file.  The option `-nodtk' can be used as
+a workaround.  If GNU CC is not installed, it is therefore recommended
+to try
+
+     ./configure CC="cc"
+
+and if that doesn't work, try
+
+     ./configure CC="cc -nodtk"
+
+   On Solaris, don't put `/usr/ucb' early in your `PATH'.  This
+directory contains several dysfunctional programs; working variants of
+these programs are available in `/usr/bin'.  So, if you need `/usr/ucb'
+in your `PATH', put it _after_ `/usr/bin'.
+
+   On Haiku, software installed for all users goes in `/boot/common',
+not `/usr/local'.  It is recommended to use the following options:
+
+     ./configure --prefix=/boot/common
+
+Specifying the System Type
+==========================
+
+   There may be some features `configure' cannot figure out
+automatically, but needs to determine by the type of machine the package
+will run on.  Usually, assuming the package is built to be run on the
+_same_ architectures, `configure' can figure that out, but if it prints
+a message saying it cannot guess the machine type, give it the
+`--build=TYPE' option.  TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+
+     CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+     OS
+     KERNEL-OS
+
+   See the file `config.sub' for the possible values of each field.  If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+
+   If you are _building_ compiler tools for cross-compiling, you should
+use the option `--target=TYPE' to select the type of system they will
+produce code for.
+
+   If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+
+Sharing Defaults
+================
+
+   If you want to set default values for `configure' scripts to share,
+you can create a site shell script called `config.site' that gives
+default values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists.  Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Defining Variables
+==================
+
+   Variables not defined in a site shell script can be set in the
+environment passed to `configure'.  However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost.  In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'.  For example:
+
+     ./configure CC=/usr/local2/bin/gcc
+
+causes the specified `gcc' to be used as the C compiler (unless it is
+overridden in the site shell script).
+
+Unfortunately, this technique does not work for `CONFIG_SHELL' due to
+an Autoconf limitation.  Until the limitation is lifted, you can use
+this workaround:
+
+     CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash
+
+`configure' Invocation
+======================
+
+   `configure' recognizes the following options to control how it
+operates.
+
+`--help'
+`-h'
+     Print a summary of all of the options to `configure', and exit.
+
+`--help=short'
+`--help=recursive'
+     Print a summary of the options unique to this package's
+     `configure', and exit.  The `short' variant lists options used
+     only in the top level, while the `recursive' variant lists options
+     also present in any nested packages.
+
+`--version'
+`-V'
+     Print the version of Autoconf used to generate the `configure'
+     script, and exit.
+
+`--cache-file=FILE'
+     Enable the cache: use and save the results of the tests in FILE,
+     traditionally `config.cache'.  FILE defaults to `/dev/null' to
+     disable caching.
+
+`--config-cache'
+`-C'
+     Alias for `--cache-file=config.cache'.
+
+`--quiet'
+`--silent'
+`-q'
+     Do not print messages saying which checks are being made.  To
+     suppress all normal output, redirect it to `/dev/null' (any error
+     messages will still be shown).
+
+`--srcdir=DIR'
+     Look for the package's source code in directory DIR.  Usually
+     `configure' can determine that directory automatically.
+
+`--prefix=DIR'
+     Use DIR as the installation prefix.  *note Installation Names::
+     for more details, including other options available for fine-tuning
+     the installation locations.
+
+`--no-create'
+`-n'
+     Run the configure checks, but stop before creating any output
+     files.
+
+`configure' also accepts some other, not widely useful, options.  Run
+`configure --help' for more details.

Makefile

@@ -1,39 +0,0 @@
-python=python3
-dyncode_filename='lodel/leapi/dyncode.py'
-
-all: tests doc dyncode
-
-# generate doxygen documentation
-doc: cleandoc doc_graphviz
-	doxygen
-
-doc_graphviz:
-	cd doc/img/graphviz; make
-
-# Test em update ( examples/em_test.pickle )
-em_test:
-	$(python) em_test.py
-
-# generate leapi dynamic code
-dyncode: clean_dyn em_test
-	$(python) scripts/refreshdyn.py examples/em_test.pickle $(dyncode_filename) && echo -e "\n\nCode generated in $(dyncode_filename)"
-
-# run tests
-tests:
-	./runtest -v
-
-.PHONY: clean clean_dyn cleandoc cleanpyc tests
-
-clean: clean_dyn cleandoc cleanpyc
-
-cleanpyc:
-	-find ./ |grep -E "\.pyc$$" |xargs rm -f 2>/dev/null
-cleanpycache:
-	-find ./ -type d |grep '__pycache__' | xargs rmdir -f 2>/dev/null
-
-cleandoc:
-	-rm -R doc/html doc/doxygen_sqlite3.db
-
-clean_dyn:
-	-rm $(dyncode_filename)
-	

Makefile.am

@@ -0,0 +1,41 @@
+SUBDIRS=lodel
+
+#python=/usr/bin/env python3
+python=@PYTHON@
+dyncode_filename='lodel/leapi/dyncode.py'
+
+# Doxygen doc generation targets
+doc:
+	test -z "@DOCOK@" && echo -e "\n\nUnable to generate documentation. See ./configure output for details\n\n" >&2 || make generate-doc
+
+generate-doc: clean doc_graphviz
+	doxygen
+
+doc_graphviz:
+	cd doc/img/graphviz; make
+
+# Test em update ( examples/em_test.pickle )
+em_test: em_test.py
+	$(python) em_test.py
+
+# generate leapi dynamic code
+dyncode: examples/em_test.pickle
+	$(python) scripts/refreshdyn.py examples/em_test.pickle $(dyncode_filename) && echo -e "\n\nCode generated in $(dyncode_filename)"
+
+# run tests
+tests:
+	./runtest -v
+
+check: tests
+checks: tests
+
+#Cleaning documentation and dyncode
+clean-local: cleandoc
+	-rm -R doc/html doc/doxygen_sqlite3.db
+cleandoc:
+	-rm $(dyncode_filename)
+
+distclean-local:
+	-rm -R Makefile Makefile.in autom4te.cache/ aclocal.m4 install-sh missing py-compile configure
+
+.PHONY: cleandoc tests doc

README.txt → README

@@ -1,6 +1,15 @@
 Dependencies :
-	with pip : see requirements.txt
-	debian stable : python3 python3-lxml python3-jinja2 python3-werkzeug python3-pymongo uwsgi-plugin-python3 mongodbd
+	lodel2 :
+		with pip : see requirements.txt
+		debian stable : python3 python3-lxml python3-jinja2 python3-werkzeug python3-pymongo uwsgi-plugin-python3 mongodbd
+	build & install :
+		debian stable : autoconf automake make
+
+Build & install :
+	./bootstrap.sh
+	./configure
+	make
+	make install
 
 Doxygen documentation generation :
 	dependencies: doxypy doxygen graphviz

bootstrap.sh

@@ -0,0 +1,3 @@
+#!/bin/bash
+
+autoreconf -fvi

configure.ac

@@ -0,0 +1,86 @@
+AC_INIT([lodel], [0.1], [contact@openedition.org])
+
+AM_INIT_AUTOMAKE
+
+AC_CONFIG_FILES([Makefile \
+	lodel/buildconf.py \
+	lodel/Makefile \
+	lodel/auth/Makefile \
+	lodel/editorial_model/Makefile \
+		lodel/editorial_model/translator/Makefile \
+	lodel/leapi/Makefile \
+		lodel/leapi/datahandlers/Makefile \
+	lodel/plugin/Makefile \
+	lodel/settings/Makefile \
+	lodel/utils/Makefile \
+])
+
+
+###
+#Kind of dangerous mix between default aclocal's macro and pyconfigure macros...
+#
+#pyconfigure macros are prefixed by PC_
+###
+m4_include([m4/python.m4]) # Patched version of aclocal python.m4 file
+m4_include([m4/python_pyconfigure.m4]) #Renamed because we use a patched version of aclocal python.m4 file
+m4_define(python_min_ver, 3.4.2)
+
+AM_PATH_PYTHON([3.4.2]) #init aclocal's default python support
+PC_INIT([3.4.2], [3.5]) #init pyconfigure aclocal's macro
+
+PC_PYTHON_VERIFY_VERSION([>=], python_min_ver, ,
+	[AC_MSG_ERROR(Python interpreter too old)])
+
+AC_ARG_VAR([SITEPACKAGES], [If installed in /usr or /System* specify the name of the site directory (default value "site-packages"])
+
+PC_PYTHON_CHECK_MODULE([lxml], ,
+	AC_MSG_ERROR([Module lxml not found but mandatory for lodel2]))
+#Webui deps
+AC_SUBST([WEBUI], 'True')
+PC_PYTHON_CHECK_MODULE_VERSION([jinja2], [2.7.3], [], ,
+	AC_MSG_WARN([Module jinja2 not found but mandatory for default web interface])
+	AC_SUBST([WEBUI], 'False'))
+PC_PYTHON_CHECK_MODULE_VERSION([werkzeug], [0.9], [], , 
+	AC_MSG_WARN([Module werkzeug not found but mandatory for default web interface])
+	AC_SUBST([WEBUI], 'False'))
+#Mongo datasource deps
+AC_SUBST([PYMONGO], 'True') #Can be found in lodel/buildconf.py
+PC_PYTHON_CHECK_MODULE_VERSION([pymongo], [2.7], [2.8], ,
+	AC_MSG_WARN([Module pymongo not found. The mongodb datasource will not be able to work])
+	AC_SUBST([PYMONGO], 'False')
+)
+
+#Documentation checks
+AC_SUBST([DOCOK], 'OK')
+AC_CHECK_PROGS([DOXYGEN], [doxygen])
+if test -z "$DOXYGEN";
+then
+	AC_MSG_WARN([Doxygen not found - You will not be able to generate documentation])
+	AC_SUBST([DOCOK], '')
+fi
+AC_CHECK_PROGS([GRAPHVIZ], [dot neato twopi])
+if test -z "$GRAPHVIZ";
+then
+	AC_MSG_WARN([Graphviz not found (dot executable missing) - You will not be able to generate documentation])
+	AC_SUBST([DOCOK], '')
+fi
+AC_CHECK_PROGS([DOXYPY], [doxypy])
+if test -z "$DOXYPY";
+then
+	AC_MSG_WARN([Doxypy script not found (https://pypi.python.org/pypi/doxypy/0.3) - You will not be able to generate documentation])
+	AC_SUBST([DOCOK], '')
+fi
+
+AC_OUTPUT
+
+if test -z "$DOCOK";
+	then AC_MSG_WARN([You will not be able to generate doxygen documentation. See up for reasons])
+fi
+
+if test "$WEBUI" = 'False';
+	then AC_MSG_WARN([Mandatory components are missing for running default web UI. See up for reasons])
+fi
+
+if test "$PYMONGO" = 'False';
+	then AC_MSG_WARN([You will not be able to user mongodb datasource. See up for reasons])
+fi

install/Makefile

@@ -11,5 +11,5 @@ init_db:
 list_hooks: dyncode
 	$(python) -c 'import lodel_admin; lodel_admin.list_registered_hooks()'
 
-discover_plugins:
+refresh_plugins:
 	$(python) -c 'import lodel_admin; lodel_admin.update_plugin_discover_cache()'

install/conf.d/lodel2.ini

@@ -1,8 +1,6 @@
 [lodel2]
 debug = False
 sitename = noname
-plugins_path = /foo/plugins
-plugins = dummy, webui, dummy_datasource
 
 [lodel2.logging.stderr]
 level = DEBUG

lodel/Makefile.am

@@ -0,0 +1,9 @@
+SUBDIRS=auth editorial_model leapi plugin settings utils
+
+lodel_PYTHON = *.py
+
+lodeldir=$(pkgpythondir)/
+
+distclean-local:
+	-rm Makefile Makefile.in
+

lodel/__init__.py

@@ -14,3 +14,179 @@ dyncode = None
 # 4. "lodel2_bootstraped" hooks are called
 # 5. "lodel2_loader_main" hooks are called (if runned from loader.py as main executable)
 #
+
+##@page lodel2_instance_admin Lodel2 instance administration
+#
+#@section lodel2_instance_adm_tools Tools
+#
+#@subsection lodel2_instance_makefile Makefile
+#
+#The Makefile allows to run automated without arguments such as :
+#- refresh the dynamic code using conf + EM (target **dyncode**)
+#- update databases (target **init_db**)
+#- refresh plugins list (target **refresh_plugins**)
+#
+#@subsection lodel2_instance_adm_scripts lodel_admin.py scripts
+#
+#In all instances you find a symlink named lodel_admin.py . This script
+#contains the code run by @ref lodel2_instance_makefile "Makefile targets"
+#and a main function that allows to run it as a CLI script.
+#
+#@par Script help
+#<pre>
+#usage: lodel_admin.py [-h] [-L] [ACTION] [OPTIONS [OPTIONS ...]]
+#
+#Lodel2 script runner
+#
+#positional arguments:
+#  ACTION              One of the following actions : discover-plugin [...]
+#  OPTIONS             Action options. Use lodel_admin.py ACTION -h to have
+#                      help on a specific action
+#
+#optional arguments:
+#  -h, --help          show this help message and exit
+#  -L, --list-actions  List available actions
+#</pre>
+#
+#@par Script customization
+#
+#See @ref lodel2_script_doc "Lodel2 scripting"
+#
+#
+
+##@defgroup lodel2_deployment Diffusion and deployment
+
+##@page lodel2_autotools Lodel2 and autotools integration
+#@ingroup lodel2_deployment
+#
+#Autotools provide a way to distribute a software on Posix platforms.
+#
+#@section lodel2_autotools_howto Howto use them
+#
+#Basically you have to run :
+#- <code>./bootstrap.sh</code> to generate the configure script( run 
+#approximatly <code>aclocal; autoconf; automake</code> or 
+#<code>autoreconf</code> )
+#- <code>./configure</code> to generate Makefile s
+#- <code>make</code> to build lodel2 (actually to generate lodel/buildconf.py
+#from @ref lodel/buildconf.py.in )
+#
+#Here is a list of most usefull targets provided by lodel2's Makefile :
+#- automake targets
+# - **all** compile the sources (don't do a lot for a script langage)
+# - **clean** delete compiled files (don't do a lot for a script langage)
+# - **distclean** enhanced comportment compared to default (delete compiled 
+#files and generated binary). Here it deletes everything generated by
+#<code>./bootstrap.sh && ./configure && make</code>
+# - **install** Install lodel2 (for the moment copy the lodel dir in 
+#the good path (configurable when running ./configure ) )
+# - **uninstall** Remove installed files
+#- lodel2 specific targets 
+# - **tests**, **check** and **checks** are aliases for running tests
+# - **doc** generate the doxygen documentation
+# - **em_test** refresh the example/em_test.pickle file using em_test.py
+# - **dyncode** generate a dyncode.py file using lefactory in
+#lodel/leapi/dyncode.py
+#
+#@section lodel2_autotools_why Why using autotools
+#
+#Python has a lot of packaging and distributing solutions, but none of them
+#is as convinent, complete, portable as GNU autotools. For example setup.py 
+#with distutils has no uninstall target; pip, wheel, easy-install etc brokes 
+#totally your distribution packaging/upgrade system etc.
+#
+#Autotools are portable, integrated by debian packaging system ( see 
+#checkinstall) and can support multi langages.
+#
+#@section lodel2_autotools_whatfor For doing what
+#
+#Autotools are here to allow distributing and installing Lodel2 on 
+#Posix OS. 
+#
+#The distribution mechanisms handles dependencies checking (NO AUTO INSTALL
+#WITH BINARY BLOBS !!!), compiling .py files to pyc and pyo, and copy all files
+#in the good directories (python libs, doc, scripts etc)
+#
+#@section lodel2_autotools_how How autotools are integrated
+#
+#What we call autotools is in fact a lot of software. In our case we use only
+#both of them : 
+#<a href="https://www.gnu.org/software/autoconf/autoconf.html#documentation">
+#autoconf</a> and 
+#<a href="https://www.gnu.org/software/automake/#documentation">automake</a>
+#
+#A python file is generated ( lodel/buildconf.py from 
+#@ref lodel/buildconf.py.in) containing various informations gathered during
+#the build process (for example the presence of pymongo or the precense of
+#the dependency needed by webui etc.)
+#
+#@subsection lodel2_autoconf Autoconf
+#
+#Autoconf job is to handle configure.ac file and generated the configure
+#script.
+#
+#@par Configure script
+#The configure script job is to check all dependencies fetch all
+#path etc. And when runned it generates all Makefile from the Makefile.in files
+#(see @ref lodel2_automake "below" )
+#
+#@par Autoconf macros
+#We use both macro family :
+#- <a href="https://www.gnu.org/software/automake/manual/html_node/Python.html">
+#default autoconf python macro</a>
+#- <a href="https://www.gnu.org/software/pyconfigure/manual/">
+#pyconfigure autoconf macros</a>
+#@see lodel2_autotools_problems
+#
+#@subsection lodel2_automake Automake
+#
+#Automake job is to transform the Makefile.am files into Makefile.in files.
+#It handles all target creation for build, clean, install, uninstall etc.
+#
+#@section lodel2_autotools_problems Encontered problems
+#
+#@ref lodel2_autoconf "Autoconf" use macro "written in m4" (not sure if m4
+#is the macro langage). We use two macros sources : automake default python 
+#support & pyconfigure automake macros.
+#
+#Those macros are broken with python3 (see 
+#<a href="https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1408092">
+#the python3 sysconfig bug with debian OS</a> ). There is patched version of 
+#these macro in the m4 directory (and the associated patches : 
+#@ref m4/python.m4.patch "for automake python macros patch" and 
+#@ref m4/python_pyconfigure.m4.patch "for pyconfigure python macros patch")
+
+##@file m4/python.m4.patch
+#@ingroup lodel2_deployment
+#@brief Patch of automake python macro to solve a bug in pythondir retrieval 
+#on debian
+#@see https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1408092
+
+##@file m4/python_pyconfigure.m4.patch
+#@ingroup lodel2_deployment
+#@brief Patch to solve a bug in pyconfigure ac macros in pythondir retrieval 
+#on debian
+#@see https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1408092
+
+##@file m4/python.m4
+#@ingroup lodel2_deployment
+#@brief Automake macro for python (patched version)
+#@see m4/python.m4.patch
+
+
+##@file m4/python_pyconfigure.m4
+#@brief Pyconfigure automake macro (patched version)
+#@see m4/python_pyconfigure.m4.patch
+
+##@file configure.ac
+#@brief configure script model for autoconf
+#@ingroup lodel2_deployment
+
+##@file Makefile.am
+#@brief Makefile model for autotools
+#@ingroup lodel2_deployment
+
+##@file lodel/Makefile.am
+#@brief Makefile model for autotools
+#@ingroup lodel2_deployment
+

lodel/auth/Makefile.am

@@ -0,0 +1,5 @@
+auth_PYTHON = *.py
+authdir=$(pkgpythondir)/auth
+
+distclean-local:
+	-rm Makefile Makefile.in

lodel/buildconf.py.in

@@ -0,0 +1,5 @@
+##@brief Stores constant evaluated at build time
+#@note Populated by ./configure
+
+PYMONGO=@PYMONGO@
+WEBUI=@WEBUI@

lodel/editorial_model/Makefile.am

@@ -0,0 +1,7 @@
+SUBDIRS=translator
+
+em_PYTHON=*.py
+emdir=$(pkgpythondir)/editorial_model
+
+distclean-local:
+	-rm Makefile Makefile.in

lodel/editorial_model/translator/Makefile.am

@@ -0,0 +1,5 @@
+translator_PYTHON=*.py
+translatordir=$(pkgpythondir)/editorial_model/translator
+
+distclean-local:
+	-rm Makefile Makefile.in

lodel/leapi/Makefile.am

@@ -0,0 +1,7 @@
+SUBDIRS=datahandlers
+
+leapi_PYTHON= *.py
+leapidir=$(pkgpythondir)/leapi
+
+distclean-local:
+	-rm Makefile Makefile.in

lodel/leapi/datahandlers/Makefile.am

@@ -0,0 +1,5 @@
+dh_PYTHON=*.py
+dhdir=$(pkgpythondir)/leapi/datahandlers
+
+distclean-local:
+	-rm Makefile Makefile.in

lodel/leapi/datahandlers/base_classes.py

@@ -31,7 +31,6 @@ class DataHandler(object):
     ##@brief List fields that will be exposed to the construct_data_method
     _construct_datas_deps = []
     
-    directly_editable = True
     ##@brief constructor
     # @param internal False | str : define whether or not a field is internal
     # @param immutable bool : indicates if the fieldtype has to be defined in child classes of LeObject or if it is
@@ -251,15 +250,11 @@ class Reference(DataHandler):
     # @param internal bool : if False, the field is not internal
     # @param **kwargs : other arguments
     def __init__(self, allowed_classes = None, back_reference = None, internal=False, **kwargs):
+        ##@brief set of allowed LeObject child classes
         self.__allowed_classes = set() if allowed_classes is None else set(allowed_classes)
-        self.allowed_classes = list() if allowed_classes is None else allowed_classes
-        
-        if back_reference is not None:
-            if len(back_reference) != 2:
-                raise ValueError("A tuple (classname, fieldname) expected but got '%s'" % back_reference)
-            #if not issubclass(lodel.leapi.leobject.LeObject, back_reference[0]) or not isinstance(back_reference[1], str):
-            #    raise TypeError("Back reference was expected to be a tuple(<class LeObject>, str) but got : (%s, %s)" % (back_reference[0], back_reference[1]))
-        self.__back_reference = back_reference
+        ##@brief Stores back references informations
+        self.__back_reference = None
+        self.__set_back_reference(back_reference)
         super().__init__(internal=internal, **kwargs)
     
     @property
@@ -271,7 +266,13 @@ class Reference(DataHandler):
         return copy.copy(self.__allowed_classes)
 
     ##@brief Set the back reference for this field.
-    def _set_back_reference(self, back_reference):
+    def __set_back_reference(self, back_reference):
+        if back_reference is None:
+            return
+        if len(back_reference) != 2:
+            raise LodelDataHandlerException("A tuple(LeObjectChild, fieldname) \
+expected but got '%s'" % back_reference)
+        
         self.__back_reference = back_reference
 
     ##@brief Check value

lodel/leapi/datahandlers/references.py

@@ -74,7 +74,6 @@ class Map(MultipleRef):
 ##@brief This Reference class is designed to handler hierarchy with some constraint
 class Hierarch(MultipleRef):
     
-    directly_editable = False
     ##@brief Instanciate a data handler handling hierarchical relation with constraints
     # @param back_reference tuple : Here it is mandatory to have a back ref (like a parent field)
     # @param max_depth int | None :  limit of depth
@@ -91,3 +90,4 @@ class Hierarch(MultipleRef):
         else:
             return None, FieldValidationError("Set or string expected for a set field")
         return val, expt
+

lodel/plugin/Makefile.am

@@ -0,0 +1,5 @@
+plugin_PYTHON=*.py
+plugindir=$(pkgythondir)/plugin
+
+distclean-local:
+	-rm Makefile Makefile.in

lodel/plugin/__init__.py

@@ -1,6 +1,7 @@
 #-*- coding: utf-8 -*-
 
 ##@defgroup lodel2_plugins Plugins
+#@ingroup lodel2_leapi
 #
 #Groups all stuff that concerns plugins
 

lodel/plugin/core_scripts.py

@@ -6,7 +6,7 @@ import lodel.plugin.scripts as lodel_script
 #@ingroup lodel2_script
 
 
-##@brief Implements lodel_admin.py discover-plugin action
+##@brief Implements lodel_admin.py **discover-plugin** action
 #@ingroup lodel2_plugins
 #@ingroup lodel2_script
 #
@@ -38,4 +38,31 @@ without modifying existing cache")
             print("\t- %s(%s) in %s" % (
                 pname, pinfos['version'], pinfos['path']))
             
+##@brief Implements lodel_admin.py **hooks-list** action
+#@ingroup lodel2_script
+#@ingroup lodel2_hooks
+class ListHooks(lodel_script.LodelScript):
+    _action = 'hooks-list'
+    _description = 'Generate a list of registered hooks once instance started'
+
+    @classmethod
+    def argparser_config(cls, parser):
+        pass
+
+    @classmethod
+    def run(cls, args):
+        import loader
+        loader.start()
+        from lodel.plugin.hooks import LodelHook
+        hlist = LodelHook.hook_list()
+        print("Registered hooks : ")
+        for name in sorted(hlist.keys()):
+            print("\t- %s is registered by :" % name)
+            for hfun, priority in hlist[name]:
+                msg = "\t\t- {modname}.{funname} with priority : {priority}"
+                print(msg.format(
+                    modname = hfun.__module__,
+                    funname = hfun.__name__,
+                    priority = priority))
+            print("\n")
 

lodel/plugin/interface.py

@@ -25,3 +25,12 @@ class InterfacePlugin(Plugin):
             raise PluginError("Maximum one interface allowed")
         super().__init__(name)
         self._instance = self
+
+    ##@brief Clear class
+    #@see plugins.Plugin::clear()
+    @classmethod
+    def clear_cls(cls):
+        if cls._instance is not None:
+            inst = cls._instance
+            cls._instance = None
+            del(inst)

lodel/plugin/plugins.py

@@ -7,7 +7,6 @@ import copy
 import json
 from importlib.machinery import SourceFileLoader, SourcelessFileLoader
 
-import plugins
 from lodel import logger
 from lodel.settings.utils import SettingsError
 from .exceptions import *
@@ -216,6 +215,13 @@ class MetaPlugType(type):
         if ptype_name not in cls._all_ptypes:
             raise PluginError("Unknown plugin type '%s'" % ptype_name)
         return cls._all_ptypes[ptype_name]
+    
+    ##@brief Call the clear classmethod on each child classes
+    @classmethod
+    def clear_cls(cls):
+        for pcls in cls._all_ptypes.values():
+            pcls.clear_cls()
+        
 
 ##@brief Handle plugins
 #@ingroup lodel2_plugins
@@ -254,6 +260,12 @@ class Plugin(object, metaclass=MetaPlugType):
     #None in abstract classes and implemented by child classes
     _type_conf_name = None
 
+    ##@brief Stores virtual modules uniq key
+    #@note When testing if a dir contains a plugin, if we reimport the __init__
+    #in a module with the same name, all non existing value (plugin_type for
+    #example) are replaced by previous plugin values
+    _mod_cnt = 0
+
     ##@brief Plugin class constructor
     #
     # Called by setting in early stage of lodel2 boot sequence using classmethod
@@ -656,6 +668,12 @@ file : '%s'. Running discover again..." % DISCOVER_CACHE_FILENAME)
             cls._plugin_instances = dict()
         if cls._load_called != []:
             cls._load_called = []
+        MetaPlugType.clear_cls()
+    
+    ##@brief Designed to be implemented by child classes
+    @classmethod
+    def clear_cls(cls):
+        pass
     
     ##@brief Reccursively walk throught paths to find plugin, then stores
     #found plugin in a file...
@@ -684,6 +702,7 @@ file : '%s'. Running discover again..." % DISCOVER_CACHE_FILENAME)
                 #dropped
                 pass
         result = {'path_list': paths, 'plugins': result}
+        print("DEUG ",result['plugins'])
         #Writing to cache
         if not no_cache:
             with open(DISCOVER_CACHE_FILENAME, 'w+') as pdcache:
@@ -789,11 +808,12 @@ file : '%s'. Running discover again..." % DISCOVER_CACHE_FILENAME)
     #@param path str : Directory path
     #@return a tuple (init_module, module_name)
     @classmethod
-    def import_init(self, path):
+    def import_init(cls, path):
+        cls._mod_cnt += 1 # in order to ensure module name unicity
         init_source = os.path.join(path, INIT_FILENAME)
-        temp_module = '%s.%s.%s' % (
+        temp_module = '%s.%s.%s%d' % (
             VIRTUAL_TEMP_PACKAGE_NAME, os.path.basename(os.path.dirname(path)),
-            'test_init')
+            'test_init', cls._mod_cnt)
         try:
             loader = SourceFileLoader(temp_module, init_source)
         except (ImportError, FileNotFoundError) as e:

lodel/plugin/scripts.py

@@ -21,7 +21,7 @@ __registered_scripts = dict()
 #@ingroup lodel2_script
 #@ingroup lodel2_plugins
 #
-#Automatic script registration on child class declaration
+#Automatic action registration on child class declaration
 class MetaLodelScript(type):
     
     def __init__(self, name, bases, attrs):
@@ -177,3 +177,44 @@ def main_run():
     ret = script._run()
     ret = 0 if ret is None else ret
     exit(ret)
+
+##@page lodel2_script_doc Lodel2 scripting
+#@ingroup lodel2_script
+#
+#@section lodel2_script_adm Lodel2 instance administration scripts
+#
+#Lodel2 provides instance administration operation using Makefiles or 
+#lodel_admin.py script ( see @ref lodel2_instance_admin ).
+#
+#The lodel_admin.py script take as first option an action. Each action
+#correspond to a sub-script with it's own options etc. To get a list
+#of all available action run <code>python3 lodel_admin.py -L</code>.
+#
+#@section lodel2_script_action lodel_admin.py actions
+#
+#Action implementation is done by class inheritance. To create a new action
+#write a @ref lodel.plugin.scripts.LodelScript "LodelScript" derived class (
+#see @ref lodel.plugin.core_scripts "core_scripts.py" file as example )
+#
+#@subsection lodel2_script_inheritance LodelScript inheritance
+#
+#In order to implement properly a new action you have to write a new 
+#@ref lodel.plugin.scripts.LodelScript "LodelScript" derivated class.
+#Some methods and attributes are mandatory to write a fully functionnal
+#derivated class. Here is a list :
+#
+#- mandatory methods
+# - @ref plugin.scripts.LodelScript.argparser_config() "argparser_config()" :
+#(classmethod) initialize argparse.Parser
+# - @ref plugin.scripts.LodelScript.run() "run()" : (classmethod) contains the
+#code that runs to perform the action
+#- mandatory attributes
+# - @ref plugin.scripts.LodelScript::_action "_action" : (class attribute)
+#stores action name
+# - @ref plugin.scripts.LodelScript::_description "_description" : (class 
+#attribute) sotres a short action description
+#
+#@note On script's action registration : once child class is written you only
+#need to import it to trigger script's action registration (see
+#@ref plugin.scripts.MetaLodelScript )
+#

lodel/plugin/sessionhandler.py

@@ -57,3 +57,12 @@ class SessionHandlerPlugin(Plugin, metaclass=SessionPluginWrapper):
             self.__class__._instance = self
         else:
             raise RuntimeError("A SessionHandler Plugin is already plug")
+    
+    ##@brief Clear class
+    #@see plugins.Plugin::clear()
+    @classmethod
+    def clear_cls(cls):
+        if cls._instance is not None:
+            inst = cls._instance
+            cls._instance = None
+            del(inst)

lodel/settings/Makefile.am

@@ -0,0 +1,5 @@
+settings_PYTHON=*.py
+settingsdir=$(pkgpythondir)/settings
+
+distclean-local:
+	-rm Makefile Makefile.in

lodel/utils/Makefile.am

@@ -0,0 +1,5 @@
+utils_PYTHON=*.py
+utilsdir=$(pkgpythondir)/utils
+
+distclean-local:
+	-rm Makefile Makefile.in

m4/python.m4

@@ -0,0 +1,243 @@
+## ------------------------                                 -*- Autoconf -*-
+## Python file handling
+## From Andrew Dalke
+## Updated by James Henstridge
+## ------------------------
+# Copyright (C) 1999-2013 Free Software Foundation, Inc.
+#
+# This file is free software; the Free Software Foundation
+# gives unlimited permission to copy and/or distribute it,
+# with or without modifications, as long as this notice is preserved.
+
+
+# AM_PATH_PYTHON([MINIMUM-VERSION], [ACTION-IF-FOUND], [ACTION-IF-NOT-FOUND])
+# ---------------------------------------------------------------------------
+# Adds support for distributing Python modules and packages.  To
+# install modules, copy them to $(pythondir), using the python_PYTHON
+# automake variable.  To install a package with the same name as the
+# automake package, install to $(pkgpythondir), or use the
+# pkgpython_PYTHON automake variable.
+#
+# The variables $(pyexecdir) and $(pkgpyexecdir) are provided as
+# locations to install python extension modules (shared libraries).
+# Another macro is required to find the appropriate flags to compile
+# extension modules.
+#
+# If your package is configured with a different prefix to python,
+# users will have to add the install directory to the PYTHONPATH
+# environment variable, or create a .pth file (see the python
+# documentation for details).
+#
+# If the MINIMUM-VERSION argument is passed, AM_PATH_PYTHON will
+# cause an error if the version of python installed on the system
+# doesn't meet the requirement.  MINIMUM-VERSION should consist of
+# numbers and dots only.
+AC_DEFUN([AM_PATH_PYTHON],
+ [
+  dnl Find a Python interpreter.  Python versions prior to 2.0 are not
+  dnl supported. (2.0 was released on October 16, 2000).
+  m4_define_default([_AM_PYTHON_INTERPRETER_LIST],
+[python python2 python3 python3.3 python3.2 python3.1 python3.0 python2.7 dnl
+ python2.6 python2.5 python2.4 python2.3 python2.2 python2.1 python2.0])
+
+  AC_ARG_VAR([PYTHON], [the Python interpreter])
+
+  m4_if([$1],[],[
+    dnl No version check is needed.
+    # Find any Python interpreter.
+    if test -z "$PYTHON"; then
+      AC_PATH_PROGS([PYTHON], _AM_PYTHON_INTERPRETER_LIST, :)
+    fi
+    am_display_PYTHON=python
+  ], [
+    dnl A version check is needed.
+    if test -n "$PYTHON"; then
+      # If the user set $PYTHON, use it and don't search something else.
+      AC_MSG_CHECKING([whether $PYTHON version is >= $1])
+      AM_PYTHON_CHECK_VERSION([$PYTHON], [$1],
+			      [AC_MSG_RESULT([yes])],
+			      [AC_MSG_RESULT([no])
+			       AC_MSG_ERROR([Python interpreter is too old])])
+      am_display_PYTHON=$PYTHON
+    else
+      # Otherwise, try each interpreter until we find one that satisfies
+      # VERSION.
+      AC_CACHE_CHECK([for a Python interpreter with version >= $1],
+	[am_cv_pathless_PYTHON],[
+	for am_cv_pathless_PYTHON in _AM_PYTHON_INTERPRETER_LIST none; do
+	  test "$am_cv_pathless_PYTHON" = none && break
+	  AM_PYTHON_CHECK_VERSION([$am_cv_pathless_PYTHON], [$1], [break])
+	done])
+      # Set $PYTHON to the absolute path of $am_cv_pathless_PYTHON.
+      if test "$am_cv_pathless_PYTHON" = none; then
+	PYTHON=:
+      else
+        AC_PATH_PROG([PYTHON], [$am_cv_pathless_PYTHON])
+      fi
+      am_display_PYTHON=$am_cv_pathless_PYTHON
+    fi
+  ])
+
+  if test "$PYTHON" = :; then
+  dnl Run any user-specified action, or abort.
+    m4_default([$3], [AC_MSG_ERROR([no suitable Python interpreter found])])
+  else
+
+  dnl Query Python for its version number.  Getting [:3] seems to be
+  dnl the best way to do this; it's what "site.py" does in the standard
+  dnl library.
+
+  AC_CACHE_CHECK([for $am_display_PYTHON version], [am_cv_python_version],
+    [am_cv_python_version=`$PYTHON -c "import sys; sys.stdout.write(sys.version[[:3]])"`])
+  AC_SUBST([PYTHON_VERSION], [$am_cv_python_version])
+
+  dnl Use the values of $prefix and $exec_prefix for the corresponding
+  dnl values of PYTHON_PREFIX and PYTHON_EXEC_PREFIX.  These are made
+  dnl distinct variables so they can be overridden if need be.  However,
+  dnl general consensus is that you shouldn't need this ability.
+
+  AC_SUBST([PYTHON_PREFIX], ['${prefix}'])
+  AC_SUBST([PYTHON_EXEC_PREFIX], ['${exec_prefix}'])
+
+  dnl At times (like when building shared libraries) you may want
+  dnl to know which OS platform Python thinks this is.
+
+  AC_CACHE_CHECK([for $am_display_PYTHON platform], [am_cv_python_platform],
+    [am_cv_python_platform=`$PYTHON -c "import sys; sys.stdout.write(sys.platform)"`])
+  AC_SUBST([PYTHON_PLATFORM], [$am_cv_python_platform])
+
+  # Just factor out some code duplication.
+  am_python_setup_sysconfig="\
+import sys
+# Prefer sysconfig over distutils.sysconfig, for better compatibility
+# with python 3.x.  See automake bug#10227.
+# But not see <https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1408092>
+try:
+    import sysconfig
+except ImportError:
+    can_use_sysconfig = 0
+else:
+    can_use_sysconfig = 1
+# Can't use sysconfig in CPython 2.7, since it's broken in virtualenvs:
+# <https://github.com/pypa/virtualenv/issues/118>
+# Can't use sysconfig in CPython > 3.0 in debian since it's broken :
+# <https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1408092>
+try:
+    from platform import python_implementation
+    if python_implementation() == 'CPython' and ( \
+            float(sys.version[[:3]]) > 3.0 or sys.version[[:3]] == '2.7'):
+        can_use_sysconfig = 0
+except ImportError:
+    pass"
+
+  dnl Set up 4 directories:
+
+  dnl pythondir -- where to install python scripts.  This is the
+  dnl   site-packages directory, not the python standard library
+  dnl   directory like in previous automake betas.  This behavior
+  dnl   is more consistent with lispdir.m4 for example.
+  dnl Query distutils for this directory.
+  AC_CACHE_CHECK([for $am_display_PYTHON script directory],
+    [am_cv_python_pythondir],
+    [if test "x$prefix" = xNONE
+     then
+       am_py_prefix=$ac_default_prefix
+     else
+       am_py_prefix=$prefix
+     fi
+     am_cv_python_pythondir=`$PYTHON -c "
+$am_python_setup_sysconfig
+if can_use_sysconfig:
+    sitedir = sysconfig.get_path('purelib', vars={'base':'$am_py_prefix'})
+else:
+    from distutils import sysconfig
+    sitedir = sysconfig.get_python_lib(0, 0, prefix='$am_py_prefix')
+sys.stdout.write(sitedir)"`
+     case $am_cv_python_pythondir in
+     $am_py_prefix*)
+       am__strip_prefix=`echo "$am_py_prefix" | sed 's|.|.|g'`
+       am_cv_python_pythondir=`echo "$am_cv_python_pythondir" | sed "s,^$am__strip_prefix,$PYTHON_PREFIX,"`
+       ;;
+     *)
+       case $am_py_prefix in
+         /usr|/System*) ;;
+         *)
+	  am_cv_python_pythondir=$PYTHON_PREFIX/lib/python$PYTHON_VERSION/site-packages
+	  ;;
+       esac
+       ;;
+     esac
+    ])
+  AC_SUBST([pythondir], [$am_cv_python_pythondir])
+
+  dnl pkgpythondir -- $PACKAGE directory under pythondir.  Was
+  dnl   PYTHON_SITE_PACKAGE in previous betas, but this naming is
+  dnl   more consistent with the rest of automake.
+
+  AC_SUBST([pkgpythondir], [\${pythondir}/$PACKAGE])
+
+  dnl pyexecdir -- directory for installing python extension modules
+  dnl   (shared libraries)
+  dnl Query distutils for this directory.
+  AC_CACHE_CHECK([for $am_display_PYTHON extension module directory],
+    [am_cv_python_pyexecdir],
+    [if test "x$exec_prefix" = xNONE
+     then
+       am_py_exec_prefix=$am_py_prefix
+     else
+       am_py_exec_prefix=$exec_prefix
+     fi
+     am_cv_python_pyexecdir=`$PYTHON -c "
+$am_python_setup_sysconfig
+if can_use_sysconfig:
+    sitedir = sysconfig.get_path('platlib', vars={'platbase':'$am_py_prefix'})
+else:
+    from distutils import sysconfig
+    sitedir = sysconfig.get_python_lib(1, 0, prefix='$am_py_prefix')
+sys.stdout.write(sitedir)"`
+     case $am_cv_python_pyexecdir in
+     $am_py_exec_prefix*)
+       am__strip_prefix=`echo "$am_py_exec_prefix" | sed 's|.|.|g'`
+       am_cv_python_pyexecdir=`echo "$am_cv_python_pyexecdir" | sed "s,^$am__strip_prefix,$PYTHON_EXEC_PREFIX,"`
+       ;;
+     *)
+       case $am_py_exec_prefix in
+         /usr|/System*) ;;
+         *)
+	   am_cv_python_pyexecdir=$PYTHON_EXEC_PREFIX/lib/python$PYTHON_VERSION/site-packages
+	   ;;
+       esac
+       ;;
+     esac
+    ])
+  AC_SUBST([pyexecdir], [$am_cv_python_pyexecdir])
+
+  dnl pkgpyexecdir -- $(pyexecdir)/$(PACKAGE)
+
+  AC_SUBST([pkgpyexecdir], [\${pyexecdir}/$PACKAGE])
+
+  dnl Run any user-specified action.
+  $2
+  fi
+
+])
+
+
+# AM_PYTHON_CHECK_VERSION(PROG, VERSION, [ACTION-IF-TRUE], [ACTION-IF-FALSE])
+# ---------------------------------------------------------------------------
+# Run ACTION-IF-TRUE if the Python interpreter PROG has version >= VERSION.
+# Run ACTION-IF-FALSE otherwise.
+# This test uses sys.hexversion instead of the string equivalent (first
+# word of sys.version), in order to cope with versions such as 2.2c1.
+# This supports Python 2.0 or higher. (2.0 was released on October 16, 2000).
+AC_DEFUN([AM_PYTHON_CHECK_VERSION],
+ [prog="import sys
+# split strings by '.' and convert to numeric.  Append some zeros
+# because we need at least 4 digits for the hex conversion.
+# map returns an iterator in Python 3.0 and a list in 2.x
+minver = list(map(int, '$2'.split('.'))) + [[0, 0, 0]]
+minverhex = 0
+# xrange is not present in Python 3.0 and range returns an iterator
+for i in list(range(0, 4)): minverhex = (minverhex << 8) + minver[[i]]
+sys.exit(sys.hexversion < minverhex)"
+  AS_IF([AM_RUN_LOG([$1 -c "$prog"])], [$3], [$4])])

m4/python.m4.patch

@@ -0,0 +1,24 @@
+--- /usr/share/aclocal-1.14/python.m4	2014-10-27 05:45:43.000000000 +0100
++++ python.m4	2016-08-30 17:20:03.690623000 +0200
+@@ -111,6 +111,7 @@ AC_DEFUN([AM_PATH_PYTHON],
+ import sys
+ # Prefer sysconfig over distutils.sysconfig, for better compatibility
+ # with python 3.x.  See automake bug#10227.
++# But not see <https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1408092>
+ try:
+     import sysconfig
+ except ImportError:
+@@ -119,9 +120,12 @@ else:
+     can_use_sysconfig = 1
+ # Can't use sysconfig in CPython 2.7, since it's broken in virtualenvs:
+ # <https://github.com/pypa/virtualenv/issues/118>
++# Can't use sysconfig in CPython > 3.0 in debian since it's broken :
++# <https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1408092>
+ try:
+     from platform import python_implementation
+-    if python_implementation() == 'CPython' and sys.version[[:3]] == '2.7':
++    if python_implementation() == 'CPython' and ( \
++            float(sys.version[[:3]]) > 3.0 or sys.version[[:3]] == '2.7'):
+         can_use_sysconfig = 0
+ except ImportError:
+     pass"

m4/python_pyconfigure.m4

@@ -0,0 +1,755 @@
+# Copyright 2012, 2013, 2014 Brandon Invergo <brandon@invergo.net>
+#
+# This file is part of pyconfigure.  This program is free
+# software; you can redistribute it and/or modify it under the
+# terms of the GNU General Public License as published by the
+# Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# Under Section 7 of GPL version 3, you are granted additional
+# permissions described in the Autoconf Configure Script Exception,
+# version 3.0, as published by the Free Software Foundation.
+#
+# You should have received a copy of the GNU General Public License
+# and a copy of the Autoconf Configure Script Exception along with
+# this program; see the files COPYINGv3 and COPYING.EXCEPTION
+# respectively.  If not, see <http://www.gnu.org/licenses/>.
+
+
+# Many of these macros were adapted from ones written by Andrew Dalke
+# and James Henstridge and are included with the Automake utility
+# under the following copyright terms:
+#
+# Copyright (C) 1999-2012 Free Software Foundation, Inc.
+#
+# This file is free software; the Free Software Foundation
+# gives unlimited permission to copy and/or distribute it,
+# with or without modifications, as long as this notice is preserved.
+
+# Table of Contents:
+#
+# 1. Language selection
+#    and routines to produce programs in a given language.
+#
+# 2. Producing programs in a given language.
+#
+# 3. Looking for a compiler
+#    And possibly the associated preprocessor.
+#
+# 4. Looking for specific libs & functionality
+
+
+## ----------------------- ##
+## 1. Language selection.  ##
+## ----------------------- ##
+
+
+# AC_LANG(Python)
+# ---------------
+AC_LANG_DEFINE([Python], [py], [PY], [PYTHON], [],
+[ac_ext=py
+ac_compile='chmod +x conftest.$ac_ext >&AS_MESSAGE_LOG_FD'
+ac_link='chmod +x conftest.$ac_ext && cp conftest.$ac_ext conftest >&AS_MESSAGE_LOG_FD'
+])
+
+
+# AC_LANG_PYTHON
+# --------------
+AU_DEFUN([AC_LANG_PYTHON], [AC_LANG(Python)])
+
+
+## ----------------------- ##
+## 2. Producing programs.  ##
+## ----------------------- ##
+
+
+# AC_LANG_PROGRAM(Python)([PROLOGUE], [BODY])
+# -------------------------------------------
+m4_define([AC_LANG_PROGRAM(Python)], [dnl
+@%:@!$PYTHON
+$1
+m4_if([$2], [], [], [dnl
+if __name__ == '__main__':
+$2])])
+
+
+# _AC_LANG_IO_PROGRAM(Python)
+# ---------------------------
+# Produce source that performs I/O.
+m4_define([_AC_LANG_IO_PROGRAM(Python)],
+[AC_LANG_PROGRAM([dnl
+import sys
+try:
+    h = open('conftest.out')
+except:
+    sys.exit(1)
+else:
+    close(h)
+    sys.exit(0)
+], [])])
+
+
+# _AC_LANG_CALL(Python)([PROLOGUE], [FUNCTION])
+# ---------------------
+# Produce source that calls FUNCTION
+m4_define([_AC_LANG_CALL(Python)],
+[AC_LANG_PROGRAM([$1], [$2])])
+
+
+## -------------------------------------------- ##
+## 3. Looking for Compilers and Interpreters.   ##
+## -------------------------------------------- ##
+
+
+AC_DEFUN([AC_LANG_COMPILER(Python)],
+[AC_REQUIRE([PC_PROG_PYTHON])])
+
+
+# PC_INIT([MIN-VERSION], [MAX-VERSION]) 
+# -----------------------------
+# Initialize pyconfigure, finding a Python interpreter with a given
+# minimum and/or maximum version. 
+AC_DEFUN([PC_INIT],
+[PC_PROG_PYTHON([], [$1], [$2])
+dnl If we found something, do a sanity check that the interpreter really
+dnl has the version its name would suggest.
+m4_ifval([PYTHON],
+        [PC_PYTHON_VERIFY_VERSION([>=], [pc_min_ver], [],
+                  [AC_MSG_FAILURE([No compatible Python interpreter found. If you're sure that you have one, try setting the PYTHON environment variable to the location of the interpreter.])])])
+m4_ifval([PYTHON],
+        [PC_PYTHON_VERIFY_VERSION([<=], [pc_max_ver], [],
+                  [AC_MSG_FAILURE([No compatible Python interpreter found. If you're sure that you have one, try setting the PYTHON environment variable to the location of the interpreter.])])])
+])# PC_INIT
+
+# PC_PROG_PYTHON([PROG-TO-CHECK-FOR], [MIN-VERSION], [MAX-VERSION])
+# ---------------------------------
+# Find a Python interpreter.  Python versions prior to 2.0 are not
+# supported. (2.0 was released on October 16, 2000).
+AC_DEFUN_ONCE([PC_PROG_PYTHON],
+[AC_ARG_VAR([PYTHON], [the Python interpreter])
+dnl The default minimum version is 2.0
+m4_define_default([pc_min_ver], m4_ifval([$2], [$2], [2.0]))
+dnl The default maximum version is 3.3
+m4_define_default([pc_max_ver], m4_ifval([$3], [$3], [4.0]))
+dnl Build up a list of possible interpreter names. 
+m4_define_default([_PC_PYTHON_INTERPRETER_LIST],
+    [dnl If we want some Python 3 versions (max version >= 3.0), 
+dnl also search for "python3"
+     m4_if(m4_version_compare(pc_max_ver, [2.9]), [1], [python3], []) \
+dnl If we want some Python 2 versions (min version <= 2.7),
+dnl also search for "python2".
+     m4_if(m4_version_compare(pc_min_ver, [2.8]), [-1], [python2], []) \
+dnl Construct a comma-separated list of interpreter names (python2.6, 
+dnl python2.7, etc). We only care about the first 3 characters of the
+dnl version strings (major-dot-minor; not 
+dnl major-dot-minor-dot-bugfix[-dot-whatever])
+     m4_foreach([pc_ver], 
+                    m4_esyscmd_s(seq -s[[", "]] -f["[[%.1f]]"] m4_substr(pc_max_ver, [0], [3]) -0.1 m4_substr(pc_min_ver, [0], [3])),
+dnl Remove python2.8 and python2.9 since they will never exist
+                    [m4_bmatch(pc_ver, [2.[89]], [], [python]pc_ver)]) \
+     [python]])
+dnl Do the actual search at last.
+m4_ifval([$1],
+	[AC_PATH_PROGS(PYTHON, [$1 _PC_PYTHON_INTERPRETER_LIST])],
+	[AC_PATH_PROGS(PYTHON, [_PC_PYTHON_INTERPRETER_LIST])])
+])# PC_PROG_PYTHON
+  
+
+# PC_PYTHON_PROG_PYTHON_CONFIG(PROG-TO-CHECK-FOR)
+# ----------------------------------------------
+# Find the python-config program
+AC_DEFUN([PC_PYTHON_PROG_PYTHON_CONFIG],
+[AC_REQUIRE([PC_PROG_PYTHON])[]dnl
+AC_ARG_VAR([PYTHON_CONFIG], [the Python-config program])
+dnl python-config's binary name is normally based on the Python interpreter's
+dnl binary name (i.e. python2.7 -> python2.7-config)
+m4_define([_PYTHON_BASENAME], [`basename $PYTHON`])
+m4_ifval([$1],
+	[AC_PATH_PROGS(PYTHON_CONFIG, [$1 _PYTHON_BASENAME-config])],
+	[AC_PATH_PROG(PYTHON_CONFIG, _PYTHON_BASENAME-config)])
+]) # PC_PYTHON_PROG_PYTHON_CONFIG
+
+
+# PC_PYTHON_VERIFY_VERSION([RELATION], [VERSION], [ACTION-IF-TRUE], [ACTION-IF-FALSE])
+# ---------------------------------------------------------------------------
+# Run ACTION-IF-TRUE if the Python interpreter PROG has version [RELATION] VERSION.
+# i.e if RELATION is "<", check if PROG has a version number less than VERSION.
+# Run ACTION-IF-FALSE otherwise.
+# Specify RELATION as any mathematical comparison "<", ">", "<=", ">=", "==" or "!="
+# This test uses sys.hexversion instead of the string equivalent (first
+# word of sys.version), in order to cope with versions such as 2.2c1.
+# This supports Python 2.0 or higher. (2.0 was released on October 16, 2000).
+AC_DEFUN([PC_PYTHON_VERIFY_VERSION],
+[m4_define([pc_python_safe_ver], m4_bpatsubsts($2, [\.], [_]))
+AC_CACHE_CHECK([if Python $1 '$2'],
+    [[pc_cv_python_req_version_]pc_python_safe_ver],
+    [AC_LANG_PUSH(Python)[]dnl
+     AC_RUN_IFELSE(
+        [AC_LANG_PROGRAM([dnl
+import sys
+], [dnl
+    # split strings by '.' and convert to numeric.  Append some zeros
+    # because we need at least 4 digits for the hex conversion.
+    # map returns an iterator in Python 3.0 and a list in 2.x
+    reqver = list(map(int, '$2'.split('.'))) + [[0, 0, 0]]
+    reqverhex = 0
+    # xrange is not present in Python 3.0 and range returns an iterator
+    for i in list(range(4)):
+        reqverhex = (reqverhex << 8) + reqver[[i]]
+    # the final 8 bits are "0xf0" for final versions, which are all
+    # we'll test against, since it's doubtful that a released software
+    # will depend on an alpha- or beta-state Python.
+    reqverhex += 0xf0
+    if sys.hexversion $1 reqverhex:
+        sys.exit()
+    else:
+        sys.exit(1)
+])], 
+         [[pc_cv_python_req_version_]pc_python_safe_ver=yes], 
+         [[pc_cv_python_req_version_]pc_python_safe_ver=no])
+     AC_LANG_POP(Python)[]dnl
+    ])
+AS_IF([test "$[pc_cv_python_req_version_]pc_python_safe_ver" = "no"], [$4], [$3])
+])# PC_PYTHON_VERIFY_VERSION
+
+
+# PC_PYTHON_CHECK_VERSION
+# -----------------------
+# Query Python for its version number.  Getting [:3] seems to be
+# the best way to do this; it's what "site.py" does in the standard
+# library.
+AC_DEFUN([PC_PYTHON_CHECK_VERSION],
+[AC_REQUIRE([PC_PROG_PYTHON])[]dnl
+AC_CACHE_CHECK([for $1 version], 
+    [pc_cv_python_version],
+    [AC_LANG_PUSH(Python)[]dnl
+     AC_LINK_IFELSE([AC_LANG_PROGRAM([dnl
+import sys
+], [dnl
+    sys.stdout.write(sys.version[[:3]])
+])],
+                   [pc_cv_python_version=`./conftest`],
+                   [AC_MSG_FAILURE([failed to run Python program])])
+     AC_LANG_POP(Python)[]dnl
+    ])
+AC_SUBST([PYTHON_VERSION], [$pc_cv_python_version])
+])# PC_PYTHON_CHECK_VERSION
+
+
+# PC_PYTHON_CHECK_PREFIX
+# ----------------------
+# Use the value of $prefix for the corresponding value of
+# PYTHON_PREFIX. This is made a distinct variable so it can be
+# overridden if need be.  However, general consensus is that you
+# shouldn't need this ability. 
+AC_DEFUN([PC_PYTHON_CHECK_PREFIX],
+[AC_REQUIRE([PC_PYTHON_PROG_PYTHON_CONFIG])[]dnl
+dnl Try to get it with python-config otherwise do it from within Python
+AC_CACHE_CHECK([for Python prefix], [pc_cv_python_prefix],
+[if test -x "$PYTHON_CONFIG"; then
+    pc_cv_python_prefix=`$PYTHON_CONFIG --prefix 2>&AS_MESSAGE_LOG_FD`
+else
+    AC_LANG_PUSH(Python)[]dnl
+    AC_LINK_IFELSE([AC_LANG_PROGRAM([dnl
+import sys
+], [dnl
+    sys.stdout.write(sys.prefix)
+])], [pc_cv_python_prefix=`./conftest`;
+      if test $? != 0; then
+         AC_MSG_FAILURE([could not determine Python prefix])
+      fi],
+      [AC_MSG_FAILURE([failed to run Python program])])
+    AC_LANG_POP(Python)[]dnl
+fi])
+AC_SUBST([PYTHON_PREFIX], [$pc_cv_python_prefix])])
+
+
+# PC_PYTHON_CHECK_EXEC_PREFIX
+# --------------------------
+# Like above, but for $exec_prefix
+AC_DEFUN([PC_PYTHON_CHECK_EXEC_PREFIX],
+[AC_REQUIRE([PC_PYTHON_PROG_PYTHON_CONFIG])[]dnl
+dnl Try to get it with python-config otherwise do it from within Python
+AC_CACHE_CHECK([for Python exec-prefix], [pc_cv_python_exec_prefix],
+[if test -x "$PYTHON_CONFIG"; then
+    pc_cv_python_exec_prefix=`$PYTHON_CONFIG --exec-prefix 2>&AS_MESSAGE_LOG_FD`
+else
+    AC_LANG_PUSH(Python)[]dnl
+    AC_LINK_IFELSE([AC_LANG_PROGRAM([dnl
+import sys
+], [dnl
+    sys.stdout.write(sys.exec_prefix)
+])],
+        [pc_cv_python_exec_prefix=`./conftest`;
+         if test $? != 0; then
+            AC_MSG_FAILURE([could not determine Python exec_prefix])
+         fi],
+         [AC_MSG_FAILURE([failed to run Python program])])
+    AC_LANG_POP(Python)[]dnl
+fi
+])
+AC_SUBST([PYTHON_EXEC_PREFIX], [$pc_cv_python_exec_prefix])])
+
+
+# PC_PYTHON_CHECK_INCLUDES
+# ------------------------
+# Find the Python header file include flags (ie
+# '-I/usr/include/python')
+AC_DEFUN([PC_PYTHON_CHECK_INCLUDES],
+[AC_REQUIRE([PC_PYTHON_PROG_PYTHON_CONFIG])[]dnl
+dnl Try to find the headers location with python-config otherwise guess
+AC_CACHE_CHECK([for Python includes], [pc_cv_python_includes],
+[if test -x "$PYTHON_CONFIG"; then
+    pc_cv_python_includes=`$PYTHON_CONFIG --includes 2>&AS_MESSAGE_LOG_FD`
+else
+    pc_cv_python_includes="[-I$includedir/$_PYTHON_BASENAME]m4_ifdef(PYTHON_ABI_FLAGS,
+    PYTHON_ABI_FLAGS,)"
+fi
+])
+AC_SUBST([PYTHON_INCLUDES], [$pc_cv_python_includes])])
+
+
+# PC_PYTHON_CHECK_HEADERS([ACTION-IF-PRESENT], [ACTION-IF-ABSENT])
+# -----------------------
+# Check for the presence and usability of Python.h
+AC_DEFUN([PC_PYTHON_CHECK_HEADERS],
+[AC_REQUIRE([PC_PYTHON_CHECK_INCLUDES])[]dnl
+pc_cflags_store=$CPPFLAGS
+CPPFLAGS="$CFLAGS $PYTHON_INCLUDES"
+AC_CHECK_HEADER([Python.h], [$1], [$2])
+CPPFLAGS=$pc_cflags_store
+])
+
+
+# PC_PYTHON_CHECK_LIBS
+# --------------------
+# Find the Python lib flags (ie '-lpython')
+AC_DEFUN([PC_PYTHON_CHECK_LIBS],
+[AC_REQUIRE([PC_PYTHON_PROG_PYTHON_CONFIG])[]dnl
+dnl Try to find the lib flags with python-config otherwise guess
+AC_CACHE_CHECK([for Python libs], [pc_cv_python_libs],
+[if test -x "$PYTHON_CONFIG"; then
+    pc_cv_python_libs=`$PYTHON_CONFIG --libs 2>&AS_MESSAGE_LOG_FD`
+else
+    pc_cv_python_libs="[-l$_PYTHON_BASENAME]m4_ifdef(PYTHON_ABI_FLAGS, PYTHON_ABI_FLAGS,)"
+fi
+])
+AC_SUBST([PYTHON_LIBS], [$pc_cv_python_libs])])
+
+
+# PC_PYTHON_TEST_LIBS(LIBRARY-FUNCTION, [ACTION-IF-PRESENT], [ACTION-IF-ABSENT])
+# -------------------
+# Verify that the Python libs can be loaded
+AC_DEFUN([PC_PYTHON_TEST_LIBS],
+[AC_REQUIRE([PC_PYTHON_CHECK_LIBS])[]dnl
+pc_libflags_store=$LIBS
+for lflag in $PYTHON_LIBS; do
+    case $lflag in
+    	 -lpython*@:}@
+		LIBS="$LIBS $lflag"
+		pc_libpython=`echo $lflag | sed -e 's/^-l//'`
+		;;
+         *@:}@;;
+    esac
+done
+AC_CHECK_LIB([$pc_libpython], [$1], [$2], [$3])])
+
+
+# PC_PYTHON_CHECK_CFLAGS
+# ----------------------
+# Find the Python CFLAGS
+AC_DEFUN([PC_PYTHON_CHECK_CFLAGS],
+[AC_REQUIRE([PC_PYTHON_PROG_PYTHON_CONFIG])[]dnl
+dnl Try to find the CFLAGS with python-config otherwise give up
+AC_CACHE_CHECK([for Python CFLAGS], [pc_cv_python_cflags],
+[if test -x "$PYTHON_CONFIG"; then
+    pc_cv_python_cflags=`$PYTHON_CONFIG --cflags 2>&AS_MESSAGE_LOG_FD`
+else
+    pc_cv_python_cflags=
+fi
+])
+AC_SUBST([PYTHON_CFLAGS], [$pc_cv_python_cflags])])
+
+
+# PC_PYTHON_CHECK_LDFLAGS
+# -----------------------
+# Find the Python LDFLAGS
+AC_DEFUN([PC_PYTHON_CHECK_LDFLAGS],
+[AC_REQUIRE([PC_PYTHON_PROG_PYTHON_CONFIG])[]dnl
+dnl Try to find the LDFLAGS with python-config otherwise give up
+AC_CACHE_CHECK([for Python LDFLAGS], [pc_cv_python_ldflags],
+[if test -x "$PYTHON_CONFIG"; then
+    pc_cv_python_ldflags=`$PYTHON_CONFIG --ldflags 2>&AS_MESSAGE_LOG_FD`
+else
+    pc_cv_python_ldflags=
+fi
+])
+AC_SUBST([PYTHON_LDFLAGS], [$pc_cv_python_ldflags])])
+
+
+# PC_PYTHON_CHECK_EXTENSION_SUFFIX
+# --------------------------------
+# Find the Python extension suffix (i.e. '.cpython-32.so')
+AC_DEFUN([PC_PYTHON_CHECK_EXTENSION_SUFFIX],
+[AC_REQUIRE([PC_PYTHON_PROG_PYTHON_CONFIG])[]dnl
+dnl Try to find the suffix with python-config otherwise give up
+AC_CACHE_CHECK([for Python extension suffix], [pc_cv_python_extension_suffix],
+[if test -x "$PYTHON_CONFIG"; then
+     pc_cv_python_extension_suffix=`$PYTHON_CONFIG --extension-suffix 2>&AS_MESSAGE_LOG_FD`
+else
+    pc_cv_python_extension_suffix=
+fi
+])
+AC_SUBST([PYTHON_EXTENSION_SUFFIX], [$pc_cv_python_extension_suffix])])
+
+
+# PC_PYTHON_CHECK_ABI_FLAGS
+# -------------------------
+# Find the Python ABI flags
+AC_DEFUN([PC_PYTHON_CHECK_ABI_FLAGS],
+[AC_REQUIRE([PC_PYTHON_PROG_PYTHON_CONFIG])[]dnl
+dnl Try to find the ABI flags with python-config otherwise give up
+AC_CACHE_CHECK([for Python ABI flags], [pc_cv_python_abi_flags],
+[if test -x "$PYTHON_CONFIG"; then
+     pc_cv_python_abi_flags=`$PYTHON_CONFIG --abiflags 2>&AS_MESSAGE_LOG_FD`
+else
+    pc_cv_python_abi_flags=
+fi
+])
+AC_SUBST([PYTHON_ABI_FLAGS], [$pc_cv_python_abi_flags])])
+
+
+# PC_PYTHON_CHECK_PLATFORM
+# ------------------------
+# At times (like when building shared libraries) you may want
+# to know which OS platform Python thinks this is.
+AC_DEFUN([PC_PYTHON_CHECK_PLATFORM],
+[AC_REQUIRE([PC_PROG_PYTHON])[]dnl
+dnl Get the platform from within Python (sys.platform)
+AC_CACHE_CHECK([for Python platform], [pc_cv_python_platform],
+    [AC_LANG_PUSH(Python)[]dnl
+     AC_LINK_IFELSE([AC_LANG_PROGRAM([dnl
+import sys
+], [dnl
+    sys.stdout.write(sys.platform)
+])], [pc_cv_python_platform=`./conftest`;
+     if test $? != 0; then
+        AC_MSG_FAILURE([could not determine Python platform])
+     fi],
+     [AC_MSG_FAILURE([failed to run Python program])])
+    AC_LANG_POP(Python)[]dnl
+   ])
+AC_SUBST([PYTHON_PLATFORM], [$pc_cv_python_platform])
+])
+
+
+# PC_PYTHON_CHECK_SITE_DIR
+# ---------------------
+# The directory to which new libraries are installed (i.e. the
+# "site-packages" directory.
+AC_DEFUN([PC_PYTHON_CHECK_SITE_DIR],
+[AC_REQUIRE([PC_PROG_PYTHON])AC_REQUIRE([PC_PYTHON_CHECK_PREFIX])[]dnl
+AC_CACHE_CHECK([for Python site-packages directory],
+    [pc_cv_python_site_dir],
+    [AC_LANG_PUSH(Python)[]dnl
+    if test "x$prefix" = xNONE
+     then
+       pc_py_prefix=$ac_default_prefix
+     else
+       pc_py_prefix=$prefix
+     fi
+     AC_LINK_IFELSE([AC_LANG_PROGRAM([dnl
+import sys
+from platform import python_implementation
+# sysconfig in CPython 2.7 doesn't work in virtualenv
+# <https://github.com/pypa/virtualenv/issues/118>
+try:
+    import sysconfig
+except:
+    can_use_sysconfig = False
+else:
+    can_use_sysconfig = True
+if can_use_sysconfig:
+    # Can't use sysconfig in CPython > 3.0 in debian since it's broken :
+    # <https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1408092>
+    if python_implementation() == "CPython" (
+            float(sys.version[[:3]]) > 3.0 or sys.version[[:3]] == '2.7'):
+        can_use_sysconfig = False
+if not can_use_sysconfig:        
+    from distutils import sysconfig
+    sitedir = sysconfig.get_python_lib(False, False, prefix='$pc_py_prefix')
+else:
+    sitedir = sysconfig.get_path('purelib', vars={'base':'$pc_py_prefix'})
+], [dnl
+    sys.stdout.write(sitedir)
+])], [pc_cv_python_site_dir=`./conftest`],
+     [AC_MSG_FAILURE([failed to run Python program])])
+     AC_LANG_POP(Python)[]dnl
+     case $pc_cv_python_site_dir in
+     $pc_py_prefix*)
+       pc__strip_prefix=`echo "$pc_py_prefix" | sed 's|.|.|g'`
+       pc_cv_python_site_dir=`echo "$pc_cv_python_site_dir" | sed "s,^$pc__strip_prefix/,,"`
+       ;;
+     *)
+       case $pc_py_prefix in
+         /usr|/System*) ;;
+         *)
+	  pc_cv_python_site_dir=lib/python$PYTHON_VERSION/site-packages
+	  ;;
+       esac
+       ;;
+     esac
+     ])
+AC_SUBST([pythondir], [\${prefix}/$pc_cv_python_site_dir])])# PC_PYTHON_CHECK_SITE_DIR
+
+# PC_PYTHON_SITE_PACKAGE_DIR
+# --------------------------
+# $PACKAGE directory under PYTHON_SITE_DIR
+AC_DEFUN([PC_PYTHON_SITE_PACKAGE_DIR],
+[AC_REQUIRE([PC_PYTHON_CHECK_SITE_DIR])[]dnl
+AC_SUBST([pkgpythondir], [\${pythondir}/$PACKAGE_NAME])])
+
+
+# PC_PYTHON_CHECK_EXEC_DIR
+# ------------------------
+# directory for installing python extension modules (shared libraries)
+AC_DEFUN([PC_PYTHON_CHECK_EXEC_DIR],
+[AC_REQUIRE([PC_PROG_PYTHON])AC_REQUIRE([PC_PYTHON_CHECK_EXEC_PREFIX])[]dnl
+  AC_CACHE_CHECK([for Python extension module directory],
+    [pc_cv_python_exec_dir],
+    [AC_LANG_PUSH(Python)[]dnl
+    if test "x$pc_cv_python_exec_prefix" = xNONE
+     then
+       pc_py_exec_prefix=$pc_cv_python_prefix
+     else
+       pc_py_exec_prefix=$pc_cv_python_exec_prefix
+     fi
+     AC_LINK_IFELSE([AC_LANG_PROGRAM([dnl
+import sys
+from platform import python_implementation
+# sysconfig in CPython 2.7 doesn't work in virtualenv
+# <https://github.com/pypa/virtualenv/issues/118>
+try:
+    import sysconfig
+except:
+    can_use_sysconfig = False
+else:
+    can_use_sysconfig = True
+if can_use_sysconfig:
+    if python_implementation() == "CPython" and sys.version[[:3]] == '2.7':
+        can_use_sysconfig = False
+if not can_use_sysconfig:        
+    from distutils import sysconfig
+    sitedir = sysconfig.get_python_lib(False, False, prefix='$pc_py__exec_prefix')
+else:
+    sitedir = sysconfig.get_path('purelib', vars={'platbase':'$pc_py_exec_prefix'})
+], [dnl
+    sys.stdout.write(sitedir)
+])], [pc_cv_python_exec_dir=`./conftest`],
+     [AC_MSG_FAILURE([failed to run Python program])])
+     AC_LANG_POP(Python)[]dnl
+     case $pc_cv_python_exec_dir in
+     $pc_py_exec_prefix*)
+       pc__strip_prefix=`echo "$pc_py_exec_prefix" | sed 's|.|.|g'`
+       pc_cv_python_exec_dir=`echo "$pc_cv_python_exec_dir" | sed "s,^$pc__strip_prefix/,,"`
+       ;;
+     *)
+       case $pc_py_exec_prefix in
+         /usr|/System*) ;;
+         *)
+	   pc_cv_python_exec_dir=lib/python$PYTHON_VERSION/site-packages
+	   ;;
+       esac
+       ;;
+     esac
+    ])
+AC_SUBST([pyexecdir], [\${exec_prefix}/$pc_cv_python_pyexecdir])]) #PY_PYTHON_CHECK_EXEC_LIB_DIR
+
+
+# PC_PYTHON_EXEC_PACKAGE_DIR
+# --------------------------
+# $PACKAGE directory under PYTHON_SITE_DIR
+AC_DEFUN([PC_PYTHON_EXEC_PACKAGE_DIR],
+[AC_REQUIRE([PC_PYTHON_CHECK_EXEC_DIR])[]dnl
+AC_SUBST([pkgpyexecdir], [\${pyexecdir}/$PACKAGE_NAME])])
+
+
+## -------------------------------------------- ##
+## 4. Looking for specific libs & functionality ##
+## -------------------------------------------- ##
+
+
+# PC_PYTHON_CHECK_MODULE(LIBRARY, [ACTION-IF-FOUND], [ACTION-IF-NOT-FOUND])
+# ----------------------------------------------------------------------
+# Macro for checking if a Python library is installed
+AC_DEFUN([PC_PYTHON_CHECK_MODULE],
+[AC_REQUIRE([PC_PROG_PYTHON])[]dnl
+m4_define([pc_python_safe_mod], m4_bpatsubsts($1, [\.], [_]))
+AC_CACHE_CHECK([for Python '$1' library],
+    [[pc_cv_python_module_]pc_python_safe_mod],
+    [AC_LANG_PUSH(Python)[]dnl
+     AC_RUN_IFELSE(
+	[AC_LANG_PROGRAM([dnl
+import sys
+try:
+    import $1
+except:
+    sys.exit(1)
+else:
+    sys.exit(0)
+], [])],
+	[[pc_cv_python_module_]pc_python_safe_mod="yes"],
+	[[pc_cv_python_module_]pc_python_safe_mod="no"])
+     AC_LANG_POP(Python)[]dnl
+    ])
+AS_IF([test "$[pc_cv_python_module_]pc_python_safe_mod" = "no"], [$3], [$2])
+])# PC_PYTHON_CHECK_MODULE
+
+
+# PC_PYTHON_CHECK_FUNC([LIBRARY], FUNCTION, ARGS, [ACTION-IF-FOUND], [ACTION-IF-NOT-FOUND])
+# ---------------------------------------------------------------------------------------
+# Check to see if a given function call, optionally from a module, can
+# be successfully called
+AC_DEFUN([PC_PYTHON_CHECK_FUNC],
+[AC_REQUIRE([PC_PROG_PYTHON])[]dnl
+m4_define([pc_python_safe_mod], m4_bpatsubsts($1, [\.], [_]))
+AC_CACHE_CHECK([for Python m4_ifnblank($1, '$1.$2()', '$2()') function],
+    [[pc_cv_python_func_]pc_python_safe_mod[_$2]],
+    [AC_LANG_PUSH(Python)[]dnl
+     AC_RUN_IFELSE(
+	[AC_LANG_PROGRAM([dnl
+import sys
+m4_ifnblank([$1], [dnl
+try:
+    import $1
+except:
+    sys.exit(1)
+], [])], 
+[
+m4_ifnblank([$1], [
+    try:
+        $1.$2($3)], [
+    try:
+        $2($3)])
+    except:
+        sys.exit(1)
+    else:
+        sys.exit(0)
+])],
+	[[pc_cv_python_func_]pc_python_safe_mod[_$2]="yes"],
+	[[pc_cv_python_func_]pc_python_safe_mod[_$2]="no"])
+     AC_LANG_POP(Python)[]dnl
+    ])
+AS_IF([test "$[pc_cv_python_func_]pc_python_safe_mod[_$2]" = "no"], [$5], [$4])
+])# PC_PYTHON_CHECK_FUNC
+
+# PC_PYTHON_CHECK_MODULE_MATCH_VERSION(LIBRARY, VERSION, [ACTION-IF-FOUND], [ACTION-IF-NOT-FOUND)
+# -------------------------------------------------
+# Macro for checking if a Python library with this version is installed
+#
+AC_DEFUN([PC_PYTHON_CHECK_MODULE_MATCH_VERSION],
+[AC_REQUIRE([PC_PROG_PYTHON])[]dnl
+m4_define([pc_python_safe_mod], m4_bpatsubsts($1, [\.], [_]))
+AC_CACHE_CHECK([for Python '$1' library version '$2'],
+    [[pc_cv_python_module_version]pc_python_safe_mod],
+    [AC_LANG_PUSH(Python)[]dnl
+     AC_LINK_IFELSE(
+	[AC_LANG_PROGRAM([dnl
+import sys
+try:
+    import $1
+except:
+    version='no'
+else:
+    for vers_attr in ('__version__', 'version', 'version_info'):
+        if hasattr($1, vers_attr):
+            version = getattr($1, vers_attr)
+            break
+    else:
+        version = 'unknown'
+sys.stdout.write(version)
+], [])], 
+	[[pc_cv_python_module_version]pc_python_safe_mod=`./conftest`],
+	[AC_MSG_FAILURE([failed to run Python program])])
+	AC_LANG_POP(Python)[]dnl
+	])
+
+AS_IF([test "x$[pc_cv_python_module_version]pc_python_safe_mod" = "x$2" ],
+	[$3],
+	[	AS_IF(
+			[test "x$[pc_cv_python_module_version]pc_python_safe_mod" = 'unknown'],
+			AC_MSG_WARN([Unable to fetch version of Python module $1]))
+		[$4]
+	])
+])# PC_PYTHON_CHECK_MODULE_VERSION
+
+
+# PC_PYTHON_CHECK_MODULE_VERSION(LIBRARY, MIN-VERSION, MAX-VERSION, [ACTION-IF-FOUND], [ACTION-IF-NOT-FOUND)
+# -------------------------------------------------
+# Macro for checking if a Python library with this version is installed
+#
+AC_DEFUN([PC_PYTHON_CHECK_MODULE_VERSION],
+[AC_REQUIRE([PC_PROG_PYTHON])[]dnl
+m4_define([pc_python_safe_mod], m4_bpatsubsts($1, [\.], [_]))
+m4_append([pc_python_safe_mod], m4_bpatsubsts($2, [\.], [_]))
+m4_append([pc_python_safe_mod], m4_bpatsubsts($3, [\.], [_]))
+AC_CACHE_CHECK(
+    [for Python '$1' library m4_ifnblank([$2],['$2' <= ]) version m4_ifnblank([$3], [<= '$3'])],
+    [[pc_cv_python_module_version]pc_python_safe_mod],
+    [AC_LANG_PUSH(Python)[]dnl
+     AC_LINK_IFELSE(
+	[AC_LANG_PROGRAM([dnl
+import sys
+def cmp_vers(v1,v2):
+    v1 = v1.split('.')
+    v2 = v2.split('.')
+    for i in range(max([len](v1), [len](v2))):
+        v1v = int(v1[[i]] if i < [len](v1) else 0)
+        v2v = int(v2[[i]] if i < [len](v2) else 0)
+        if v1v > v2v:
+            return 1
+        if v1v < v2v:
+            return -1
+    return 0
+try:
+    import $1
+except:
+    result='not found'
+else:
+    result='yes'
+    vmin = '$2'
+    vmax = '$3'
+    for vers_attr in ('__version__', 'version', 'version_info'):
+        if hasattr($1, vers_attr):
+            version = getattr($1, vers_attr)
+            break
+    else:
+        result = 'unknown'
+    if version not in ('unknonwn', 'no'):
+        failmsg = "but "+ version + " found"
+        if [len](vmin) > 0:
+            if cmp_vers(version, vmin) < 0:
+                result = failmsg
+        if [len](vmax) > 0:
+            if cmp_vers(version, vmax) > 0:
+                result = failmsg
+
+sys.stdout.write(result)
+], [])], 
+	[[pc_cv_python_module_version]pc_python_safe_mod=`./conftest`],
+	[AC_MSG_FAILURE([failed to run Python program])])
+	AC_LANG_POP(Python)[]dnl
+	])
+AS_IF(	[test "$[pc_cv_python_module_version]pc_python_safe_mod" = "yes"],
+	[$4],
+	[	AS_IF(
+			[test "x$[pc_cv_python_module_version]pc_python_safe_mod" = 'unknown'],
+			AC_MSG_WARN([Unable to fetch version of Python module $1]))
+		[$5]
+	])
+])# PC_PYTHON_CHECK_MODULE_VERSION

m4/python_pyconfigure.m4.patch_bugfix

@@ -0,0 +1,14 @@
+--- /usr/share/pyconfigure/m4/python.m4	2016-04-27 05:19:12.000000000 +0200
++++ python_pyconfigure.m4	2016-08-30 17:21:56.810623000 +0200
+@@ -475,7 +475,10 @@ except:
+ else:
+     can_use_sysconfig = True
+ if can_use_sysconfig:
+-    if python_implementation() == "CPython" and sys.version[[:3]] == '2.7':
++    # Can't use sysconfig in CPython > 3.0 in debian since it's broken :
++    # <https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1408092>
++    if python_implementation() == "CPython" (
++            float(sys.version[[:3]]) > 3.0 or sys.version[[:3]] == '2.7'):
+         can_use_sysconfig = False
+ if not can_use_sysconfig:        
+     from distutils import sysconfig

plugins/mongodb_datasource/__init__.py

@@ -17,4 +17,5 @@ __fullname__ = "MongoDB plugin"
 #
 # @return bool|str : True if all the checks are OK, an error message if not
 def _activate():
-    return True
+    from lodel import buildconf
+    return buildconf.PYMONGO

plugins/webui/run.py

@@ -44,12 +44,18 @@ def cookie_hash(token):
 #@return None or a session token
 def load_cookie(request):
     token = request.cookies.get(COOKIE_SESSION_ID)
+<<<<<<< HEAD
     
     if token is None or len(token) == 0:
         return None
     
     token=token.encode()
     
+=======
+    if token is None or len(token) == 0:
+        return None
+    token=token.encode()
+>>>>>>> 0fc8616c02ad999204e1e4926e9007c0ae7e035b
     hashtok = request.cookies.get(COOKIE_SESSION_HASH)
     if hashtok is None:
         raise ClientAuthenticationFailure(

runtest

@@ -54,6 +54,7 @@ cp -R tests $testdir
 cd $testdir
 rm -R conf.d && mv tests/tests_conf.d conf.d
 make
+make refresh_plugins
 python3 loader.py $@
 
 rm -Rf $testdir

tests/migration_handler/test_db_init.py

@@ -1,26 +1,32 @@
 # -*- coding: utf-8 -*-
-import unittest
-from plugins.mongodb_datasource.migration_handler import *
 
-class MongoDbMigrationHandlerTestCase(unittest.TestCase):
+from lodel import buildconf
 
-    def test_check_connection_args(self):
-        empty_connection_args = {}
-        with self.assertRaises(TypeError):
-            MigrationHandler(empty_connection_args)
+if not buildconf.PYMONGO:
+    import warnings
+    warnings.warn("Skipping tests about mongodb datasource. Pymongo not installed")
+else:
+    import unittest
+    from plugins.mongodb_datasource.migration_handler import *
+    class MongoDbMigrationHandlerTestCase(unittest.TestCase):
 
-        bad_connection_args_dicts = [
-            {'host': 'localhost', 'port': 20030},
-            {'host': 'localhost', 'port': 28015},
-            {'host': 'localhost', 'port': 28015, 'login':'lodel', 'password': 'lap'}
-        ]
-        for bad_connection_args_dict in bad_connection_args_dicts:
+        def test_check_connection_args(self):
+            empty_connection_args = {}
             with self.assertRaises(TypeError):
-                MigrationHandler(bad_connection_args_dict)
+                MigrationHandler(empty_connection_args)
 
-    ## @todo pass the connection arguments in the settings
-    @unittest.skip
-    def test_init_db(self):
-        correct_connection_args = {'host': 'localhost', 'port': 28015, 'username': 'lodel_admin', 'password': 'lapwd', 'db_name': 'lodel'}
-        migration_handler = MigrationHandler(correct_connection_args)
-        migration_handler.init_db()
+            bad_connection_args_dicts = [
+                {'host': 'localhost', 'port': 20030},
+                {'host': 'localhost', 'port': 28015},
+                {'host': 'localhost', 'port': 28015, 'login':'lodel', 'password': 'lap'}
+            ]
+            for bad_connection_args_dict in bad_connection_args_dicts:
+                with self.assertRaises(TypeError):
+                    MigrationHandler(bad_connection_args_dict)
+
+        ## @todo pass the connection arguments in the settings
+        @unittest.skip
+        def test_init_db(self):
+            correct_connection_args = {'host': 'localhost', 'port': 28015, 'username': 'lodel_admin', 'password': 'lapwd', 'db_name': 'lodel'}
+            migration_handler = MigrationHandler(correct_connection_args)
+            migration_handler.init_db()

tests/plugin/test_plugin.py

@@ -3,62 +3,63 @@
 import unittest
 
 from lodel.plugin.plugins import Plugin, PluginError
+from lodel.plugin.datasource_plugin import DatasourcePlugin
+from lodel.plugin.sessionhandler import SessionHandlerPlugin
+from lodel.plugin.interface import InterfacePlugin
+from lodel.plugin.extensions import Extension
 from lodel.settings.settings import Settings
 import tests.loader_utils
 
+##@todo write tests about discovering
 class PluginTestCase(unittest.TestCase):
+    """ Test case grouping all tests on Plugin class init procedures """
 
-    def test_plugin_init_right_name(self):
-        Plugin.start(['/home/helene/lodel2/plugins'],['dummy'])
+    def setUp(self):
         Plugin.clear()
-        
-    # With a wrong plugin name, a NameError Exception has to be raised at line 318 of plugin.py
-    def test_plugin_init_wrong_name(self):
-        with self.assertRaises(NameError):
-            Plugin.start(['/home/helene/lodel2/plugins', '/home/helene/lodel2/tests/tests_plugins' ],['wrong_plugin_name'])
-        Plugin.clear()
-        
-    # With a wrong plugin name, a NameError Exception has to be raised at line 318 of plugin.py
-    def test_plugin_init_right_wrong_name(self):
-        with self.assertRaises(NameError):
-            Plugin.start(['/home/helene/lodel2/plugins', '/home/helene/lodel2/tests/tests_plugins'],['dummy', 'wrong_plugin_name'])
+
+    def test_start(self):
+        """ Testing plugin registration with a valid list of plugins name """
+        Plugin.start(['dummy', 'dummy_datasource'])
+
+    def test_double_start(self):
+        """ Testing clas behavior when starting it twice """
+        Plugin.start(['dummy', 'dummy_datasource'])
+        with self.assertRaises(PluginError):
+            Plugin.start(['dummy', 'dummy_datasource'])
+
+    def test_clear(self):
+        """ Testing that clear allow to start again Plugin """
+        Plugin.start(['dummy', 'dummy_datasource'])
         Plugin.clear()
-    
-    def test_plugin_started(self):
-        with self.assertRaises(RuntimeError):
-            Plugin.started()
-            
-    def test_plugin_plugin_path(self):
-        Plugin.start(['/home/helene/lodel2/plugins', '/home/helene/lodel2/tests/tests_plugins'],['dummy'])
-        self.assertEqual(Plugin.plugin_path('dummy'), '/home/helene/lodel2/plugins/dummy/')
+        Plugin.start(['dummy', 'dummy_datasource'])
+
+class PluginStartedTestCase(unittest.TestCase):
+    """ Test case grouping all tests on a started Plugin class """
+
+    @classmethod
+    def setUpClass(cls):
         Plugin.clear()
-        
-    def test_plugin_get(self):
-        Plugin.start(['/home/helene/lodel2/plugins', '/home/helene/lodel2/tests/tests_plugins'],['dummy'])
-        with self.assertRaises(PluginError):
-            Plugin.get('wrong_plugin_name')
-        self.assertTrue(isinstance(Plugin.get('dummy'), Plugin))
+        Plugin.start(['dummy', 'dummy_datasource', 'webui', 'ram_session'])
+
+    @classmethod
+    def tearDownClass(cls):
         Plugin.clear()
-        
-    def test_plugin_register(self):
-        with self.assertRaises(RuntimeError):
-            Plugin.register('dummy')
-        Plugin.start(['/home/helene/lodel2/plugins'],['dummy'])
+
+    def test_construct(self):
+        """ Testing plugin instanciation """
+        pname_type = {
+            'dummy': Extension,
+            'dummy_datasource': DatasourcePlugin,
+            #'webui': InterfacePlugin, #singleton, cannot reinstanciate
+            #'ram_session': SessionHandlerPlugin, #singleton, cannot resintanciate
+            }
+        for pname, ptype in pname_type.items():
+            pinstance = Plugin.get(pname)
+            self.assertIsInstance(pinstance, ptype, "Expected plugin '%s' \
+to be in an %s instance but found an %s instance" % (
+                pname, ptype, pinstance.__class__))
+
+    def test_construct_invalid(self):
+        """ Testing plugin instanciation with a non existing name """
         with self.assertRaises(PluginError):
-            Plugin.register('dummy')
-        Plugin.clear()
-        
-    def test_plugin_load_all(self):
-        #Plugin.start(['/home/helene/lodel2/plugins'],['dummynotactivable'])
-        #Plugin.load_all()
-        pass
-        
-    
-     
-        
-        
-        
-        
-        
-        
-        
+            Plugin.get("fljkhsfh")

tests/plugin/tests_hooks.py

@@ -0,0 +1,63 @@
+#-*- coding: utf-8 -*-
+
+import unittest
+from unittest.mock import MagicMock
+
+from lodel.plugin.plugins import Plugin, PluginError
+from lodel.plugin.hooks import LodelHook
+
+testhook = 'are_we_sure_that_this_name_is_uniq'
+
+class HookTestCase(unittest.TestCase):
+
+    def setUp(self):
+        LodelHook.__reset__()
+
+    def test_registration(self):
+        """ Testing hook registration using decorator (checking using hook_list() """
+        hook_list = LodelHook.hook_list(testhook)
+        self.assertEqual({}, hook_list)
+        #hook_registration
+        @LodelHook(testhook,42)
+        def funny_fun_test_hook(hook_name, caller, payload):
+            pass
+        hook_list = LodelHook.hook_list(testhook)
+        self.assertEqual({testhook: [(funny_fun_test_hook, 42)]}, hook_list)
+
+    def test_call(self):
+        """ Testing LodelHook.call_hook() """
+        #manual registration using a mock
+        mmock = MagicMock(return_value = '4242')
+        mmock.__name__ = 'mmock'
+        hooking = LodelHook(testhook, 1337)
+        hooking(mmock)
+        res = LodelHook.call_hook(testhook, 'Caller', 'payload')
+        #Check returned value
+        self.assertEqual(
+            res,
+            '4242',
+            'Expected value was "4242" but found %s' % res)
+        #Checks call
+        mmock.assert_called_once_with(testhook, 'Caller', 'payload')
+
+    def test_priority_call(self):
+        """ Testing priority to ensure a call order """
+        @LodelHook(testhook, 1)
+        def stage_1_hook(name, caller, payload):
+            return '4'+payload
+
+        @LodelHook(testhook, 10)
+        def stage_1_hook(name, caller, payload):
+            return '3'+payload
+
+        @LodelHook(testhook, 20)
+        def stage_1_hook(name, caller, payload):
+            return '1'+payload
+
+        @LodelHook(testhook, 15)
+        def stage_1_hook(name, caller, payload):
+            return '2'+payload
+
+        result = LodelHook.call_hook(testhook, 'me', 'WootWoot')
+        self.assertEqual(result, '1234WootWoot')
+