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
This means that any project that uses laika as a dependency itself will fail unless it explicitly knows to install atomicwrites itself. But on the project homepage, the author of that package recommends its deprecation:
I thought it'd be a good time to deprecate this package. Python 3 has os.replace and os.rename which probably do well enough of a job for most usecases.
So, what's the need for that atomic_write function? Could it not be simply replaced by a basic wrapper using native library calls?
The text was updated successfully, but these errors were encountered:
thank for the comment, it was added here 6e87f53 to fix a race condition, as astro_dog downloads in parallel,
just to replace it will not work, we could add locking here, would merge a PR for this
It looks like the only race condition was caused by using hatanaka.decompress_on_disk() which is no longer used. I think a temp file with random name + rename approach should work everywhere we use atomic_write() now.
This is a pretty simple issue at first glance.
You have a missing dependency in
setup.py
for the libraryatomicwrites
. The actual library calls are indownloader.py
, for example:laika/laika/downloader.py
Line 283 in 5eb0c3c
This means that any project that uses laika as a dependency itself will fail unless it explicitly knows to install
atomicwrites
itself. But on the project homepage, the author of that package recommends its deprecation:So, what's the need for that
atomic_write
function? Could it not be simply replaced by a basic wrapper using native library calls?The text was updated successfully, but these errors were encountered: