GitLab

Previously the code could only handle single constraints when expressing
dependencies in __pkginfo__ as in:

  "blog": ">= 1.1.0",

This improves on the previous situation by handling cases where
multiple constraints are stated as in:

  "blog": ">= 1.1.0, < 1.2.0",

Since we have been switched (or have switched) to using requirements.txt
and pip for installing packages, maybe this whole check could be removed
entirely.

* Validate changeset f3b46587ea1f by testing if an entity view return a 403
  status error for guests when the cubicweb instance do not allowed anonymous
  connection

--HG--
branch : 3.29

--HG--
branch : 3.30

* Related to issue #335

--HG--
branch : 3.29

--HG--
branch : 3.28

--HG--
branch : 3.28

--HG--
branch : 3.27

--HG--
branch : 3.27

--HG--
branch : 3.29

--HG--
branch : 3.28

--HG--
branch : 3.28

--HG--
branch : 3.27

Test setup fail since the self.vref is not available

This is very likely a breaking change and will force all code bases that
haven't already do so to migrate to pyramid as web server.

90% of the job has been porting and adapting a lot of tests code.

See pyramid documentation as a reference:

* https://docs.pylonsproject.org/projects/pyramid/en/2.0-branch/narr/security.html#preventing-cross-site-request-forgery-attacks
* https://docs.pylonsproject.org/projects/pyramid/en/2.0-branch/narr/security.html#checking-csrf-tokens-automatically
* https://docs.pylonsproject.org/projects/pyramid/en/latest/api/csrf.html#pyramid.csrf.CookieCSRFStoragePolicy

* Related to issue #335

 * the relation dont have rqlexpr permissions and can be deleted
 * at least one of related entites can be deleted

These two conditions are consistent with conditions in
AutoformSectionRelationTags.relations_by_section).

We also check that at least one unrelated entity exists and can be added

related #324

--HG--
branch : 3.29

--HG--
branch : 3.27

--HG--
branch : 3.31

Notification are done using Operation, and Operation do not have a `event`
attribute, because they can be used for several event.

Moreover, this commit (bcb633bd791d) changed the prototype of the
`notify_on_commit` without giving the right event to the Operation (which is a
singleton)

--HG--
branch : 3.31

related: #301

- renaming raw_input to input
- removing from __future__ import
- web/views/management.py

--HG--
branch : 3.28

cant wait for black and flake8 on CW… :)