-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop Python 2.6 #165
Comments
Afaik, the places where we have fixes for 2.6 are: |
Given that we have relaxed the python-markdown requirement on pythons greater than 2.6 I don't see a huge rush to do this. We may want to do this for python-markdown version 3 or mkdocs version 1 Changing the milestone to think about this later. |
I am going to start moving towards this. Support will be dropped in MkDocs 1.0. We will display a warning to users in 0.15 and above if they are running Python 2.6. |
👍 |
Mock also now doesn't support Python 2.6. #688 |
MkDocs most likley will no longer run on Python 2.6. All relevant tests have been removed. Closes mkdocs#165.
MkDocs most likley will no longer run on Python 2.6. All relevant tests have been removed. Closes mkdocs#165.
MkDocs most likley will no longer run on Python 2.6. All relevant tests have been removed. Closes #165.
MkDocs most likley will no longer run on Python 2.6. All relevant tests have been removed. Closes mkdocs#165.
MkDocs most likley will no longer run on Python 2.6. All relevant tests have been removed. Closes #165.
We should aim to drop Python 2.6, probably not in the next release, but the one after, or before 1.0 at least.
Doing this will involve:
The text was updated successfully, but these errors were encountered: