This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Natanael Copa, benjamin.peterson, christian.heimes, georg.brandl, jeremy.kloth, jkloth, larry, matrixise, ned.deily, vstinner, yan12125
Date 2017-07-11.20:43:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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.
Date User Action Args
2017-07-11 20:43:26vstinnersetrecipients: + vstinner, georg.brandl, larry, christian.heimes, benjamin.peterson, jkloth, ned.deily, jeremy.kloth, matrixise, yan12125, Natanael Copa
2017-07-11 20:43:26vstinnersetmessageid: <>
2017-07-11 20:43:26vstinnerlinkissue29591 messages
2017-07-11 20:43:26vstinnercreate