In flask_uploads.py
Change
from werkzeug import secure_filename,FileStorage
to
from werkzeug.utils import secure_filename
from werkzeug.datastructures import FileStorage
Top answer 1 of 5
160
In flask_uploads.py
Change
from werkzeug import secure_filename,FileStorage
to
from werkzeug.utils import secure_filename
from werkzeug.datastructures import FileStorage
2 of 5
35
According to this issue, it is a bug related to the current version 1.0.0 of workzeug. It's merged but not yet published in pypi.
The workaround know until now is to downgrade from werkzeug=1.0.0 to werkzeug==0.16.0
So for do that you just need run the command:
pip install -U Werkzeug==0.16.0
Looking in the release notes from werkzeug there is a version 0.16.1, but in bug report there is no evidence that using that version could be of any help.
GitHub
github.com › bigeyex › python-adminui › issues › 14
ImportError: cannot import name 'secure_filename' from 'werkzeug' · Issue #14 · bigeyex/python-adminui
September 21, 2020 - Meanwhile, the latest version of Werkzeug has moved secure_filename from being importable via werkzeug directly to now only being importable via werkzeug.utils.
Author bigeyex
werkzeug fails to import secure_filename within Docker
I have a Flask application that depends on flask-uploads, which in turn depends on werkzeug. When I run my Flask application outside of Docker it runs fine. However, if I use Docker Compose to buil... More on github.com
1
February 9, 2020bookshelf error on App Engine: "ImportError: cannot import name 'secure_filename' from 'werkzeug'"
Manifests in App Engine by showing: 502 Bad Gateway nginx Look in the logs, to see the whole traceback: Traceback (most recent call last): File "/env/lib/python3.7/site-packages/gunicorn/arbit... More on github.com
7
February 11, 2020Cannot import secure_filename from werkzeug
Python 3.5 with werkzeug 1.0.1 # export FIOWEBVIEWER_SETTINGS=$(pwd)/config.cfg; python create_tables.py Traceback (most recent call last): File "create_tables.py", line 13, in from fioweb... More on github.com
0
February 8, 2021Import Error when importing secure_filename from Werkzeug.utils : Forums : PythonAnywhere
2020-06-09 19:19:39,700: Error ... ImportError: cannot import name 'secure_filename' 2020-06-09 19:19:39,731: File "/var/www/virtualta_pythonanywhere_com_wsgi.py", line 16, in 2020-06-09 19:19:39,731: from flask_app import app as application # noqa 2020-06-09 19:19:39,731: 2020-06-09 19:19:39,731: File "/home/VirtualTA/mysite/flask_app.py", line 6, in 2020-06-09 19:19:39,731: from werkzeug.utils import ... More on pythonanywhere.com
Top answer 1 of 3
13
That exception looks like Flask-Uploads is trying to from werkzeug import secure_filename which should be from werkzeug.utils import secure_filename, as per your own code.
Going by the Flask-Uploads github repo this appears to have been fixed 12 months ago.
I'd try pip install -U flask-uploads in your virtual environment, to ensure the latest version.
EDIT:
As @mattficke points out, the PyPi version is dated, and there's not a more recent release on the repo. Turns out you can install directly based on a commit hash, so for the latest (at the time of writing this):
pip install git+https://github.com/maxcountryman/flask-uploads.git@f66d7dc
Or in a requirements.txt:
git+https://github.com/maxcountryman/flask-uploads.git@f66d7dc
Then pip install -r requirements.txt.
Which works wonders:
>>> from flask_uploads import UploadSet,configure_uploads,IMAGES,DATA,ALL
>>> # No Exception
2 of 3
3
Alternatively to above suggested solution, you can use the well maintained fork called Flask-Reuploaded.
You do not even have to change import statements, as it tries to stay compatible with the no longer well maintained Flask-Uploads.
See https://github.com/jugmac00/flask-reuploaded
Also, Flask-Reuploaded certainly provides uptodate packages on PyPI:
https://pypi.org/project/Flask-Reuploaded/
GitHub
github.com › pallets › werkzeug › issues › 1724
werkzeug fails to import secure_filename within Docker · Issue #1724 · pallets/werkzeug
February 9, 2020 - Traceback (most recent call last): File "db_setup.py", line 1, in <module> from app import db File "/usr/src/app/app.py", line 6, in <module> from flask_uploads import UploadSet, configure_uploads File "/usr/local/lib/python3.8/site-packages/flask_uploads.py", line 26, in <module> from werkzeug import secure_filename, FileStorage ImportError: cannot import name 'secure_filename' from 'werkzeug' (/usr/local/lib/python3.8/site-packages/werkzeug/__init__.py)
Author pallets
GitHub
github.com › GoogleCloudPlatform › getting-started-python › issues › 256
bookshelf error on App Engine: "ImportError: cannot import name 'secure_filename' from 'werkzeug'" · Issue #256 · GoogleCloudPlatform/getting-started-python
February 11, 2020 - bookshelf error on App Engine: "ImportError: cannot import name 'secure_filename' from 'werkzeug'"#256
Author GoogleCloudPlatform
Jugmac00
jugmac00.github.io › blogs › flask reuploaded
Flask Reuploaded | Jürgen Gmach
June 28, 2020 - It all started with this error message: File "/Projects/xxx/venv/lib/python3.7/site-packages/flask_uploads.py", line 26, in from werkzeug import secure_filename, FileStorage ImportError: cannot import name 'secure_filename' from 'werkzeug'' Trying to build my Flask application, the above error ...
GitHub
github.com › ovh › fiowebviewer › issues › 4
Cannot import secure_filename from werkzeug · Issue #4 · ovh/fiowebviewer
February 8, 2021 - # export FIOWEBVIEWER_SETTINGS=$(pwd)/config.cfg; python create_tables.py Traceback (most recent call last): File "create_tables.py", line 13, in <module> from fiowebviewer.engine.run import ( File "/opt/fiowebviewer/fiowebviewer/__init__.py", line 5, in <module> from fiowebviewer.engine.run import ( File "/opt/fiowebviewer/fiowebviewer/engine/run.py", line 38, in <module> from fiowebviewer.engine.view import * File "/opt/fiowebviewer/fiowebviewer/engine/view.py", line 21, in <module> from werkzeug import secure_filename ImportError: cannot import name 'secure_filename'
Author ovh
PythonAnywhere
pythonanywhere.com › forums › topic › 27730
Import Error when importing secure_filename from Werkzeug.utils : Forums : PythonAnywhere
It looks like your code has been written to work with werkzeug 1.0, but is running with a different version. You can upgrade the version installed for your account easily; as your website is using Python 3.6 and is not using a virtualenv, just run this in bash: ... Thanks for sharing, @enzipe2. ...
GitHub
github.com › puckel › docker-airflow › issues › 499
Incompatible with newly released Werkzeug 1.0.0 · Issue #499 · puckel/docker-airflow
February 8, 2020 - v1.0.0 of Werkzeug was just released, ... top-level attributes were removed in 1.0: Deprecate most top-level attributes provided by the werkzeug module in favor of direct imports....
Author puckel
GitHub
github.com › chrissimpkins › crypto › issues › 23
Cannot import secure_filename from werkzeug · Issue #23 · chrissimpkins/crypto
February 5, 2020 - import os.path as op from admin.views import BaseModelView from flask_admin.form.upload import FileUploadField from werkzeug import secure_filename from libs.predefined_template_parser import ParseTemplateZip from libs.utilities import get_random_string, generate_slug_code from config import BASE_PATH, TASK_DIR, TASK_FILE, ZIP_NAME class PredefinedTemplateModelView(BaseModelView): def prefix_name(obj, file_data): parts = op.splitext(file_data.filename) return secure_filename('%s%s' % parts) column_list = ('id', 'slug', 'template_code', 'name', 'description', 'created_at') form_excluded_columns
Author chrissimpkins
Stack Overflow
stackoverflow.com › questions › 70416975 › python-flask-deployed-on-heroku-importerror-cannot-import-name-secure-filen › 70418393
Python Flask (deployed on Heroku): ImportError: cannot import name 'secure_filename' from 'werkzeug' when deploying on Heroku - Stack Overflow
Copyfrom werkzeug.utils import secure_filename from werkzeug.datastructures import FileStorage
Reddit
reddit.com › r/flask › cannot deploy to heroku with flask uploads
r/flask on Reddit: Cannot deploy to Heroku with Flask Uploads
July 1, 2020 -
Hi, I'm trying to deploy my flask app to heroku and it uses the package Flask-Uploads. Though it keeps saying "ImportError: cannot import name 'secure_filename' from 'werkzeug' ". I've tried to change the import but I guess heroku just gets the lastest update to the package.
Stack Overflow
stackoverflow.com › questions › tagged › flask-reuploaded
Newest 'flask-reuploaded' Questions - Stack Overflow
I was trying to use flask-uploads module but I found in the thread: Flask-Uploads Module That I should go with flask-reuploaded module to fix the error: import name 'secure_filename' from 'werkzeug' (...
Velog
velog.io › @b8739 › from-werkzeug-import-securefilename-FileStorageImportError-cannot-import-name-securefilename
from werkzeug import secure_filename, FileStorage ImportError: cannot import name 'secure_filename'
March 28, 2021 - https://stackoverflow.com/questions/61628503/flask-uploads-importerror-cannot-import-name-secure-filename
GitHub
github.com › pallets › werkzeug › issues › 1616
Cannot import `secure_filename` · Issue #1616 · pallets/werkzeug
July 19, 2019 - In [1]: import werkzeug In [2]: werkzeug.secure_filename --------------------------------------------------------------------------- AttributeError Traceback (most recent call last) <ipython-input-2-1002393a11fd> in <module> ----> 1 werkzeug.secure_filename ~/pypath/werkzeug/__init__.py in __getattr__(self, name) 186 module = __import__(object_origins[name], None, None, [name]) 187 for extra_name in all_by_module[module.__name__]: --> 188 setattr(self, extra_name, getattr(module, extra_name)) 189 return getattr(module, name) 190 elif name in attribute_modules: AttributeError: module 'werkzeug.utils' has no attribute 'dump_cookie'
Author pallets
Beautiful Soup
tedboy.github.io › flask › generated › werkzeug.secure_filename.html
werkzeug.secure_filename — Flask API
Pass it a filename and it will return a secure version of it. This filename can then safely be stored on a regular file system and passed to os.path.join(). The filename returned is an ASCII only string for maximum portability · On windows systems the function also makes sure that the file ...
Alibaba Cloud
developer.aliyun.com › article › 1299548
flask开发导入flask_uploads包时提示"ImportError: cannot import name 'secure_filename' from 'werkzeug'"-阿里云开发者社区
August 8, 2023 - 在使用Flask开发过程中，使用Flask_uploads模块开发上传文件功能时，在项目中导入该包时，提示“ImportError: cannot import name ‘secure_filename’ from 'werkzeug”错误。
Debug Lab
debuglab.net › home › flask_uploads: importerror: cannot import name ‘secure_filename’
Flask_Uploads: Importerror: Cannot Import Name 'Secure_Filename' - Debug Lab
August 10, 2023 - It’s understandable how one can get confused because multiple Flask extension libraries deal with file uploads and names. However, the ‘secure_filename’ function doesn’t actually belong to the ‘flask_uploads’ module, which is driving the ImportError. Instead, what you want to do is import it from the ‘werkzeug.utils‘ module:
CSDN
devpress.csdn.net › python › 6304537ec67703293080b29f.html
flask_uploads: ImportError: cannot import name 'secure_filename'_python_Mangs-Python
August 23, 2022 - Traceback (most recent call last): File "app.py", line 10, in <module> from flask_uploads import UploadSet, configure_uploads, IMAGES File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/flask_uploads.py", line 26, in <module> from werkzeug import secure_filename, FileStorage ImportError: cannot import name 'secure_filename'
GitHub
github.com › pallets › flask › issues › 1547
Quickstart > File Uploads > incorrect import: secure_filename · Issue #1547 · pallets/flask
August 2, 2015 - It should be imported as: from werkzeug.utils import secure_filename Not: from werkzeug import secure_filename see http://werkzeug.pocoo.org/docs/0.10/utils/
Author pallets