Re: [Django] #29331: Model fields where the field name is shadowed by Python property aren't saved (was: Model fields where the python attribute name does not match the db column are not saved)

ch? If not, I suppose the restriction could at least be documented. -- Ticket URL: <https://code.djangoproject.com/ticket/29331#comment:4> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed

Re: [Django] #29317: filter keyword undocumented in PostgreSQL aggregate functions

ticket/29317#comment:3> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails f

Re: [Django] #29281: In some cases i18n set_language does not change url language

`tests/view_tests/tests/test_i18n.py` that demonstrates the issue would be great. -- Ticket URL: <https://code.djangoproject.com/ticket/29281#comment:6> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message bec

Re: [Django] #29331: Model fields where the field name is shadowed by Python property aren't saved

ct.com/ticket/29331#comment:5> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving e

Re: [Django] #29331: Model fields where the field name is shadowed by Python property aren't saved

athes): I suspect this is related, since the root cause is a change in {{{get_deferred_attributes}}} https://github.com/jpwatts/django-positions/issues/49 -- Ticket URL: <https://code.djangoproject.com/ticket/29331#comment:6> Django <https://code.djangoproject.com/> The

Re: [Django] #29331: Model fields where the field name is shadowed by Python property aren't saved

the will be present in `__dict__` without breaking a lot of stuff. -- Ticket URL: <https://code.djangoproject.com/ticket/29331#comment:7> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are sub

[Django] #29332: AdminReadOnly field accepts the optional argument model_admin but treats it as non-optional

does not error, and sets the `empty_value_display` to the empty string. Relevant file: https://github.com/django/django/blob/master/django/contrib/admin/helpers.py Cheers. -- Ticket URL: <https://code.djangoproject.com/ticket/29332> Django <https://code.djangoproject.com/> The Web f

Re: [Django] #29332: AdminReadonlyField accepts the optional argument model_admin but treats it as non-optional (was: AdminReadOnly field accepts the optional argument model_admin but treats it as non

Ticket URL: <https://code.djangoproject.com/ticket/29332#comment:1> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscr

Re: [Django] #29332: AdminReadonlyField accepts the optional argument model_admin but treats it as non-optional

ror > since AdminReadOnly calls: `model_admin.get_empty_value_display()`. > > My expected behaviour is that it does not error, and sets the > `empty_value_display` to the empty string. > Relevant file: > https://github.com/django/django/blob/master/django/contrib/admin/helper

Re: [Django] #29331: Model fields where the field name is shadowed by Python property aren't saved

s (by Tim Graham): * status: new => closed * resolution: => invalid -- Ticket URL: <https://code.djangoproject.com/ticket/29331#comment:8> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because yo

[Django] #29333: Returning a file with an invalid name throws an error that does not show up in the logs

d not appear in Sentry. It did not appear in any log file, neither. This was bad because I only noticed when a user complained. Also, it made debugging quite tricky. Please make sure that such errors appear in the logs. -- Ticket URL: <https://code.djangoproject.com/ticket/29333> Dj

Re: [Django] #29333: Returning a file with an invalid name throws an error that does not show up in the logs

Comment: Please provide steps to reproduce the problem and confirm the issues exists on the most recent release of Django. Django 1.8 is several years old and unsupported. -- Ticket URL: <https://code.djangoproject.com/ticket/29333#comment:1> Django <https://code.djangoproject.com/>

Re: [Django] #29324: Change Settings to raise ImproperlyConfigured on SECRET_KEY; not initialization

ed and not set. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29324#comment:4> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates"

[Django] #29334: Update pypi.python.org links to point to pypi.org

for now, over time the old URLs will start to look weird to folks new to Python). -- Ticket URL: <https://code.djangoproject.com/ticket/29334> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are s

Re: [Django] #29334: Update pypi.python.org links to point to pypi.org

: Unreviewed => Ready for checkin Comment: [https://github.com/django/django/pull/9882 PR] -- Ticket URL: <https://code.djangoproject.com/ticket/29334#comment:1> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message

Re: [Django] #29334: Update pypi.python.org links to point to pypi.org

g URLs to pypi.org. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29334#comment:2> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django up

Re: [Django] #29334: Update pypi.python.org links to point to pypi.org

f7cb529c0478b4c4d9 from master }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29334#comment:3> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "

Re: [Django] #29175: makemessages doesn't parse ES6 template strings (was: makemessages does parse ES6 template strings)

s: 0 | Patch needs improvement: 0 Easy pickings: 0 |UI/UX: 0 --+ -- Ticket URL: <https://code.djangoproject.com/ticket/29175#comment:6> Django <https://code.djangoproject

[Django] #29335: changed default pastebin link to dpaste.de

but the fixes have not been completed. Rather than engage in anything so elaborate, this pull request simply changes the default away from dpaste.com to dpaste.de, which is the site used by Django IRC. I don't profess to know anything about pastebin.com or dpaste.com other than the clear

Re: [Django] #29335: changed default pastebin link to dpaste.de

"django_technical_500.html" added. -- Ticket URL: <https://code.djangoproject.com/ticket/29335> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django upd

[Django] #29336: No docs for circular inheritance

this, or at least none that appear to be easy to find. This is a very useful feature. It allows a lot of power and flexibility without the need to create many template overrides. Before Django properly supported this, most of us used: https://github.com/stephenmcd/django-overextends The docs

Re: [Django] #29336: No docs for circular inheritance

=> Adrian Turjak * status: new => assigned Comment: Fixed by: https://github.com/django/django/pull/9884 -- Ticket URL: <https://code.djangoproject.com/ticket/29336#comment:1> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You rec

Re: [Django] #28600: Add prefetch related support to RawQuerySet

: 0 => 1 Comment: Patch is looking good. Just needs some adjustments to the documentation changes. -- Ticket URL: <https://code.djangoproject.com/ticket/28600#comment:19> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You receiv

Re: [Django] #28600: Add prefetch related support to RawQuerySet

arate PR. Did that happen? (I [https://github.com/django/django/pulls?utf8=✓&q=is%3Apr+author%3Auadnan can't see another PR by Adnan]) I ask because the warning in [https://github.com/django/django/blob/7a22d9f75125e3cfbea0979a876efe4634f6fe05/docs/topics/db/sql.txt#L88-L97 docs/db/

Re: [Django] #27391: Support unittest.TestCase.debug() method

Ticket URL: <https://code.djangoproject.com/ticket/27391#comment:10> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscr

[Django] #29337: __len__ & __bool__ support in RawQueryset

results caching in RawQueryset. https://code.djangoproject.com/ticket/28600 adds support for that. `__len__` & `__bool__` supports need to be added for `RawQueryset` -- Ticket URL: <https://code.djangoproject.com/ticket/29337> Django <https://code.djangoproject.com/> The Web fram

Re: [Django] #29337: __len__ & __bool__ support in RawQueryset

nges (by Adnan Umer): * status: new => assigned * owner: nobody => Adnan Umer -- Ticket URL: <https://code.djangoproject.com/ticket/29337#comment:1> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this m

Re: [Django] #28600: Add prefetch related support to RawQuerySet

[comment:20 Carlton Gibson]: > Did that happen? (I [https://github.com/django/django/pulls?utf8=✓&q=is%3Apr+author%3Auadnan can't see another PR by Adnan]) I havn't yet opened any new PR for that. I was just waiting on approval/merge of my existing ticket. Once that is done I'l

Re: [Django] #28600: Add prefetch related support to RawQuerySet

=> 0 Comment: Unchecking "Needs Documentation" to have PR reviewed again after doing requested changes. -- Ticket URL: <https://code.djangoproject.com/ticket/28600#comment:22> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadline

Re: [Django] #29174: makemessages does not find translations in Python 3.6 formatted string literals

can't be translated. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29174#comment:4> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "

Re: [Django] #29175: makemessages doesn't parse ES6 template strings

}} -- Ticket URL: <https://code.djangoproject.com/ticket/29175#comment:7> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group.

Re: [Django] #29174: makemessages does not find translations in Python 3.6 formatted string literals

d93f798151f712064394652cabed from master }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29174#comment:5> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "

Re: [Django] #29175: makemessages doesn't parse ES6 template strings

abed from master }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29175#comment:8> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" grou

Re: [Django] #29174: makemessages does not find translations in Python 3.6 formatted string literals

d93f798151f712064394652cabed from master }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29174#comment:6> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "

Re: [Django] #29175: makemessages doesn't parse ES6 template strings

abed from master }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29175#comment:9> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" grou

Re: [Django] #29175: makemessages doesn't parse ES6 template strings

9faab4caf11fca000b07f0181. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29175#comment:10> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django

Re: [Django] #29174: makemessages does not find translations in Python 3.6 formatted string literals

ts commit 8b4798c8d31b3cd9faab4caf11fca000b07f0181. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29174#comment:7> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the G

Re: [Django] #29336: No docs for circular inheritance

stage: Unreviewed => Accepted Comment: This would make a good addition to the [https://docs.djangoproject.com/en/2.0/howto/overriding-templates/ Overriding Templates How-To]. -- Ticket URL: <https://code.djangoproject.com/ticket/29336#comment:2> Django <https://code.djangopro

Re: [Django] #29303: non_atomic_requests decorator alters _non_atomic_requests attribute of original function

_requests(view, using) }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29303#comment:4> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django up

Re: [Django] #3006: generic relations do not act as expected in a filter/get

-+- Changes (by Carlton Gibson): * stage: Accepted => Ready for checkin Comment: Patch looks good. Not 100% sure it's needed given `GenericRelation` is already available. -- Ticket URL: <https://code.djangoproject.com/ticket/3006#comment:22> Django <https://code.

Re: [Django] #28600: Add prefetch related support to RawQuerySet

-+- Changes (by Carlton Gibson): * stage: Accepted => Ready for checkin -- Ticket URL: <https://code.djangoproject.com/ticket/28600#comment:23> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you

Re: [Django] #29337: __len__ & __bool__ support in RawQueryset

tage: Unreviewed => Accepted Comment: Follow on from #28600 -- Ticket URL: <https://code.djangoproject.com/ticket/29337#comment:2> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed t

Re: [Django] #28919: Add support for Common Table Expression (CTE) queries

ables`, and there is a secret (undocumented, experimental API) way to do a left outer join. -- Ticket URL: <https://code.djangoproject.com/ticket/28919#comment:9> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this messag

Re: [Django] #27629: Inconsistent check of allow_relation in ForwardManyToOneDescriptor.__set__

-+- Changes (by Asif Saifuddin Auvi): * needs_docs: 0 => 1 -- Ticket URL: <https://code.djangoproject.com/ticket/27629#comment:8> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this mess

Re: [Django] #3006: generic relations do not act as expected in a filter/get

-+- Comment (by Tim Graham): I'd lean toward a wontfix. In particular, making changes in `django/db/models/sql/query.py` for a contrib app doesn't look like a good separation of concerns. Is there a downside to the alternative of adding the `GenericRelation`? -- Ticket U

Re: [Django] #29122: Add a better font for Persian/Farsi to the admin

: nobody => Kelly Hogan * status: new => assigned -- Ticket URL: <https://code.djangoproject.com/ticket/29122#comment:2> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to

[Django] #29338: Can't use OuterRef in union Subquery

ce to an outer query and may only be used in a subquery. }}} I get the same error with this statement: {{{ return self.annotate( owner=Subquery((cls | ots).values('owner')[:1]) ) }}} (As an aside, I also get an error when I try to apply an `order_by`

Re: [Django] #3006: generic relations do not act as expected in a filter/get

-+- Changes (by Tim Graham): * status: new => closed * resolution: => wontfix Comment: Feel free to continue the [https://groups.google.com/d/topic/django- developers/bCUDl7MlkOA/discussion discussion on django-developers] if there's some motivati

Re: [Django] #29338: Can't use OuterRef in union Subquery

some sensible SQL for this queryset is possible? -- Ticket URL: <https://code.djangoproject.com/ticket/29338#comment:1> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Googl

Re: [Django] #29122: Add a better font for Persian/Farsi to the admin

, I think it's a bit premature to assign the ticket as it has "someday/maybe" status. The first step is to propose a solution (if a change in Django needs to be made at all) on the DevelopersMailingList as I suggested in comment 1. -- Ticket URL: <https://code.djangoprojec

Re: [Django] #29335: changed default pastebin link to dpaste.de

=> closed * resolution: => wontfix * component: contrib.admin => Error reporting Comment: I don't understand the benefit of the proposed change. The topic for #django says "do not use pastebin.com!" -- which is different from dpaste.com that the debug page uses. Anyw

Re: [Django] #23890: Deprecation warning with numpy 1.8+

; a917a560]: {{{ #!CommitTicketReference repository="" revision="a917a5601f145042f31d0e2011bc41c2a3aaea7c" Refs #23890 -- Removed numpy deprecation warning silencing. Obsolete since numpy 1.12.0. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/23890#comment:4> Django <https://cod

Re: [Django] #4848: Allow inline fields to be "mixed in" with the models' own fields

ld require checking fieldsets instead of inlines. I could implement this feature. -- Ticket URL: <https://code.djangoproject.com/ticket/4848#comment:13> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message becau

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

): * needs_better_patch: 0 => 1 -- Ticket URL: <https://code.djangoproject.com/ticket/19580#comment:24> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups

Re: [Django] #29049: Add slicing notation to F expressions

): * needs_better_patch: 0 => 1 Comment: Comments on PR. -- Ticket URL: <https://code.djangoproject.com/ticket/29049#comment:9> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google

Re: [Django] #8936: Add view (read-only) permission to admin

I will review over the next week with a possible inclusion (or not) in 2.1 in mind. -- Ticket URL: <https://code.djangoproject.com/ticket/8936#comment:45> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message beca

Re: [Django] #29212: Redirect loop with @permission_required and redirect_authenticated_user

ct loop if @permission_required used with redirect_authenticated_user. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29212#comment:4> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscr

Re: [Django] #28574: Add a QuerySet.explain() method

xed #28574 -- Added QuerySet.explain(). }}} -- Ticket URL: <https://code.djangoproject.com/ticket/28574#comment:13> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Gro

[Django] #29339: Add result caching to RawQuerySet / QuerySet.raw()

()` requires result caching to avoid performance problems as discussed in ticket:22349#comment:4. -- Ticket URL: <https://code.djangoproject.com/ticket/29339> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message bec

Re: [Django] #29338: Can't use OuterRef in union Subquery

have, especially in the discussion of CTEs (common table expressions). -- Ticket URL: <https://code.djangoproject.com/ticket/29338#comment:2> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are

Re: [Django] #29339: Add result caching to RawQuerySet / QuerySet.raw()

erySet. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29339#comment:1> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates"

Re: [Django] #29337: Add __len__() & __bool__() to RawQueryset (was: __len__ & __bool__ support in RawQueryset)

#28600 adds support for results caching. -- Comment: [https://github.com/django/django/pull/9887 PR] -- Ticket URL: <https://code.djangoproject.com/ticket/29337#comment:3> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You rec

Re: [Django] #22349: RawQuerySet doesn't implement __len__, __bool__

29339 added results caching to `RawQuerySet` and #29337 added `__len__()` and `__bool__()`. -- Ticket URL: <https://code.djangoproject.com/ticket/22349#comment:14> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this messag

Re: [Django] #29337: Add __len__() & __bool__() to RawQueryset

047" Fixed #29337 -- Added __len__() & __bool__() to RawQuerySet. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29337#comment:4> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because

Re: [Django] #28600: Add prefetch related support to RawQuerySet

0dac546" Fixed #28600 -- Added prefetch_related() support to RawQuerySet. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/28600#comment:24> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because

Re: [Django] #27391: Support unittest.TestCase.debug() method

:10 Asif Saifuddin Auvi]: Patch was improved as per Tim Martin's notes [https://github.com/django/django/pull/7436/commits/7ec5fae434f01ebef77e2d7bb2544bf5314d99bf in commit 7ec5fae]. I added a sketch for release note mention in [https://github.com/django/django/pull/7436#issuecomment-3

[Django] #29340: "cache.get_or_set()" extra hits on database

tion cache.set('event_location_eID{}'.format(event.pk),output,None) return output }}} there will be no more unnecessarily SQL queries. I'm using **django-debug-toolbar** to monitor my database requests and the information about queries is based on the statistics

Re: [Django] #29340: "cache.get_or_set()" extra hits on database

che.get('event_location_eID{}'.format(event.pk)) > if output is None: > output = event.location > cache.set('event_location_eID{}'.format(event.pk),output,None) > > return output > }}} > > there will be no more unnecessarily SQL que

Re: [Django] #29340: "cache.get_or_set()" extra hits on database

patch: 0| Needs documentation: 0 Needs tests: 0| Patch needs improvement: 0 Easy pickings: 0|UI/UX: 0 -+- Comment (by Tim Graham): Can you explain why

Re: [Django] #29340: "cache.get_or_set()" extra hits on database

ment:2 Tim Graham]: > Can you explain why Django is at fault? I haven't debugged your project but I think it's more likely that you've made a mistake somewhere. django is expected to use cached data and not to create sql queries when the required cache keys are present. as I

Re: [Django] #29340: "cache.get_or_set()" extra hits on database

rtChannels our support channels] if you need help confirming whether or not Django is at fault. -- Ticket URL: <https://code.djangoproject.com/ticket/29340#comment:4> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received thi

Re: [Django] #29313: Add documentation for how to use F() expressions in combination with nulls_last

Fixed #29313 -- Doc'd how to use F() to sort null values. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29313#comment:3> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscr

Re: [Django] #29313: Add documentation for how to use F() expressions in combination with nulls_last

to sort null values. Backport of 5d923f2d8cadb06497d255097caa4583d66b697a from master }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29313#comment:4> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscrib

Re: [Django] #29212: Redirect loop with @permission_required and redirect_authenticated_user

t_authenticated_user. Backport of df90e462d91d3a77aa89b69d791bf17c2bf7ff9b from master }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29212#comment:5> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscrib

Re: [Django] #29027: file_move_safe error with SELinux

dding removing and editing files works fine. In previous django versions, I believe this kind of behavior was just ignored. However my deployment environment has been upgraded as well, so I'm not 100% sure of this. Like OP says, this does not happen when the file size is smaller than

[Django] #29341: Automatically Set "request.current_app" for all Request

tation: 0 |Needs tests: 0 Patch needs improvement: 0 | Easy pickings: 0 UI/UX: 0 | -+----- Django should provide a standrad middleware to add current_app attribute to request objects.

Re: [Django] #29341: Automatically Set "request.current_app" for all Request

t URL: <https://code.djangoproject.com/ticket/29341#comment:1> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this grou

Re: [Django] #29341: Automatically Set "request.current_app" for all Request

lly bound to the URL reversal mechanism. IMHO `request.resolver_match.namespace` does a good job at exposing this attribute while making its origin clear. Feel free to bring the discussion to developer mailing list if your disagree with my resolution. -- Ticket URL: <https://code.django

[Django] #29342: Spam filter on issues is insane

| ---+ The spam filter on the issue tracker keeps flagging my text as spam. Even when I include a page from a newspaper or a small poem. -- Ticket URL: <https://code.djangoproject.com/ticket/29342> Django

Re: [Django] #29341: Automatically Set "request.current_app" for all Request

ent_app to replace current_app argument 。 Add the attribute in every view function is repeatly. -- Ticket URL: <https://code.djangoproject.com/ticket/29341#comment:3> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this m

Re: [Django] #29342: Spam filter on issues is insane

pickings: 0|UI/UX: 0 -+-- Changes (by Carlton Gibson): * status: new => closed * resolution: => invalid Comment: This is spam itself. Valid reports of issues with Django have no p

[Django] #29343: An exception AttributeError during HEAD request on media object

eption, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/wsgiref/handlers.py", line 141, in run self.handle_error() File "/home/yehor/.local/share/virtualenvs/webapp-Dlno2ZDu/lib/python3.6 /site-packages/django/core/servers/basehttp.py"

Re: [Django] #29340: "cache.get_or_set()" extra hits on database

if you need help confirming whether or not Django is at fault. Sir I believe you didn't get my point. this two block of code should work just alike while they don't when certain condition meets: {{{ #!python def get_location(self,event): output = cache.get(

Re: [Django] #29340: "cache.get_or_set()" extra hits on database

cond block evaluates `event.location` (which causes a database query) because it's an argument to `cache.get_or_set()`. The first block delays that evaluation until the cache is checked (`cache.get()`). This is how Python works and not a bug in Django. -- Ticket URL: <https://code.django

[Django] #29344: RemoveField on model with a single field

traceback {{{ Traceback (most recent call last): File "/home/shadi/.local/share/virtualenvs/BSEC_CMS2/lib/python3.5/site- packages/django/db/backends/utils.py", line 65, in execute return self.cursor.execute(sql, params) File "/home/shadi/.local/share/virtualenvs/BSEC_CMS2

Re: [Django] #29344: RemoveField on model with a single field

|UI/UX: 0 ---+-- Changes (by Shadi Akiki): * component: Uncategorized => Migrations -- Ticket URL: <https://code.djangoproject.com/ticket/29344#comment:1> Django <https://code.djangoproject.c

Re: [Django] #29344: RemoveField on model with a single field

name with "appname" and model name with > "modelname". > > This query threw an error in sqlite3. > > Here is the complete traceback > > {{{ > Traceback (most recent call last): > File "/home/shadi/.local/share/virtualenvs/BSEC_CMS2/lib/python

Re: [Django] #29344: RemoveField on model with a single field

name with "appname" and model name with > "modelname". > > This query threw an error in sqlite3. > > Here is the complete traceback > > {{{ > Traceback (most recent call last): > File "/home/shadi/.local/share/virtualenvs/BSEC_CMS2/lib/python

Re: [Django] #29344: RemoveField on model with a single field generates invalid SQL (was: RemoveField on model with a single field)

L: <https://code.djangoproject.com/ticket/29344#comment:4> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group

Re: [Django] #29344: RemoveField on model with a single field generates invalid SQL

pickings: 0|UI/UX: 0 -+-- Comment (by Shadi Akiki): Oh ok thanks. Sorry I didn't find that issue before filing this one -- Ticket URL: <https://code.djangoproject.com/ticket/29344#comment:5

Re: [Django] #29345: Migrations that recreate constraints can fail on PostgreSQL if table is not in public schema

ct.com/ticket/29345> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails f

[Django] #29345: Migrations that recreate constraints can fail on PostgreSQL if table is not in public schema

UI/UX: 0| ---+ The `django.db.backends.postgresql.introspection.get_constraints(...)`-function contains an SQL expression that assumes that all tables are in the `public` schema: https://github.com/django

Re: [Django] #29345: Migrations that recreate constraints can fail on PostgreSQL if table is not in public schema

improvement: 0 Easy pickings: 0|UI/UX: 0 -+-- Changes (by Olav Morken): * Attachment "models.py" added. `models.py` for migration_app -- Ticket URL: <https://code.djangoproject.com/ticket/

Re: [Django] #29345: Migrations that recreate constraints can fail on PostgreSQL if table is not in public schema

: 0 Easy pickings: 0|UI/UX: 0 -+ Changes (by Tim Graham): * stage: Unreviewed => Accepted -- Ticket URL: <https://code.djangoproject.com/ticket/29345#comment:1> Djan

Re: [Django] #28600: Add prefetch related support to RawQuerySet

-+- Comment (by Дилян Палаузов): Would you mind implementing the same for bulk_create() #28692? -- Ticket URL: <https://code.djangoproject.com/ticket/28600#comment:25> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You r

Re: [Django] #26780: Prefetch objects don't work with slices

Needs tests: 0| Patch needs improvement: 0 Easy pickings: 0|UI/UX: 0 -+- Comment (by Haseeb Ahmad): I think there is a workaround now to in django new version as we

[Django] #29346: Add "intermediary" kwarg to ModelForm._save_m2m

continue # ADDED if f.name in cleaned_data: f.save_form_data(self.instance, cleaned_data[f.name]) }}} And yes, this means adding the `intermediary` kwarg to `ModelForm.save()` so that `intermediary` can be passed to `ModelForm._save_m2m`. -- Ticket URL: <https://code.dj

Re: [Django] #29247: A custom blank value in model field choices doesn't work when using named groups

d choice to be defined in nested choices. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29247#comment:3> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups &

Re: [Django] #28622: Allow password reset token to expire in under a day

: New feature => Cleanup/optimization Comment: Please uncheck "Needs documentation" if it's added to the patch. [https://groups.google.com/d/topic/django- developers/65iOQunvkPY/discussion django-developers discussion] -- Ticket URL: <https://code.djangoproject.com/tic

Re: [Django] #29346: Add "intermediary" kwarg to ModelForm._save_m2m

/ticket/29346#comment:1> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails f

<    1   2   3   4   5   6   7   8   9   10   >