bulk_update: add **exclude** arg
Dear Django developers, Thank you very much for great work and team-work on our beloved Django. I suddenly saw the new great feature *bulk_update *for models and so updated to the dev branch. As other similar situations like forms, we have exclude argument for *lazy programmers.* *Thank you,* *Mohammad Etemaddar* -- 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/9cbf3c99-70b5-49d4-a141-d317652ff66a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
static templatetag: adding default argument blank
in the conversion of HTML template to Django template, sometimes it is hard
to find&remplce static paths.
In current Django template we should change for example this:
to
as you see we add two parts to the href:
We can also do in this order:
(2)
In this way, we need to do only one find/replace. But in the previous way,
we should first do find/replace on beginning and then add "%}" to the end.
Maybe with some find/replace on every suffix (jpg,jpeg,css,js,png...)
But in way (2) We need only one find/replace if we have one asset directory
in template.
In this way, We can give the static function default value blank in order
to put just *{% static %}*.
--
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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/b891d179-a6da-4150-8ebd-a966e5af9567%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: static templatetag: adding default argument blank
You are right. This is a better option, {{ STATIC_URL }}.
Mohammad Etemaddar
* in <http://www.linkedin.com/pub/mohammad-etemaddar/9/832/462>*
Programming services: *Python* & *Linux*
On Sun, Jan 20, 2019 at 9:46 PM Adam Johnson wrote:
> I would be against adding this. Most text editors support a
> find-and-replace with regex option that would let you capture the asset
> path and place it within the {% static '' %} tag; additionally, you could
> always change your templates to include STATIC_URL globally and just do
> {{ STATIC_URL }} if you wanted to avoid using the static tag with the path
> to the asset.
>
> On Sun, 20 Jan 2019 at 17:47, Mohammad Etemaddar <
> mohammad.etemad...@gmail.com> wrote:
>
>> in the conversion of HTML template to Django template, sometimes it is
>> hard to find&remplce static paths.
>> In current Django template we should change for example this:
>>
>>
>> to
>>
>>
>> as you see we add two parts to the href:
>>
>>
>>
>> We can also do in this order:
>>
>>
>> (2)
>>
>> In this way, we need to do only one find/replace. But in the previous
>> way, we should first do find/replace on beginning and then add "%}" to the
>> end. Maybe with some find/replace on every suffix (jpg,jpeg,css,js,png...)
>> But in way (2) We need only one find/replace if we have one asset
>> directory in template.
>> In this way, We can give the static function default value blank in order
>> to put just *{% static %}*.
>>
>> --
>> 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 https://groups.google.com/group/django-developers.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/b891d179-a6da-4150-8ebd-a966e5af9567%40googlegroups.com
>> <https://groups.google.com/d/msgid/django-developers/b891d179-a6da-4150-8ebd-a966e5af9567%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> 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 post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CAMyDDM2ffNLrD-ARSnwDdMms6__RU1MJ-q2V09SDpPVheO%3DBAg%40mail.gmail.com
> <https://groups.google.com/d/msgid/django-developers/CAMyDDM2ffNLrD-ARSnwDdMms6__RU1MJ-q2V09SDpPVheO%3DBAg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> 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 post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/CALJt1nvTy5x6DDUuf2pC-KOwxoR5kh8jADzLv%3DrfgPF6W2j6dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: Django 2.2 release candidate 1 released
Is it possible to have this option in Django 2.2? When we select a OneToOne object by related_name, rises DoesNotExists when have no object related. Is it possible to add the behaviour to return None instead of DoesNotExists? Thank you On Monday, March 18, 2019 at 12:33:15 PM UTC+3:30, Carlton Gibson wrote: > > We've made the final (hopefully) release on the way to Django's next > major release, Django 2.2! Check out the blog post: > https://www.djangoproject.com/weblog/2019/mar/18/django-22-rc1/ > -- 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ba861ea5-8916-4293-82c0-89461418af89%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Django 2.2 release candidate 1 released
Ryan and Adam, Thank you very much. The links was so helpful. I liked to find the best way to contribute. Sincerely, Mohammad Etemaddar <https://www.linkedin.com/in/mohammad-etemaddar> On Wed, Mar 20, 2019 at 7:39 PM Adam Johnson wrote: > Hi Mohammed, > > Thanks for making a suggestion, but this is not the thread to bring such > an issue up on. If you want to make a suggestion, it's best to make a new > thread. > > Ryan is also right, 2.2 is feature frozen, so it won't be possible to make > such a change, only to fix bugs before it gets its full release. > > As to the change you are suggesting, it is not backwards compatible. It's > a good idea to read the contributing documentation ( > https://docs.djangoproject.com/en/dev/internals/contributing/ ) and > importantly the deprecation policy ( > https://docs.djangoproject.com/en/dev/internals/release-process/#internal-release-deprecation-policy > ) before suggesting something of such magnitude. > > Hope that helps, > > Adam > > On Wed, 20 Mar 2019 at 16:03, Ryan Hiebert wrote: > >> That won't be possible, Django 2.2 has been feature-frozen for a while >> now. You might want to follow the following issue which is related to what >> you're suggesting. >> >> https://code.djangoproject.com/ticket/10227 >> >> On Wed, Mar 20, 2019 at 10:52 AM Mohammad Etemaddar < >> mohammad.etemad...@gmail.com> wrote: >> >>> Is it possible to have this option in Django 2.2? >>> When we select a OneToOne object by related_name, rises DoesNotExists >>> when have no object related. >>> Is it possible to add the behaviour to return None instead of >>> DoesNotExists? >>> >>> Thank you >>> >>> On Monday, March 18, 2019 at 12:33:15 PM UTC+3:30, Carlton Gibson wrote: >>>> >>>> We've made the final (hopefully) release on the way to Django's next >>>> major release, Django 2.2! Check out the blog post: >>>> https://www.djangoproject.com/weblog/2019/mar/18/django-22-rc1/ >>>> >>> -- >>> 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 https://groups.google.com/group/django-developers. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-developers/ba861ea5-8916-4293-82c0-89461418af89%40googlegroups.com >>> <https://groups.google.com/d/msgid/django-developers/ba861ea5-8916-4293-82c0-89461418af89%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> 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 post to this group, send email to django-developers@googlegroups.com. >> Visit this group at https://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/CABpHFHR1H%3Dii6tQD9f7MULmxNvTuoCKCC8b1tnOsO06Bi7QcFQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/django-developers/CABpHFHR1H%3Dii6tQD9f7MULmxNvTuoCKCC8b1tnOsO06Bi7QcFQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > 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 post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAMyDDM30Z4LR%2BMpXKzEh7vNoQPo8Cnn7VcNxbyNfAa4jE4tQGg%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAMyDDM30Z4LR%2BMpXKzEh7vNoQPo8Cnn7VcNxbyNfAa4jE4tQGg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more o
