Skip to content

Conversation

@untitaker
Copy link
Contributor

See #1135

@untitaker
Copy link
Contributor Author

cc @DasIch (now on the PR properly)

@untitaker untitaker added this to the 1.0 milestone Jun 14, 2015
@ThiefMaster
Copy link
Member

Would it make sense to show a different warning in case a flask.ext import points to an old flaskext package?

@untitaker
Copy link
Contributor Author

@ThiefMaster fixed, an additional warning is now shown. One is addressing the app dev, the other the extension dev.

@davidism
Copy link
Member

What are we waiting on to merge this?

@untitaker
Copy link
Contributor Author

Feel free to do so.

On 31 October 2015 05:02:17 CET, David Lord notifications@github.com wrote:

What are we waiting on to merge this?


Reply to this email directly or view it on GitHub:
#1484 (comment)

Sent from my phone. Please excuse my brevity.

@jeffwidman
Copy link
Contributor

Can someone rebase and then merge this?

Seems like this is all that's needed to check one of the #1182 checkboxes.

@untitaker untitaker force-pushed the ext-deprecation-new branch from 7f30cdb to 7ede661 Compare April 2, 2016 19:01
@untitaker untitaker assigned untitaker and mitsuhiko and unassigned untitaker Apr 2, 2016
@mitsuhiko
Copy link
Contributor

Let's merge this.

mcrowson pushed a commit to mcrowson/Flask-Fixtures that referenced this pull request Sep 7, 2016
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 14, 2020
willdrewesum referenced this pull request in tommyboytech/flask-mako Jul 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants