Fixed regression dating back to 0.7.9 whereby the name of a CTE might
not be properly quoted if it was referred to in multiple FROM clauses.
Also in 0.8.3, 0.7.11. [ticket:2801]

Conflicts:
	doc/build/changelog/changelog_09.rst

Conflicts:
	doc/build/changelog/changelog_08.rst
Fixed bug where list instrumentation would fail to represent a
setslice of ``[0:0]`` correctly, which in particular could occur
when using ``insert(0, item)`` with the association proxy.  Due
to some quirk in Python collections, the issue was much more likely
with Python 3 rather than 2.  Also in 0.8.3, 0.7.11.
[ticket:2807]

Conflicts:
	doc/build/changelog/changelog_09.rst

Conflicts:
	doc/build/changelog/changelog_08.rst
- this comment is wrong, the method here returns all mapper entities
- use a simple isinstance() check instead of looking for presence of
"primary_entity" flag, that's a little unclear
clean up formatting and other linting issues

Conflicts:
	test/ext/test_associationproxy.py

Conflicts:
	test/ext/test_associationproxy.py
correct for missing fail() methods which were lost when we removed unittest.TestCase
render "backports"/ "forward ports" automatically, only write out
changelog once

Conflicts:
	doc/build/changelog/changelog_09.rst

Conflicts:
	doc/build/changelog/changelog_07.rst
	doc/build/changelog/changelog_08.rst
- The regexp used by the :func:`.url.make_url` function now parses
ipv6 addresses, e.g. surrounded by brackets. [ticket:2851]
- farm out everthing to do with rtd out to the sqlalchemy.org site
fix to the changelog system for when there's no change recs in the body

Conflicts:
	doc/build/builder/changelog.py
css updates to better work with RTD badge
Fix indentation and escape *args and **kwargs
sync up 0.8's changelogs with 0.7....
sync up some changes for #2604 and #2607 from 0.7.10, 0.8.0b2
- the pronoun removal commit.   there was only one instance of a
standalone gendered pronoun with a gender-neutral subject, but also
have replaced all occurences of "his/her", "his or her", etc.  The docs have always
strived to account for both genders in any non-specific singular pronoun,
however recent controversy in the community suggests
that a zero-gendered-pronoun policy is probably best going forward.

Conflicts:
	doc/build/changelog/migration_08.rst
	doc/build/orm/session.rst
	examples/nested_sets/nested_sets.py