requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3002 4.5.6 Backporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3002 4.5 the next minor milestone otherwise) • Changes should comply with our Version policy. 4.5.6 Backporting pandas supports point releases (e.g. 1.4.3) that aim to: 1. Fix bugs in new features introduced releases are based on Github branches (e.g. point release of 1.4 are based off the 1.4.x branch), “backporting” means merging a pull request fix to the main branch and correct minor branch associated with the

requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2658 4.6.6 Backporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2659 4.6 data analysis toolkit, Release 1.3.2 • Changes should comply with our Version policy. 4.6.6 Backporting In the case you want to apply changes to a stable branch from a newer branch then you can comment:

requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2738 4.6.6 Backporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2738 4.6 the next minor milestone otherwise) • Changes should comply with our Version policy. 4.6.6 Backporting In the case you want to apply changes to a stable branch from a newer branch then you can comment:

requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2738 4.6.6 Backporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2738 4.6 the next minor milestone otherwise) • Changes should comply with our Version policy. 4.6.6 Backporting In the case you want to apply changes to a stable branch from a newer branch then you can comment:

requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2831 4.6.6 Backporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2831 4.6 the next minor milestone otherwise) • Changes should comply with our Version policy. 4.6.6 Backporting In the case you want to apply changes to a stable branch from a newer branch then you can comment:

requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2833 4.6.6 Backporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2833 4.6 the next minor milestone otherwise) • Changes should comply with our Version policy. 4.6.6 Backporting In the case you want to apply changes to a stable branch from a newer branch then you can comment:

there are people interested in continued support for Python 2.7 past December 31, 2018 (either backporting bug fixes or funding) please reach out to the maintainers on the issue tracker. For more information

there are people interested in continued support for Python 2.7 past December 31, 2018 (either backporting bug fixes or funding) please reach out to the maintainers on the issue tracker. For more information