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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update setuptools to 30.4.0 #18

Closed
wants to merge 1 commit into from

Conversation

pyup-bot
Copy link
Collaborator

There's a new version of setuptools available.
You are currently using 30.2.0. I have updated it to 30.4.0

These links might come in handy: PyPI | Changelog | Repo | Docs

Changelog

30.4.0


  • 879: For declarative config:
  • read_configuration() now accepts ignore_option_errors argument. This allows scraping tools to read metadata without a need to download entire packages. E.g. we can gather some stats right from GitHub repos just by downloading setup.cfg.
  • packages find: directive now supports fine tuning from a subsection. The same arguments as for find() are accepted.

30.3.0


  • 394 via 862: Added support for declarative package config in a setup.cfg file <http://setuptools.readthedocs.io/en/latest/setuptools.htmlconfiguring-setup-using-setup-cfg-files>_.

30.2.1


  • 850: In test command, invoke unittest.main with
    indication not to exit the process.

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 馃

@coveralls
Copy link

coveralls commented Dec 10, 2016

Coverage Status

Coverage remained the same at 96.296% when pulling 5dbaa6c on pyup-update-setuptools-30.2.0-to-30.4.0 into c437e5f on master.

@pyup-bot
Copy link
Collaborator Author

Closing this in favor of #19

@pyup-bot pyup-bot closed this Dec 11, 2016
@illagrenan illagrenan deleted the pyup-update-setuptools-30.2.0-to-30.4.0 branch December 11, 2016 23:50
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.

None yet

2 participants