Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Atomic writes generate temp files in Dropbox

See original GitHub issue

Issue Report Checklist

[ x] Searched the issues page for similar reports
[ x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ x] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
Could not reproduce inside jupyter qtconsole (if console-related)
[ x] Tried basic troubleshooting (if a bug/error)
- [x ] Restarted Spyder
- [ x] Reset preferences with spyder --reset
- [ x] Reinstalled the latest version of Anaconda
- [ x] Tried the other applicable steps from the Troubleshooting Guide
[ x] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description

Spyder4 changes the auto-save recovery file location to the last directory a script was opened from or saved to. Un-selecting the auto-save feature and restarting Spyder does not disable the auto-save file creation.

What steps reproduce the problem?

Reset Spyder Settings
Disable autosave, restart Spyder
Open a previously saved script – example.py, from directory “usr/pyscript/”
Run the script, and find a list of “File” saved under the diretory “usr/pyscript/”, where “File” are the different auto-save versions of example.py
When ceating a new script, the default “save as” directory is also “usr/pyscript/”

What is the expected output? What do you see instead?

The autosave feature can be disabled correctly, or the autosave file to be saved in a specified directory.

Versions

Spyder version: 4.1.3
Python version: 3.7
Qt version:
PyQt version:
Operating System name/version:

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:16 (11 by maintainers)

Top GitHub Comments

3reactions

skjernscommented, Oct 2, 2020

sure! I’ll try that 😃

And I’ll also test it with other clients, such as NextCloud or OneDrive, as I would suspect that they could produce problems as well, however, as they are not so wide-spread it might not have been reported yet.

2reactions

ccordoba12commented, Jun 18, 2020

@dalthviz, I think this is related to the way we perform atomic writes and how Dropbox saves (somehow) those temporary files we use in the background.