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

Add 2.7 deprecation warning #2121

Closed
Kwpolska opened this Issue Sep 26, 2015 · 3 comments

Comments

Projects
None yet
3 participants
@Kwpolska
Member

Kwpolska commented Sep 26, 2015

Should link to https://getnikola.com/blog/env-survey-results-and-the-future-of-python-27.html and it should not be too annoying.

@Kwpolska Kwpolska added this to the v7.7.2 milestone Sep 26, 2015

@Kwpolska Kwpolska referenced this issue Sep 26, 2015

Closed

Python 2.7 deprecation task list #2122

9 of 9 tasks complete
@da2x

This comment has been minimized.

Show comment
Hide comment
@da2x

da2x Sep 26, 2015

Contributor

Once per day/week when running any command? plus every time deploy is run?

Contributor

da2x commented Sep 26, 2015

Once per day/week when running any command? plus every time deploy is run?

@Kwpolska

This comment has been minimized.

Show comment
Hide comment
@Kwpolska

Kwpolska Sep 26, 2015

Member

We could do that. And have a congratulatory message if the cache/py2-last-warning file exists and the user is running Python 3.

Member

Kwpolska commented Sep 26, 2015

We could do that. And have a congratulatory message if the cache/py2-last-warning file exists and the user is running Python 3.

@ralsina ralsina self-assigned this Oct 1, 2015

@ralsina ralsina added the in progress label Oct 1, 2015

@Kwpolska

This comment has been minimized.

Show comment
Hide comment
@Kwpolska

Kwpolska Oct 8, 2015

Member

That’s finished, right?

Member

Kwpolska commented Oct 8, 2015

That’s finished, right?

@Kwpolska Kwpolska closed this Oct 8, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment