Skip to content
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.

Sign up for GitHub

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

Jump to bottom

document that when falling back to AlwaysRunner, autoclean() stops working #48

Open
GoogleCodeExporter opened this issue Mar 26, 2015 · 1 comment
Open

document that when falling back to AlwaysRunner, autoclean() stops working #48

GoogleCodeExporter opened this issue Mar 26, 2015 · 1 comment
Labels
auto-migrated docs unclear

Comments

@GoogleCodeExporter
Copy link 

AlwaysRunner is meant to be a fallback in case none of the dependency tracking 
methods can be used. However, what is not mentioned is that this fallback also 
means that autoclean() stops working entirely.

This means that if one wishes to write a project that would work also with 
AlwaysRunner, cleanup must be written manually.

Original issue reported on code.google.com by nuutti.k...@gmail.com on 9 Jul 2013 at 12:07
@GoogleCodeExporter
Copy link
Author

Original comment by simon.al...@gmail.com on 13 Sep 2013 at 12:45

  • Changed state: Accepted
  • Added labels: Component-Docs
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated docs unclear
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chriscz @GoogleCodeExporter