Re: Fellow Reports - August 2019

[Mariusz Felisiak]

Week ending August 18, 2019.

*Triaged:*
https://code.djangoproject.com/ticket/30703 - Make RelatedFieldListFilter 
respect model meta ordering. (duplicate)
https://code.djangoproject.com/ticket/30704 - JSONField nested key and 
index transforms crash. (created)
https://code.djangoproject.com/ticket/30707 - why it took 30s when call 
sorted function in django server sometimes. (invalid)
https://code.djangoproject.com/ticket/30706 - Why isn't the auth.User.id 
field documented? (wontfix)
https://code.djangoproject.com/ticket/30708 - There is bug on RSS XML 
processor (invalid)
https://code.djangoproject.com/ticket/30709 - Error in translated document. 
(invalid)
https://code.djangoproject.com/ticket/30711 - Document 
django.contrib.postgres.fields.hstore.KeyTransform. (accepted)
https://code.djangoproject.com/ticket/30712 - Add support for defaults on 
BLOB and TEXT columns on MySQL 8.0.13+ (accepted)

*Reviewed/committed:*
https://github.com/django/django/pull/11644 - Refs #11964 -- Made 
constraint support check respect required_db_features.
https://github.com/django/django/pull/11652 - Refs #25367 -- Moved Oracle 
Exists() handling to contextual methods.
https://github.com/django/django/pull/11648 - Fixed #30461 -- Made GeoIP2 
and GEOIP_PATH setting accept pathlib.Path as library path.
https://github.com/django/django/pull/11400 - Fixed #30449 -- Fixed 
RelatedFieldListFilter/RelatedOnlyFieldListFilter to respect model's 
Meta.ordering.
https://github.com/django/django/pull/11634 - Fixed #30687 -- Fixed using 
of OuterRef() expressions in distance lookups.
https://github.com/django/django/pull/11671 - Fixed #27676 -- Allowed 
BLOB/TEXT defaults on MariaDB 10.2.1+.
https://github.com/django/django/pull/11666 - Fixed #30701 -- Updated 
patch_vary_headers() to handle an asterisk according to RFC 7231.
https://github.com/django/django/pull/11677 - Fixed #29545 -- Fixed using 
filter lookups againts nested subquery expressions.
https://github.com/django/django/pull/11621 - Refs #30426 -- Changed 
default SECURE_CONTENT_TYPE_NOSNIFF to True.
https://github.com/django/django/pull/11674 - Refs #28428 -- Made 
FileField.upload_to support pathlib.Path.

Best regards,
Mariusz

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/706e2678-b466-4c63-b528-5cac9a9f0b8a%40googlegroups.com.

create microservice in django

['Gaurav Ravindra Bole' via Django developers (Contributions to Django itself)]

How we create micro services  in django

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/4b6f56d0-6ba3-4ab7-aa44-dbf624e0e750%40googlegroups.com.

Re: create microservice in django

[Adam Johnson]

Hi!

I think you've found the wrong mailing list for this post. This mailing
list is for the development of Django itself, not for support using Django.
This means the discussions of bugs and features in Django itself, rather
than in your code using it. People on this list are unlikely to answer your
support query with their limited time and energy. Read more on the mailing
lists at https://www.djangoproject.com/community/

For support, please use the django-users mailing list, or IRC #django on
Freenode, or a site like Stack Overflow. There are people out there willing
to help on those channels, but they might not respond if you don't ask your
question well. Stack Overflow's question guide can help you frame it well:
https://stackoverflow.com/help/how-to-ask .

Also if you haven't read it, please take a look at Django's Code of
Conduct: https://www.djangoproject.com/conduct/ . These are our "ground
rules" for working well as a community, and will help you get the most out
of Django and our fantastic community.

Thanks for your understanding,

Adam

On Mon, 19 Aug 2019 at 12:20, 'Gaurav Ravindra Bole' via Django developers
(Contributions to Django itself)  wrote:

> How we create micro services  in django
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/4b6f56d0-6ba3-4ab7-aa44-dbf624e0e750%40googlegroups.com
> 
> .
>


-- 
Adam

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM3E%2BOV%2BKf-kzQz3VzEH8C_cRGsOvjWmFT4GODXiKAhfLw%40mail.gmail.com.

Re: Creating a new "Triage & Review Team"

[Aymeric Augustin]

Yes, I'm in favor of trying this.

-- 
Aymeric.

Le mer. 14 août 2019 à 15:06, Josh Smeaton  a
écrit :

> I think that's sensible, including making the team public.
>
> > This struck me as a little absurd: if we weren't going to dissolve it,
> Nick should definitely be part of the old "Django Core".
>
> It's not done yet, and while we're in this limbo stage, we're potentially
> missing out on some good maintainers before a decision has even been made.
> You can still put forward names for the core team if you think they'd make
> good members,  though I'd understand your hesitation.
>
> On Tuesday, 13 August 2019 05:12:51 UTC+10, Carlton Gibson wrote:
>>
>> Oh, one more thing. I'd like to make this a "Public" team. I think there
>> should be some visibility and recognition for the folks who work so hard on
>> keeping Django strong.
>>
>> As part of that I'd add it to the Teams list on djangoproject.com, and
>> maintain a list of previous members, for those who had stepped down.
>>
>> C.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/8b5b205e-56ca-44dc-bfd8-8a22de90be60%40googlegroups.com
> 
> .
>


-- 
Aymeric.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CANE-7mW-b-o3GEt9D2DALC%2BVFeV-DKN1tSgVr1RBFuTfErQATw%40mail.gmail.com.

Re: Creating a new "Triage & Review Team"

[Carlton Gibson]

OK, thanks Josh, Aymeric. I shall roll it out (slowly as ever 🙂)

> On 19 Aug 2019, at 17:10, Aymeric Augustin 
>  wrote:
> 
> Yes, I'm in favor of trying this.
> 
> -- 
> Aymeric.
> 
> Le mer. 14 août 2019 à 15:06, Josh Smeaton  > a écrit :
> I think that's sensible, including making the team public.
> 
> > This struck me as a little absurd: if we weren't going to dissolve it, Nick 
> > should definitely be part of the old "Django Core".
> 
> It's not done yet, and while we're in this limbo stage, we're potentially 
> missing out on some good maintainers before a decision has even been made. 
> You can still put forward names for the core team if you think they'd make 
> good members,  though I'd understand your hesitation.
> 
> On Tuesday, 13 August 2019 05:12:51 UTC+10, Carlton Gibson wrote:
> Oh, one more thing. I'd like to make this a "Public" team. I think there 
> should be some visibility and recognition for the folks who work so hard on 
> keeping Django strong. 
> 
> As part of that I'd add it to the Teams list on djangoproject.com 
> , and maintain a list of previous members, for 
> those who had stepped down. 
> 
> C. 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-developers+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-developers/8b5b205e-56ca-44dc-bfd8-8a22de90be60%40googlegroups.com
>  
> .
> 
> 
> -- 
> Aymeric.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-developers+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-developers/CANE-7mW-b-o3GEt9D2DALC%2BVFeV-DKN1tSgVr1RBFuTfErQATw%40mail.gmail.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/6499F819-147D-42D6-BA1F-62AB31DA29D2%40gmail.com.

Re: Ideas for a new DEP on long-term Django API compatibility

[Patryk Zawadzki]

As someone who has spent over 12 years working with Django, I'd like to 
offer an opposite point of view:

I love where Django is headed. I love all of those breaking changes that 
have to happen so we're not perpetually stuck with decisions from 2005.

What I truly miss is strong static typing support that would tell that when 
my code is not going to work before I even begin to test it. With static 
types and tools like mypy and pyright upgrading dependencies is usually a 
matter of a single afternoon.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/f9eaf95a-8611-4715-a4bf-6aed7a284b3f%40googlegroups.com.

Fellow Reports -- August 2019

[Carlton Gibson]

Hi All, 


Calendar Week 32 -- ending 11 August.


Triaged:

https://code.djangoproject.com/ticket/30693 -- Refatoring 
django.core.management.templates (Accepted)
https://code.djangoproject.com/ticket/30691 -- Change uuid field to FK does 
not create dependency (Accepted)
https://code.djangoproject.com/ticket/30687 -- GIS distance lookups fail 
within subqueries using OuterRef (Accepted)
https://code.djangoproject.com/ticket/30689 -- ix documentation for the 
`fields` argument of MultiValueField (Invalid)
https://code.djangoproject.com/ticket/30688 -- Clarify docs for 
Options.base_manager_name. (Accepted)
https://code.djangoproject.com/ticket/30688 -- Clarify docs for 
Options.base_manager_name. (Accepted)
https://code.djangoproject.com/ticket/30686 -- Improve utils.text.Truncator 
&co to use a full HTML parser. (Accepted)
https://code.djangoproject.com/ticket/30685 -- Suboptimal 
QuerySet.distinct().count() (Accepted)
https://code.djangoproject.com/ticket/30684 -- Oracle Database 12.2 allows 
128 byte identifiers (wontfix)
https://code.djangoproject.com/ticket/30675 -- Ignore ACCEPT_LANGUAGE 
header only on i18n prefixed url patterns (needsinfo)
https://github.com/django/djangoproject.com/issues/838 -- Announce LTS 
better (wontfix)
https://github.com/django/djangoproject.com/issues/931 -- Cannot open 
ContentFile containing BytesIO content again once it is closed (Invalid)



Reviewed:

https://github.com/django/django/pull/11639 -- Fixed #30693 -- Removed 
separate import of os.path in django.core.management.templates.
https://github.com/django/djangoproject.com/pull/896 -- Update download 
page: updated roadmap and better focus on supported versions
https://github.com/django/django/pull/11630 -- Fixed #30673 -- Relaxed 
system check for db_table collision when database routers are installed by 
turning the error into a warning.
https://github.com/django/django/pull/11636 -- Fixed #30688 -- Added an 
example for base manager usage.
https://github.com/django/djangoproject.com/pull/912 -- Add docker 
configuration for local development.
https://github.com/django/django/pull/11633 -- Fixed #30686 -- Stopped 
Truncator.chars truncating HTML entities
https://github.com/django/django/pull/11632 -- Corrected several typos in 
string literals and test names.
https://code.djangoproject.com/ticket/30676 -- Add a --pdb option to the 
test runner
https://github.com/django/django/pull/11617 -- Fixed #30672 -- Fixed crash 
of JSONField/HStoreField key and index transforms on expressions with 
params.
https://github.com/django/djangopeople/pull/103 -- Improve overall look of 
front page



Authored:

https://github.com/django/djangoproject.com/pull/933 -- Refs #838 -- Marked 
current release on downloads page as LTS (if so).
https://github.com/django/djangosnippets.org/pull/72 -- Updated to 
Django==2.1.11.
https://github.com/django/code.djangoproject.com/pull/96 -- Updated to 
Django==1.11.23.
https://github.com/django/djangoproject.com/pull/932 -- Updated to Django 
v2.2.4.





Calendar Week 33 -- ending 18 August.


Triaged:

https://code.djangoproject.com/ticket/30713 -- ListView queryset issue 
(Invalid)
https://code.djangoproject.com/ticket/30710 -- impossible without 
workarounds to see which fields changed when subscribing to signals from 
generic views (wontfix)
https://code.djangoproject.com/ticket/30705 -- Django template permissions 
not working when used inside the template of an inclusion tag (needsinfo)
https://code.djangoproject.com/ticket/25139 -- ModelFormSet: allow swapping 
unique values (Someday/Maybe)
https://code.djangoproject.com/ticket/30702 -- Form leaks all objects of 
model (Invalid)
https://code.djangoproject.com/ticket/30701 -- Allowing 
patch_vary_headers() caching utility to handle '*' value. (Accepted)
https://code.djangoproject.com/ticket/30698 -- `BaseDetailView` and 
`SingleObjectMixin` optimization. (wontfix)
https://code.djangoproject.com/ticket/30699 -- Remove 
`PublisherDetail.get_context_data()` from documentation (wontfix)
https://code.djangoproject.com/ticket/30700 -- templatetag 
truncatechars_html breaks HTML entities (Duplicate of #30686)
https://code.djangoproject.com/ticket/30694 -- FileResponse does not seek 
its file source (wontfix)



Reviewed:

https://github.com/django/django/pull/11676 -- Fixed #30694 -- Documented 
FileResponse does not seek its file source
https://github.com/django/django/pull/11666 -- Fixed #30701 -- Updated 
patch_vary_headers() to handle an asterisk according to RFC 7231.
https://github.com/django/django/pull/11671 -- Fixed #27676 -- Allowed 
BLOB/TEXT defaults on MariaDB 10.2.1+.
https://github.com/django/django/pull/11481 -- Code Pull requests 228 
Security Insights Settings Fixed #10403 -- Declaraive syntax for FormSet, 
ModelFormSet & InlineF…
https://github.com/django/django/pull/11580 -- Fixed #26142 -- Added a 
'edit only' mode for model formsets
https://github.com/django/djangoproject.com/pull/928 -- Added `invisible` 
reCaptcha to

Re: Creating a new "Triage & Review Team"

[Adam Johnson]

Sounds good to me too, looking forward to it!

On Mon, 19 Aug 2019 at 16:30, Carlton Gibson 
wrote:

> OK, thanks Josh, Aymeric. I shall roll it out (slowly as ever 🙂)
>
> On 19 Aug 2019, at 17:10, Aymeric Augustin <
> aymeric.augus...@polytechnique.org> wrote:
>
> Yes, I'm in favor of trying this.
>
> --
> Aymeric.
>
> Le mer. 14 août 2019 à 15:06, Josh Smeaton  a
> écrit :
>
>> I think that's sensible, including making the team public.
>>
>> > This struck me as a little absurd: if we weren't going to dissolve it,
>> Nick should definitely be part of the old "Django Core".
>>
>> It's not done yet, and while we're in this limbo stage, we're potentially
>> missing out on some good maintainers before a decision has even been made.
>> You can still put forward names for the core team if you think they'd make
>> good members,  though I'd understand your hesitation.
>>
>> On Tuesday, 13 August 2019 05:12:51 UTC+10, Carlton Gibson wrote:
>>>
>>> Oh, one more thing. I'd like to make this a "Public" team. I think there
>>> should be some visibility and recognition for the folks who work so hard on
>>> keeping Django strong.
>>>
>>> As part of that I'd add it to the Teams list on djangoproject.com, and
>>> maintain a list of previous members, for those who had stepped down.
>>>
>>> C.
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django developers (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-developers+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/8b5b205e-56ca-44dc-bfd8-8a22de90be60%40googlegroups.com
>> 
>> .
>>
>
>
> --
> Aymeric.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CANE-7mW-b-o3GEt9D2DALC%2BVFeV-DKN1tSgVr1RBFuTfErQATw%40mail.gmail.com
> 
> .
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/6499F819-147D-42D6-BA1F-62AB31DA29D2%40gmail.com
> 
> .
>


-- 
Adam

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM0tnCMkqCb2NhsbysfWeK%2BBHiTWDLRpzSKCrdW3Hz-kOQ%40mail.gmail.com.