-
Notifications
You must be signed in to change notification settings - Fork 48
name not set for CacheRegion #27
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
Comments
Michael Bayer (zzzeek) wrote: any chance I can get a quick pullreq on this one? |
Wichert Akkerman (wichert) wrote: If you were using git I would have sent one, but I'm afraid I've never used mercurial. |
Michael Bayer (zzzeek) wrote: if it were BZR I'd understand :) ... though the mercurial flow here is pretty much identical to git.... if bitbucket would allow me to swap the repo i could do that for the dogpile products, since im generally defaulting to git now. |
Wichert Akkerman (wichert) wrote: I think I have git-remote-hg working (included as contrib script with git) on my laptop, I could give that a try to make a pull request tonight. Might also be a useful tool if you want to convert at some point. |
Changes by Michael Bayer (zzzeek):
|
Migrated issue, originally created by Wichert Akkerman (wichert)
The documentation for CacheRegion states that the name parameter is set on the caching region. The constructor forgets to do that though, leaving the region without a cache attribute.
The text was updated successfully, but these errors were encountered: