Re: GSoC 2020

[Abhijeet Viswa]

Hi guys,

I'd like to say the same. It was a wonderful opportunity. Thanks everyone.

Regards.

On Mon, 4 May 2020 at 23:41, Sanskar Jaiswal 
wrote:

> Hey everyone,
>
> I didn’t get selected for GSoC, but I would like to sincerely thank this
> community for guiding me and helping me get involved in open source.
> Especially, Simon and Carlton for solving my doubts about the ORM.
>
> I hope to improve myself and will definitely try again next year. I still
> aim to work on refactoring ORM to work with ModelState.
>
> Thanks
> Sanskar
>
> --
> 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/CACzaa%3DEWW83WkxkSREcGowwB4ne5Qen%3DLee5iV__6hP2a%3DkqjQ%40mail.gmail.com
> 
> .
>


-- 
Abhijeet

-- 
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/CAP1-Yrq%3DY_%2BbM7cKYvhJWLtfEFoFFUknEo0txf6rgF8q5rnJ7Q%40mail.gmail.com.

GSoC 2020

[Sanskar Jaiswal]

Hey everyone,

I didn’t get selected for GSoC, but I would like to sincerely thank this
community for guiding me and helping me get involved in open source.
Especially, Simon and Carlton for solving my doubts about the ORM.

I hope to improve myself and will definitely try again next year. I still
aim to work on refactoring ORM to work with ModelState.

Thanks
Sanskar

-- 
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/CACzaa%3DEWW83WkxkSREcGowwB4ne5Qen%3DLee5iV__6hP2a%3DkqjQ%40mail.gmail.com.

Re: Ticket #25236: Remove ifequal from the template language

[Markus Holtermann]

Yes please! Nice catch and followup :)

Cheers,

Markus

On Mon, May 4, 2020, at 4:08 PM, Jon Dufresne wrote:
> Hi,
> 
> I'd like to raise this topic for renewed discussion. I think it is time 
> to begin deprecating the obsolete template tags. So +1 for removal.
> 
> I had all but forgotten about the {% ifequal %} template tag and then 
> eventually stumbled across it doing unrelated work. Upon rediscovering 
> it as a practical duplicate of {% if %}, I thought I'd help out Django 
> by deprecating it for eventual removal so that we're back to "one -- 
> and preferably only one -- obvious way to do it". I created the PR to 
> begin the deprecation here: https://github.com/django/django/pull/12851
> 
> We're now coming up on 10 years since Django 1.2 was released with the 
> smart if template tag. Projects and third party apps have had a 
> generous extended time to update their code.
> 
> For projects that don't follow Django releases in detail, they may not 
> be aware that the {% ifequal %} tag is obsolete and so have not had any 
> motivation to change. Adding a deprecation warning may help such 
> projects to understand they should update their templates.
> 
> For projects that find it is a burden to update, they've had 10 years 
> to do so. I think adding more time isn't what they need at this point. 
> The actual upgrade can be mostly automated with sed (I could even put a 
> recommended command in the release notes). So the update doesn't need 
> to be very time consuming.
> 
> While perhaps we agree leaving old code around can mostly go unnoticed, 
> technical debt has subtle ways of showing up. For example, time was 
> spent by me rediscovering this feature exists and wondering why there 
> are two way to write {% if ... %} (this could happen to other 
> contributors studying the template tag system). Time has been spent on 
> this mailing list discussing what to do with old unused code. Its tests 
> -- which mostly don't matter at this point -- run on every PR and in 
> local environments. If there is ever an attempt at an internal 
> refactoring of the template code, the ifequal tag will need to be 
> considered and maintained. And so on.
> 
> On Sun, Aug 9, 2015 at 12:37 PM Collin Anderson  wrote:
> > Hi All,
> > 
> > I really like the "don't use this on new code, but there's no rush in 
> > replacing it" category. I think that's really important to have that in a 
> > project that's this old. I think it would be great to minimize the amount 
> > required changes that need to be done.
> > 
> > Thanks,
> > Collin
> > 
> 
> >  -- 
> >  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 post to this group, send email to django-developers@googlegroups.com.
> >  Visit this group at http://groups.google.com/group/django-developers.
> >  To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/django-developers/2ddf20f1-af1a-47c1-b07c-669818846b53%40googlegroups.com
> >  
> > .
> >  For more options, visit https://groups.google.com/d/optout.
> 
>  -- 
>  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/CADhq2b5%3D3A03OjPTGa7mUgm-7braWgJwLUU_xW5pFJrgPP6Uow%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/6f2a7ca0-f223-4b24-8851-5fe37db3e89a%40www.fastmail.com.

Re: Fellow Reports - April 2020

[Mariusz Felisiak]

Week ending May 3, 2020.

*Triaged:*
https://code.djangoproject.com/ticket/31517 - 
ManifestFilesMixin.file_hash() returning None get's included in hashed 
filename as 'None'. (accepted)
https://code.djangoproject.com/ticket/31513 - Store failed tests in files. 
(wontfix)
https://code.djangoproject.com/ticket/31369 - Deprecate the model 
NullBooleanField. (fixed)
https://code.djangoproject.com/ticket/31519 - Unclosed tags don't cause 
syntax errors in templates. (wontfix)
https://code.djangoproject.com/ticket/31515 - Django tries to reuse MySQL 
connections that have gone away with ASGI. (accepted)
https://code.djangoproject.com/ticket/31521 - test_parsing_rfc850 test 
failure on 32-bit platforms. (accepted)
https://code.djangoproject.com/ticket/31523 - Remove jQuery dependency from 
actions.js. (accepted)
https://code.djangoproject.com/ticket/31522 - FilteredSelectMultiple widget 
jumps to top when an option is added. (accepted)
https://code.djangoproject.com/ticket/31525 - Development vs Production. 
(invalid)
https://code.djangoproject.com/ticket/31529 - Add support for pathlib and 
os.PathLike in migrations serializer. (accepted)
https://code.djangoproject.com/ticket/31530 - Check that 
CheckConstraint.check and UniqueConstraint.condition don't span joins. 
(accepted)

*Reviewed/committed:*
https://github.com/django/django/pull/12792 - Refs #18325 -- Removed 
unnecessary line endings in management commands.
https://github.com/django/django/pull/12803 - Fixed #31517 -- Fixed 
HashedFilesMixin.hashed_name() if hash of the file is None.
https://github.com/django/django/pull/12447 - Changed 
django.forms.ValidationError imports to 
django.core.exceptions.ValidationError.
https://github.com/django/django/pull/12786 - Fixed #29249 -- Made JSON and 
YAML serializers use Unicode by default.
https://github.com/django/django/pull/12804 - Refs #30400 -- Improved 
typography of user facing strings in admin changelist.
https://github.com/django/django/pull/12809 - Fixed #31356 -- Changed IRC 
links to the Freenode webchat.
https://github.com/django/django/pull/12818 - Fixed #31521 -- Skipped 
test_parsing_rfc850 test on 32-bit systems.
https://github.com/django/django/pull/12789 - Fixed #25712 -- Reorganized 
templates docs.
https://github.com/django/django/pull/10338 - Fixed #20581 -- Added support 
for deferrable unique constraints.
https://github.com/django/django/pull/12829 - Refs #27778 -- Removed 
reference to ASCII usernames in django.contrib.auth.models.User docs.
https://github.com/django/django/pull/12659 - Doc'd Meta inheritance from 
abstract parents.
https://github.com/django/django/pull/12704 - Fixed #31455 -- Added support 
for deferrable exclusion constraints on PostgreSQL.

*Authored:*
https://github.com/django/django/pull/12822 - Refs #27468 -- Made user 
sessions use SHA-256 algorithm.
https://github.com/django/django/pull/12834 - Refs #31032 -- Removed 
obsolete CSS workaround for IE in openlayers template.
https://github.com/django/django/pull/12836 - Updated admin's Select2 to 
4.0.13.

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/8135ddde-6a2c-4d12-ace2-1df81286f32d%40googlegroups.com.

Re: Ticket #25236: Remove ifequal from the template language

[Mariusz Felisiak]

Agreed. We should deprecate both.

(I could even put a recommended command in the release notes).
>

I don't think it's a good idea. You can attach "unofficial" script in the 
ticket, but release notes are not a proper place, IMO. It may not behave 
properly in block comments etc. Don't get me wrong, I wrote dozens of such 
scripts, but they can be error-prone, and we shouldn't take 
responsibilities for potential issues.

It would also be worth having a sentence that one could extract them as 
> custom template tags as Tim noted previously. 
>

Sounds good. 

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/53a8fc25-cd6f-413b-af7a-4615f204cbfa%40googlegroups.com.

Re: Ticket #25236: Remove ifequal from the template language

[Adam Johnson]

+1 for removal. 5 years have nearly passed since that discussion with the
docs saying "The ifequal and ifnotequal tags will be deprecated in a future
release." so I think it's worth actioning.

(I could even put a recommended command in the release notes).
>

I like this idea. It would also be worth having a sentence that one could
extract them as custom template tags as Tim noted previously.

On Mon, 4 May 2020 at 15:08, Jon Dufresne  wrote:

> Hi,
>
> I'd like to raise this topic for renewed discussion. I think it is time to
> begin deprecating the obsolete template tags. So +1 for removal.
>
> I had all but forgotten about the {% ifequal %} template tag and then
> eventually stumbled across it doing unrelated work. Upon rediscovering it
> as a practical duplicate of {% if %}, I thought I'd help out Django by
> deprecating it for eventual removal so that we're back to "one -- and
> preferably only one -- obvious way to do it". I created the PR to begin the
> deprecation here: https://github.com/django/django/pull/12851
>
> We're now coming up on 10 years since Django 1.2 was released with the
> smart if template tag. Projects and third party apps have had a generous
> extended time to update their code.
>
> For projects that don't follow Django releases in detail, they may not be
> aware that the {% ifequal %} tag is obsolete and so have not had any
> motivation to change. Adding a deprecation warning may help such projects
> to understand they should update their templates.
>
> For projects that find it is a burden to update, they've had 10 years to
> do so. I think adding more time isn't what they need at this point. The
> actual upgrade can be mostly automated with sed (I could even put a
> recommended command in the release notes). So the update doesn't need to be
> very time consuming.
>
> While perhaps we agree leaving old code around can mostly go unnoticed,
> technical debt has subtle ways of showing up. For example, time was spent
> by me rediscovering this feature exists and wondering why there are two way
> to write {% if ... %} (this could happen to other contributors studying the
> template tag system). Time has been spent on this mailing list discussing
> what to do with old unused code. Its tests -- which mostly don't matter at
> this point -- run on every PR and in local environments. If there is ever
> an attempt at an internal refactoring of the template code, the ifequal tag
> will need to be considered and maintained. And so on.
>
> On Sun, Aug 9, 2015 at 12:37 PM Collin Anderson 
> wrote:
>
>> Hi All,
>>
>> I really like the "don't use this on new code, but there's no rush in
>> replacing it" category. I think that's really important to have that in a
>> project that's this old. I think it would be great to minimize the amount
>> required changes that need to be done.
>>
>> Thanks,
>> Collin
>>
>> --
>> 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 post to this group, send email to django-developers@googlegroups.com.
>> Visit this group at http://groups.google.com/group/django-developers.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/2ddf20f1-af1a-47c1-b07c-669818846b53%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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/CADhq2b5%3D3A03OjPTGa7mUgm-7braWgJwLUU_xW5pFJrgPP6Uow%40mail.gmail.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/CAMyDDM1h-DS1aNLBs5wL25sNxAjDqMF_Z2fvX5ECD1kLO%2BjtmA%40mail.gmail.com.

Re: Ticket #25236: Remove ifequal from the template language

[Jon Dufresne]

Hi,

I'd like to raise this topic for renewed discussion. I think it is time to
begin deprecating the obsolete template tags. So +1 for removal.

I had all but forgotten about the {% ifequal %} template tag and then
eventually stumbled across it doing unrelated work. Upon rediscovering it
as a practical duplicate of {% if %}, I thought I'd help out Django by
deprecating it for eventual removal so that we're back to "one -- and
preferably only one -- obvious way to do it". I created the PR to begin the
deprecation here: https://github.com/django/django/pull/12851

We're now coming up on 10 years since Django 1.2 was released with the
smart if template tag. Projects and third party apps have had a generous
extended time to update their code.

For projects that don't follow Django releases in detail, they may not be
aware that the {% ifequal %} tag is obsolete and so have not had any
motivation to change. Adding a deprecation warning may help such projects
to understand they should update their templates.

For projects that find it is a burden to update, they've had 10 years to do
so. I think adding more time isn't what they need at this point. The actual
upgrade can be mostly automated with sed (I could even put a recommended
command in the release notes). So the update doesn't need to be very time
consuming.

While perhaps we agree leaving old code around can mostly go unnoticed,
technical debt has subtle ways of showing up. For example, time was spent
by me rediscovering this feature exists and wondering why there are two way
to write {% if ... %} (this could happen to other contributors studying the
template tag system). Time has been spent on this mailing list discussing
what to do with old unused code. Its tests -- which mostly don't matter at
this point -- run on every PR and in local environments. If there is ever
an attempt at an internal refactoring of the template code, the ifequal tag
will need to be considered and maintained. And so on.

On Sun, Aug 9, 2015 at 12:37 PM Collin Anderson 
wrote:

> Hi All,
>
> I really like the "don't use this on new code, but there's no rush in
> replacing it" category. I think that's really important to have that in a
> project that's this old. I think it would be great to minimize the amount
> required changes that need to be done.
>
> Thanks,
> Collin
>
> --
> 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 post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/2ddf20f1-af1a-47c1-b07c-669818846b53%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CADhq2b5%3D3A03OjPTGa7mUgm-7braWgJwLUU_xW5pFJrgPP6Uow%40mail.gmail.com.

Re: Django for Beginners Graphic illustration

[Charles Thayer]

This is great. My one suggestion is that it appears upside down. I think 
the request should start on the upper left and go down through the sites to 
apps.

On Friday, May 1, 2020 at 5:37:08 AM UTC-7, Navneet wrote:
>
> Using the Polls app as an example used in Django for Beginners, I'm 
> putting together a chart to visualize the relationships and flow of 
> information between different components. It still needs to be improved but 
> I'm sharing what I've so far so it can be posted for everyone once done. I 
> can use some collaboration to finish it.
>

-- 
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/b61d92d7-5b2e-4800-9882-3c0b87b24d28%40googlegroups.com.