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 missing trove classifiers with setup-py-upgrade and setup-cfg-fmt #223

Closed
wants to merge 2 commits into from

Conversation

graingert
Copy link

I noticed there were no supported python versions (py3.6, py3.7 and py3.8) in the pypi metadata

pipx run setup-cfg-fmt --min-py3-version=3.3 --max-py-version=3.8 -- setup.cfg
Comment on lines +26 to +28
Programming Language :: Python :: 3.6
Programming Language :: Python :: 3.7
Programming Language :: Python :: 3.8
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these are the only supported python versions

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3.9 support is in #204

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we really still support Python 3.3 and 3.4? They're long-obsolete, Spyder itself dropped them ages ago.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be resolved in PR #208 ; you'll need to re-run your tooling once that's merged since it changes a bunch of the metadata

@CAM-Gerlach CAM-Gerlach changed the title add missing trove classifiers with setup-py-upgrade and setup-cfg-fmt Add missing trove classifiers with setup-py-upgrade and setup-cfg-fmt Mar 19, 2021
Copy link
Member

@CAM-Gerlach CAM-Gerlach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this, and sorry for the long delay! Just a few minor comments.

Comment on lines +26 to +28
Programming Language :: Python :: 3.6
Programming Language :: Python :: 3.7
Programming Language :: Python :: 3.8
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we really still support Python 3.3 and 3.4? They're long-obsolete, Spyder itself dropped them ages ago.

'Programming Language :: Python :: 3.4',
'Programming Language :: Python :: 3.5']
)
setup(version=version_ns['__version__'])
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The version attr can be specified declaratively, as e.g. I do here, so this last bit of dynamic code in the setup.py can be eliminated

maintainer = Gonzalo Peña-Castellanos
maintainer_email = goanpeca@gmail.com
license = MIT
license_file = LICENSE.txt
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

license_file is deprecated and license_files should be used instead, and in any case LICENSE.txt will be included automatically, so this can just be removed.

Suggested change
license_file = LICENSE.txt

@ccordoba12
Copy link
Member

ccordoba12 commented Aug 23, 2021

Thanks for your help with this @graingert. We already updated our classifiers in 1.10.0 and don't accustom to declare metadata in setup.cfg in our projects.

So we decided to close this one, but thanks for your interest in improving this project.

@ccordoba12 ccordoba12 closed this Aug 23, 2021
@graingert
Copy link
Author

Is there a reason you prefer the legacy metadata format? @ccordoba12

@graingert graingert deleted the setup-py-upgrade branch August 23, 2021 17:00
@ccordoba12
Copy link
Member

It's just a matter of being used to do that in all our projects. So we prefer to keep things like that for now.

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

Successfully merging this pull request may close these issues.

3 participants