-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Don't create or check permissions on .plotly config directory until it a write operation is requested #1076
Milestone
Comments
Done in #1195 |
I think this is still a problem.
I had to re-raise in the except-catch block of |
I want to make warnings into errors in my tests. ( |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now we always run the check to make sure read/write permissions are available for the user's
.plotly
directory. We do it with a call totools.ensure_local_plotly_files()
on the import ofplotly/plotly/plotly.py
. Becuase of our recursive imports this package is always imported and so we always check for these permissions.Because of use-cases like that in #1068, where a bunch of jobs are running on a cluster and are just doing offline plotting, we shouldn't do this check unless we're actually using the
plotly.plotly
package to communicate with the plot.ly servers.The text was updated successfully, but these errors were encountered: