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

Add --use-fuzzy option to compilemessages command. #978

Closed
wants to merge 30 commits into from

Conversation

Projects
None yet
@bak1an
Copy link
Contributor

commented Mar 30, 2013

Refs #18714

dbrgn and others added some commits Jun 13, 2013

Merge pull request #1265 from dbrgn/mixin_order
Fixed order of base classes in CBV mixin docs
Merge pull request #1270 from tomchristie/remove-incorrect-content-ty…
…pe-test-client

Remove incorrect CONTENT_TYPE header from GET and HEAD requests
Fixed #20528 -- regression in select_related join promotion
The join used by select_related was incorrectly INNER when the query
had an ORed filter for nullable join that was trimmed away. Fixed this
by forcing the join type to LOUTER even when a join was trimmed away
in ORed queries.
Merge pull request #1272 from chicheng/addition-http-status-codes
Fixed #20598 -- Add new HTTP status codes defined in rfc6585
Merge pull request #1271 from batisteo/ticket-20565
Fixed #20565 -- Added template examples for GCBV.
Fixed #20603 -- Made the test suite faster.
By avoiding to run syncdb with the full set of test models.

Thanks Anssi for the idea.
Fixed #20604 - Fixed file example in docs.
Thanks Chris Lasher for the report.
Fixed #20599 -- Changed wording of ValueError raised by _load_library
The _load_library method on BasePasswordHasher turns ImportErrors
into ValueErrors, this masks ImportErrors in the algorithm library.
Changed it to a clearer worded error message that includes
the ImportError string.
@jezdez

This comment has been minimized.

Copy link
Contributor

commented on 2a6a320 Jun 15, 2013

@toastdriven This needs a ..versionadded:: 1.6 directive

toastdriven and others added some commits Jun 15, 2013

Fixed #20583 -- ORM always uses setup_joins() for join generation
There were a couple of places which used Query.join() directly. By
using setup_joins() in these places the code is more DRY, and in
addition there is no need to directly call field.get_joining_columns()
unless the field is the given join_field from get_path_info(). This
makes it easier to make sure a ForeignObject subclass generates joins
correctly in all cases.
@jacobvalenta

This comment has been minimized.

Copy link

commented on 9e50833 Jun 16, 2013

Thank you so much, just ran into the need to do this.

bmispelon and others added some commits Jun 15, 2013

@bak1an

This comment has been minimized.

Copy link
Contributor Author

commented Jun 17, 2013

rebased

@timgraham

This comment has been minimized.

Copy link
Member

commented Feb 8, 2014

This PR needs to be reworked so it doesn't include unrelated commits (caused by when someone accidentally force pushed to (django/django)). It also needs updates for version 1.7.

@timgraham timgraham closed this Feb 8, 2014

@bak1an

This comment has been minimized.

Copy link
Contributor Author

commented Feb 8, 2014

@timgraham
NP, i will rebase this onto current master over a weekend and open new PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.