-
Notifications
You must be signed in to change notification settings - Fork 17
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
apify run --purge
doesn't purge
#545
Comments
Hmm, does the python SDK purge by default? It should. cc @vdusek |
I don't think so. I am used to running |
Hmm, this was the old sdk v2 behavior, I don't recall if python SDK was released before or after crawlee, but we changed this with crawlee and SDK v3 - the storages are purged by default unless you opt-out of it via env var (which the CLI sets via cc @vladfrangu, we should add the explicit purging for python projects (to both 0.x and 1.0) as it will take some time for the python tooling to catch up. |
Opened apify/crawlee-python#87 to track the change on python's end. |
Fix for this is
|
Closes #545 Will push the same fix to the 0.19.x branch and release (I've tested it locally and it works as intended now)
apify run --purge
doesn't purge, even tried withnpx apify-cli@1.0.0-beta.42 run --purge
How to reproduce?
Run:
but now if you run the following command again:
it won't scrape anything, because the purge didn't happen.
The text was updated successfully, but these errors were encountered: