-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Fully deprecate werkzeug.script #1079
Comments
Can I take this? It looks like some of the example still use ‘from werkzeug import script‘. What should be use instead? |
Click is recommended. |
Where should I add it to requirements? |
No, this would be about removing the module and - if it's referenced in the docs - mention |
I think Antonio is talking about the examples folder in the Werkzeug directory.
Since that one doesn't have a setup.py for each example, I think it's fine to
just not define the dependency anywhere. Perhaps a short notice in
examples/README would suffice.
…On Mon, Mar 27, 2017 at 03:23:20PM -0700, Adrian wrote:
No, this would be about removing the module and - if it's referenced in the docs - mention `click` there instead. There is no need/reason to make click a hard requirement of werkzeug.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#1079 (comment)
|
Yes, I'm sorry, I was talking about the examples, I didn't mention it. I'll work on this 😁 |
@untitaker I think this one can be closed now 👌 |
werkzeug.script has been deprecated since 2011 and 0.12 now shows huge warnings, I think it's time to remove it.
The text was updated successfully, but these errors were encountered: