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

Update __init__.py #51

Merged
merged 1 commit into from
Mar 20, 2015
Merged

Update __init__.py #51

merged 1 commit into from
Mar 20, 2015

Conversation

pjryan126
Copy link
Contributor

alembic version now includes parts that are not integers (e.g., 0.7.5.post1). This change will prevent the code from trying to convert non-integer values to integers.

alembic version now includes parts that are not integers (e.g., 0.7.5.post1). This change will prevent the code from trying to convert non-integer values to integers.
@miguelgrinberg
Copy link
Owner

Thanks!

miguelgrinberg added a commit that referenced this pull request Mar 20, 2015
@miguelgrinberg miguelgrinberg merged commit a9413d4 into miguelgrinberg:master Mar 20, 2015
robyoung added a commit to Crown-Commercial-Service/digitalmarketplace-api that referenced this pull request Mar 25, 2015
bsmithgall added a commit to bsmithgall/cookiecutter-flask that referenced this pull request Apr 13, 2015
Flask-Migrate was recently patched to version 1.3.1 because [alembic versions can now include parts that are not integers](miguelgrinberg/Flask-Migrate#51).

Requiring Flask-Migrate 1.3.0 installs a version of alembic that results in the following error message on startup:

`ValueError: invalid literal for int() with base 10: 'post2'`

Changing the requirements to install Flask-Migrate 1.3.1 fixes this problem.
bsmithgall added a commit to bsmithgall/cookiecutter-flask that referenced this pull request Apr 14, 2015
Flask-Migrate was recently patched to version 1.3.1 because [alembic versions can now include parts that are not integers](miguelgrinberg/Flask-Migrate#51).

Requiring Flask-Migrate 1.3.0 installs a version of alembic that results in the following error message on startup:

`ValueError: invalid literal for int() with base 10: 'post2'`

Changing the requirements to install Flask-Migrate 1.3.1 fixes this problem.
bsmithgall added a commit to bsmithgall/cookiecutter-flask that referenced this pull request Apr 14, 2015
Flask-Migrate was recently patched to version 1.3.1 because [alembic versions can now include parts that are not integers](miguelgrinberg/Flask-Migrate#51).

Requiring Flask-Migrate 1.3.0 installs a version of alembic that results in the following error message on startup:

`ValueError: invalid literal for int() with base 10: 'post2'`

Changing the requirements to install Flask-Migrate 1.3.1 fixes this problem.
wdm0006 pushed a commit to wdm0006/cookiecutter-flask that referenced this pull request Oct 28, 2015
Flask-Migrate was recently patched to version 1.3.1 because [alembic versions can now include parts that are not integers](miguelgrinberg/Flask-Migrate#51).

Requiring Flask-Migrate 1.3.0 installs a version of alembic that results in the following error message on startup:

`ValueError: invalid literal for int() with base 10: 'post2'`

Changing the requirements to install Flask-Migrate 1.3.1 fixes this problem.
curest0x1021 added a commit to curest0x1021/cookiecutter-flask that referenced this pull request May 17, 2019
Flask-Migrate was recently patched to version 1.3.1 because [alembic versions can now include parts that are not integers](miguelgrinberg/Flask-Migrate#51).

Requiring Flask-Migrate 1.3.0 installs a version of alembic that results in the following error message on startup:

`ValueError: invalid literal for int() with base 10: 'post2'`

Changing the requirements to install Flask-Migrate 1.3.1 fixes this problem.
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