Need teamwork to gain experience!

[web_dj]

I am female Django web developer . I am looking for a serious female exper
programmer(s) who have the same interests as me to work together on joint
projects on github.
We will do projects that use :
Django Rest framework(Backend),
React javascript(Frontend).

Note: please i need who have expert (not beginers) because i need to get
expert from them to reach senior programmer level to be able to work online
with a programming company at future.

You can send email to me, i will be so happy if i get any assistance.

email:
developer.web...@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/CAHgh7XZzUkBMwRSbcvO0pSCu2V2U-TEZZmVeFJ4wKj-b3hmwgw%40mail.gmail.com.

Re: Ticket #34646 Ordering a Django admin column based on multiple model fields

[Mubarak Alrashidi]

Can we at least know what the developers think about it?


On Sunday, June 11, 2023 at 1:28:58 AM UTC+3 Mubarak Alrashidi wrote:

> Hello,
>
> I posted this StackOverflow question 
> , and @Willem Van Onsem 
>  
> tried 
> to help by opening a ticket numbered #34646 
> , and creating a patch for 
> supporting the order by multiple fields in admin.display decorator.
>
> But it got closed as a duplicate of #31975 
>  which was reported about 3 
> years ago, and it got closed as wontfix by @Mariusz Felisiak 
>  because he said: *"We don't want to add 
> unnecessary complexity to the API.".*
>
> And I agree with what @Petr Dlouhý 
> 
>  says: *"it is small modification of Django code and small increase in 
> API complexity (which is consistent with the logic of other order fields, 
> BTW)."**.*
>
> The inconsistency is when somewhere we're able to order by multiple 
> fields, and somewhere else we can't.
>
> If we can order by multiple fields in the modelAdmin classes, why can't we 
> do so in the admin.display decorator?
>
> So, I do hope to reconsider implementing the patch 
> 
>  that @Willem Van Onsem 
> 
>  created.
>
> Thanks
>

-- 
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/7ca7b6c0-204e-47d3-8971-8d05722fed11n%40googlegroups.com.

Re: Ticket #34646 Ordering a Django admin column based on multiple model fields

[David Sanders]

Mariusz is a developer, so that's at least 1 developer's opinion :)

Unless anybody else pipes up to counter this I'd consider it to be a nice 
solution.

On Monday, 19 June 2023 at 05:01:52 UTC+10 Mubarak Alrashidi wrote:

> Can we at least know what the developers think about it?
>
>
> On Sunday, June 11, 2023 at 1:28:58 AM UTC+3 Mubarak Alrashidi wrote:
>
>> Hello,
>>
>> I posted this StackOverflow question 
>> , and @Willem Van Onsem 
>>  
>> tried 
>> to help by opening a ticket numbered #34646 
>> , and creating a patch for 
>> supporting the order by multiple fields in admin.display decorator.
>>
>> But it got closed as a duplicate of #31975 
>>  which was reported about 3 
>> years ago, and it got closed as wontfix by @Mariusz Felisiak 
>>  because he said: *"We don't want to add 
>> unnecessary complexity to the API.".*
>>
>> And I agree with what @Petr Dlouhý 
>> 
>>  says: *"it is small modification of Django code and small increase in 
>> API complexity (which is consistent with the logic of other order fields, 
>> BTW)."**.*
>>
>> The inconsistency is when somewhere we're able to order by multiple 
>> fields, and somewhere else we can't.
>>
>> If we can order by multiple fields in the modelAdmin classes, why can't 
>> we do so in the admin.display decorator?
>>
>> So, I do hope to reconsider implementing the patch 
>> 
>>  that @Willem Van Onsem 
>> 
>>  created.
>>
>> Thanks
>>
>

-- 
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/02535619-27e9-40ec-835b-1ea1c5a08315n%40googlegroups.com.

Re: Ticket #34646 Ordering a Django admin column based on multiple model fields

[Mark Niehues]

I also lately stumbled across this and was a little surprised that it could not 
handle multiple fields, as it is the case in other places.

So +1 for fixing this from me :)

Am 19. Juni 2023 03:05:41 MESZ schrieb David Sanders 
:
>Mariusz is a developer, so that's at least 1 developer's opinion :)
>
>Unless anybody else pipes up to counter this I'd consider it to be a nice 
>solution.
>
>On Monday, 19 June 2023 at 05:01:52 UTC+10 Mubarak Alrashidi wrote:
>
>> Can we at least know what the developers think about it?
>>
>>
>> On Sunday, June 11, 2023 at 1:28:58 AM UTC+3 Mubarak Alrashidi wrote:
>>
>>> Hello,
>>>
>>> I posted this StackOverflow question 
>>> , and @Willem Van Onsem 
>>>  
>>> tried 
>>> to help by opening a ticket numbered #34646 
>>> , and creating a patch for 
>>> supporting the order by multiple fields in admin.display decorator.
>>>
>>> But it got closed as a duplicate of #31975 
>>>  which was reported about 3 
>>> years ago, and it got closed as wontfix by @Mariusz Felisiak 
>>>  because he said: *"We don't want to add 
>>> unnecessary complexity to the API.".*
>>>
>>> And I agree with what @Petr Dlouhý 
>>> 
>>>  says: *"it is small modification of Django code and small increase in 
>>> API complexity (which is consistent with the logic of other order fields, 
>>> BTW)."**.*
>>>
>>> The inconsistency is when somewhere we're able to order by multiple 
>>> fields, and somewhere else we can't.
>>>
>>> If we can order by multiple fields in the modelAdmin classes, why can't 
>>> we do so in the admin.display decorator?
>>>
>>> So, I do hope to reconsider implementing the patch 
>>> 
>>>  that @Willem Van Onsem 
>>> 
>>>  created.
>>>
>>> Thanks
>>>
>>
>
>-- 
>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/02535619-27e9-40ec-835b-1ea1c5a08315n%40googlegroups.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/5D677F69-2F6F-480C-8657-F1851B175E4A%40posteo.de.

Re: Ticket #34646 Ordering a Django admin column based on multiple model fields

[David Sanders]

Sorry to clarify I intended to respond with "niche solution" not "nice 
solution" lol. I didn't realise the phone's autocomplete had done that.

On Monday, 19 June 2023 at 11:05:41 UTC+10 David Sanders wrote:

> Mariusz is a developer, so that's at least 1 developer's opinion :)
>
> Unless anybody else pipes up to counter this I'd consider it to be a nice 
> solution.
>
> On Monday, 19 June 2023 at 05:01:52 UTC+10 Mubarak Alrashidi wrote:
>
>> Can we at least know what the developers think about it?
>>
>>
>> On Sunday, June 11, 2023 at 1:28:58 AM UTC+3 Mubarak Alrashidi wrote:
>>
>>> Hello,
>>>
>>> I posted this StackOverflow question 
>>> , and @Willem Van Onsem 
>>>  
>>> tried 
>>> to help by opening a ticket numbered #34646 
>>> , and creating a patch for 
>>> supporting the order by multiple fields in admin.display decorator.
>>>
>>> But it got closed as a duplicate of #31975 
>>>  which was reported about 
>>> 3 years ago, and it got closed as wontfix by @Mariusz Felisiak 
>>>  because he said: *"We don't want to add 
>>> unnecessary complexity to the API.".*
>>>
>>> And I agree with what @Petr Dlouhý 
>>> 
>>>  says: *"it is small modification of Django code and small increase in 
>>> API complexity (which is consistent with the logic of other order fields, 
>>> BTW)."**.*
>>>
>>> The inconsistency is when somewhere we're able to order by multiple 
>>> fields, and somewhere else we can't.
>>>
>>> If we can order by multiple fields in the modelAdmin classes, why can't 
>>> we do so in the admin.display decorator?
>>>
>>> So, I do hope to reconsider implementing the patch 
>>> 
>>>  that @Willem Van Onsem 
>>> 
>>>  created.
>>>
>>> Thanks
>>>
>>

-- 
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/9de4defb-b14b-4174-8678-4c3b3227aca5n%40googlegroups.com.

Re: Fellow Reports - June 2023

[Mariusz Felisiak]

Week ending June 19, 2023

*Triaged:*
https://code.djangoproject.com/ticket/34651 - 'list' object has no 
attribute '_committed' (invalid)
https://code.djangoproject.com/ticket/34652 - Async support in admin 
view (wontfix)
https://code.djangoproject.com/ticket/34569 - Unify all model fields to 
call get_prep_value from get_db_prep_value (accepted)
https://code.djangoproject.com/ticket/34655 - Tests for RadioSelect and 
Select have diverged considerably, potentially leaving RadioSelect 
undertested (accepted)
https://code.djangoproject.com/ticket/34656 - Wrong HTML generation in 
Django admin's change_password form  (accepted)
https://code.djangoproject.com/ticket/34659 - mysql backend creates 
queries using CONVERT_TZ even when this is not supported (duplicate)
https://code.djangoproject.com/ticket/34660 - Use RFC3339 format and 
input type=(date|time|datetime-local) for date/time/datetime form fields 
(duplicate)
https://code.djangoproject.com/ticket/34658 - New assertion 
`assertNotInHTML`, like `assertContains` has `assertNotContains` (wontfix)
https://code.djangoproject.com/ticket/34662 - Translation strings of 
ArrayField length validators depend on wrong ngettext key (accepted)
https://code.djangoproject.com/ticket/34663 - Documentation typo in 
using Argon2 with Django. (worksforme)

*Reviewed/committed:*
https://github.com/django/django/pull/16954 - Simplified and improved 
django.utils.functional.lazy().
https://github.com/django/django/pull/16934 - Fixed #34628 -- Improved 
icons accessibility of related widget wrapper in admin.
https://github.com/django/django/pull/16970 - Made 
SeleniumTests.test_select_multiple less flaky by adding explicit Selenium 
wait.
https://github.com/django/django/pull/16965 - Fixed #34649 -- Fixed 
headless deprecation warning on Selenium 4.8+.
https://github.com/django/django/pull/16973 - Fixed 
date_time_picker_shortcuts() tests on Windows.
https://github.com/django/django/pull/16974 - Refs #32143 -- Removed 
superflous constraints on excluded query.
https://github.com/django/django/pull/16903 - Fixed #33414 -- Fixed 
creating diamond shaped MTI objects for common ancestor with primary key 
that has a default.
https://github.com/django/django/pull/16966 - Added GitHub action to 
run Selenium tests.
https://github.com/django/django/pull/16745 - Fixed #34473 -- Fixed 
step validation for form fields with non-zero minimum value.
https://github.com/django/django/pull/16939 - Fixed #34629 -- Added 
filtering support to GIS aggregates.
https://github.com/django/django/pull/16981 - Added Selenium tests to 
daily builds.
https://github.com/django/django/pull/16989 - Made 
SeleniumTests.test_inline_uuid_pk_add_with_popup less flaky by waiting 
until popup is closed.
https://github.com/django/django/pull/16986 - Fixed #34662 -- Corrected 
number in error messages for Array(Min/Max)LengthValidator.

*Reviewed:*
https://github.com/django/django/pull/16967 - Updated PyPI setup access 
in prerequisites checklist of release how-to.

*Authored:*
https://github.com/django/djangoproject.com/pull/1374 - Fixed HTML of 
community page.
https://github.com/django/django/pull/16990 - Improved names for 
Selenium daily builds.

Best,
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/2d9856c5-e0a3-424c-89fd-8baf17df59ebn%40googlegroups.com.