STINNER Victor added the comment:

Larry: "Please instead choose to use bpo-30694 for the upgrades of 3.3 and 3.4 
to expat 2.2.1.  I guess there are historical reasons why the PRs are here, but 
bpo stands as a historical record; let's not confuse posterity by upgrading to 
2.2.1 using a bpo issue talking about--and upgrading four branches to--2.2.0."

I just updated the 3.4 PR.

In fact, the PR backports the libexpat 2.2.0 commit *and* then the libexpat 
2.2.1 commit. Since it's not possible to create a "patch serie" (in GitHub, it 
would mean a PR which depends on another PR), I chose to stack the two commits 
in the same PR and reuse the existing PR to not loose context.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue29591>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to