Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork961
Drop support for EOL Python 2.6 and 3.3#737
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Changes fromall commits
929f3e114582dfac4f7d334cce4087a6441db0dfa09ec270916223e5f773b4c80b038fFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading.Please reload this page.
Jump to
Uh oh!
There was an error while loading.Please reload this page.
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -161,13 +161,13 @@ Please note that due to breaking changes, we have to increase the major version. | ||
| with large repositories. | ||
| * CRITICAL: fixed incorrect `Commit` object serialization when authored or commit date had timezones which were not | ||
| divisiblej by 3600 seconds. This would happen if the timezone was something like `+0530` for instance. | ||
| * A list of all additional fixes can be found `onGitHub <https://github.com/gitpython-developers/GitPython/issues?q=milestone%3A%22v1.0.2+-+Fixes%22+is%3Aclosed>`_ | ||
| * CRITICAL: `Tree.cache` was removed without replacement. It is technically impossible to change individual trees and expect their serialization results to be consistent with what *git* expects. Instead, use the `IndexFile` facilities to adjust the content of the staging area, and write it out to the respective tree objects using `IndexFile.write_tree()` instead. | ||
| 1.0.1 - Fixes | ||
| ============= | ||
| * A list of all issues can be found `onGitHub <https://github.com/gitpython-developers/GitPython/issues?q=milestone%3A%22v1.0.1+-+Fixes%22+is%3Aclosed>`_ | ||
| 1.0.0 - Notes | ||
| ============= | ||
| @@ -191,7 +191,7 @@ It follows the `semantic version scheme <http://semver.org>`_, and thus will not | ||
| - Those who support **GUI on windows** will now have to set `git.Git.USE_SHELL = True` to get the previous behaviour. | ||
| * A list of all issues can be found `onGitHub <https://github.com/gitpython-developers/GitPython/issues?q=milestone%3A%22v0.3.7+-+Fixes%22+is%3Aclosed>`_ | ||
| 0.3.6 - Features | ||
| @@ -207,11 +207,11 @@ It follows the `semantic version scheme <http://semver.org>`_, and thus will not | ||
| * Repo.working_tree_dir now returns None if it is bare. Previously it raised AssertionError. | ||
| * IndexFile.add() previously raised AssertionError when paths where used with bare repository, now it raises InvalidGitRepositoryError | ||
| * Added `Repo.merge_base()` implementation. See the `respective issue onGitHub <https://github.com/gitpython-developers/GitPython/issues/169>`_ | ||
| * `[include]` sections in git configuration files are now respected | ||
| * Added `GitConfigParser.rename_section()` | ||
| * Added `Submodule.rename()` | ||
| * A list of all issues can be found `onGitHub <https://github.com/gitpython-developers/GitPython/issues?q=milestone%3A%22v0.3.6+-+Features%22+>`_ | ||
Contributor There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. Probably could/will be added later -- but there should be a "loud" changelog entry about dropping 2.6 support for the upcoming release ContributorAuthor There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. Yes, that would be sensible. Would you like me to do that as part of this PR, or should it wait? If now, what's version will the next release be? | ||
| 0.3.5 - Bugfixes | ||
| ================ | ||
Uh oh!
There was an error while loading.Please reload this page.