You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I bumped up to a little bit unexpected behaviour: If you import dash, any file called test.py in the same folder will be imported, causing sometimes unexpected behaviour.
MWE
Create empty folder with app.py and test.py
# test.pyprint('In test.py')
# app.pyprint('1 in app.py')
importdashprint('2 in app.py')
Output
PS C:\tmp\test_dash> python .\app.py
1 in app.py
In test.py
2 in app.py
What would be expected?
One could expect that import dash would not run any files called test.py.
This is an issue with the future package that's used for py2/py3 compatibility, not with dash, you may want to pick it up with them. It tries to load a number of modules when importing future.moves defined here:
Question is, with py2 no longer being maintained, does dash still need to use this package, eg here?
Duplicate of #1143
I'm afraid we're not quite ready to drop py2 support yet, but #1143 points to some ways we can at least make things work better, though we probably can't prevent future from importing test and org.
I bumped up to a little bit unexpected behaviour: If you import dash, any file called
test.py
in the same folder will be imported, causing sometimes unexpected behaviour.MWE
app.py
andtest.py
Output
What would be expected?
One could expect that
import dash
would not run any files calledtest.py
.Versions
The text was updated successfully, but these errors were encountered: