Skip to content
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 DocRaptor logo #284

Merged
merged 1 commit into from Aug 11, 2020
Merged

Add DocRaptor logo #284

merged 1 commit into from Aug 11, 2020

Conversation

@AlexOverbeck
Copy link
Contributor

@AlexOverbeck AlexOverbeck commented Aug 11, 2020

In version v2.0.0 of the docraptor package we decided to drop support for Python 2. As stated in our repo, all development moving forward will only be done using Python 3.

  • Discussed dropping Python 2 support with all maintainers
  • Discussed signing the statement with all maintainers
  • Added a suitable logo if the project has one
    • Approximately square logos generally fit better than banners
    • Compressed the logo to save bandwidth (run scripts/squash-images.sh on it)
  • Checked the Netlify preview made from the pull request

Any links to any relevant tickets, articles or other resources?

https://pypi.org/project/docraptor/
DocRaptor/docraptor-python#11

In version v2.0.0 of the docraptor package we decided to drop support
for Python 2.

As stated in our repo, all development moving forward will only be done
using Python 3.

Any links to any relevant tickets, articles or other resources?
---------------------------------------------------------------
https://pypi.org/project/docraptor/
DocRaptor/docraptor-python#11

Co-authored-by: David Ronk <david@expectedbehavior.com>
@Carreau
Copy link
Member

@Carreau Carreau commented Aug 11, 2020

Nice logo ! Welcomme !

@Carreau Carreau merged commit e252235 into python3statement:master Aug 11, 2020
1 check passed
1 check passed
deploy/netlify Deploy preview ready!
Details
@Carreau
Copy link
Member

@Carreau Carreau commented Aug 11, 2020

You may want to put python_requires metadata in setup.py to make sure Python 2 user do not get a version that installs and does not work.

See this page: https://python3statement.org/practicalities/

If you already released and you have this issue, I believe PyPi now have the ability to yank releases, to make them invisible but still accessible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.