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.

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

remove the token from the ICacheBuster api #1583

Merged
merged 3 commits into from
Feb 17, 2015

Conversation

mmerickel
Copy link
Member

This exposes the QueryStringCacheBuster and PathSegmentCacheBuster
public APIs alongside the md5-variants. These should be more cleanly
subclassed by people wishing to extend their implementations.

Fixes #1582.

This exposes the QueryStringCacheBuster and PathSegmentCacheBuster
public APIs alongside the md5-variants. These should be more cleanly
subclassed by people wishing to extend their implementations.
.. versionadded:: 1.6
"""
def __init__(self):
PathSegmentCacheBuster.__init__(self)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason you're calling these explicitly instead of just doing:

def __init__(self, *args, **kwargs):
    super(PathSegmentMd5CacheBuster, self).__init__(*args, **kwargs)

Should be less fragile that way as long as you make sure you pull out any kwargs/args that the class whose defining the __init__ adds.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah alright. Fixed.

@dstufft
Copy link
Contributor

dstufft commented Feb 17, 2015

Added a comment about the particular implementation, but otherwise this looks good to me.

@dstufft
Copy link
Contributor

dstufft commented Feb 17, 2015

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ICacheBuster interface leaks some implementation details
2 participants