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

Python: Flask: Fix: Update setup.py to match requirements.txt #4205

Merged

Conversation

GuillaumeSmaha
Copy link
Contributor

In my previous PR (049f69c), I forgot to update setup.py to match requirements.txt, this PR aims to align content of setup.py with requirements.txt

PR checklist

  • Read the contribution guidelines.
  • If contributing template-only or documentation-only changes which will change sample output, build the project before .
  • Run the shell script(s) under ./bin/ (or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run ./bin/{LANG}-petstore.sh, ./bin/openapi3/{LANG}-petstore.sh if updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc).
  • File the PR against the correct branch: master, 4.1.x, 5.0.x. Default: master.
  • Copy the technical committee to review the pull request if your PR is targeting a particular programming language.
    @taxpon (2017/07) @frol (2017/07) @mbohlool (2017/07) @cbornet (2017/09) @kenjones-cisco (2017/11) @tomplus (2018/10) @Jyhess (2019/01)

@wing328 wing328 added this to the 4.2.0 milestone Oct 22, 2019
@wing328 wing328 merged commit 5d7bb17 into OpenAPITools:master Oct 22, 2019
@GuillaumeSmaha GuillaumeSmaha deleted the fix_range_version_setup.py branch October 22, 2019 02:29
@wing328
Copy link
Member

wing328 commented Oct 31, 2019

@GuillaumeSmaha thanks for the PR, which has been included in v4.2.0 release: https://twitter.com/oas_generator/status/1189824932345069569

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

Successfully merging this pull request may close these issues.

2 participants