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

Preserve order of backends in BACKENDSCACHE #1004

Closed
wants to merge 1 commit into from

Conversation

tsouvarev
Copy link

When I load backends with load_backends, it returns BACKENDSCACHE, which is unordered dict.
It's very unhandy to order result later, so it would be nice, if BACKENDSCACHE kept order of backends passed as argument

When I load backends with `load_backends`, it returns `BACKENDSCACHE`, which is unordered `dict`.
It's very unhandy to order result later, so it would be nice, if `BACKENDSCACHE` kept order of backends passed as argument
@tsouvarev
Copy link
Author

Hello @omab do you need anything else to merge this request?

@omab
Copy link
Owner

omab commented Sep 15, 2016

@tsouvarev, the PR looks good, but I'm in the middle of splitting the application in smaller pieces (core, django, flask, etc), I'll port any PR to the corresponding place once I've finish the split/migration

@tsouvarev
Copy link
Author

thanks, looking forward to that

@omab omab force-pushed the master branch 2 times, most recently from 1078c07 to de9f179 Compare December 3, 2016 14:23
@omab
Copy link
Owner

omab commented Dec 4, 2016

I've ported this PR into social-core.

Thanks!

@omab omab closed this Dec 4, 2016
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.

2 participants