rrors get thrown
to help debug issues.
--
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+unsubsc
PR which will add this functionality to the Django
>> project. But before this we decided to search similar solutions in django
>> PRs. And we found them! Ticket 30423
>> https://code.djangoproject.com/ticket/30423 sounds good enough, but it
>> was closed with wontfix lab
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/76615d60
the least), at least
for me.
So will you please consider at least discussing the issues I raise here?
Best regards,
Sébastien Gélis
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe
so recommended trying django-select2, as
> Johannes wrote on the ticket (
> https://code.djangoproject.com/ticket/32628#comment:5 ).
>
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubs
> will add a feature only for a single user, i.e. for the reporter. Also, we
>> cannot add features just because they are not complex (*"death by a
>> thousand cuts"*), each of them has a maintenance cost. Moreover, adding
>> new features to the admin which are n
omeone can provide guidance for what to do besides the two one line
changes.
Greetings
--
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 i
ed from https://code.djangoproject.com/ticket/33699 as ticket has
been closed due to wrong place...
--
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
te further and perhaps
> come up with a patch? You're likely "the world expert" on this part of
> Django at this point, after all the profiling you've done.
>
>
> On Wed, May 11, 2022 at 5:44 PM Ferran Jovell wrote:
>
>> This is still the wr
to fit our needs exactly. (But we can see on review...)
>
> Please do open a PR when you're ready.
>
> Kind regards,
> Carlton
>
> On Tue, 17 May 2022 at 15:20, 'Noxx' via Django developers (Contributions
> to Django itself) wrote:
>
>> Hi all,
>>
for f in cls._meta.fields*
>
> *if isinstance(f, GeneratedField)*
>
> *]*
>
>
> * def _do_insert(self, manager, using, fields, *args, **kwargs):*
>
> *generated_fields = self._generated_fields()*
>
> *if generated_fields and fields
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-
gt;>>>>>
>>>>>>>
>>>>>>> On Monday, 15 October 2018 20:41:13 UTC+11, tobias@truffls.com
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Thank you for your feedback. I would
uot;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/d2a082af
o implement that new feature.
>>
>
> No offense taken at all. If somehow possible I'd like to encourage you to
> work with us on your pain points. I think at least some of those are
> addressed or at least addressable. I am happy to offer code and fixes, but
>
change something that doesn't seem
>>> broken. Maybe keep some of these thoughts in mind when a change is made to
>>> the core backends or the compiler and consider how other backends will need
>>> to implement that new feature.
>>>
>>
>
ge 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 d
7d6cb764788eeaf73a371d7
> [3] https://github.com/django/django/pull/4397
> [4] https://docs.djangoproject.com/en/1.11/ref/models/options/#managed
> [5] https://code.djangoproject.com/ticket/27241
> [6] https://code.djangoproject.com/ticket/28107
> [7]
> https://github.com/djang
ango had security releases because of issues in `is_safe_url()`
> releasing a smaller package and not the full Django package could possibly
> be beneficial.
> - Does somebody from the security team want or should be another
> maintainer?
>
> Thanks for reading.
>
> Markus
gle 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-develop
the function you want
> right now is only one line (get_user_session_key).
>
> Thanks,
>
> Adam
>
> On Thu, 25 Jul 2019 at 14:09, 'andreymal' via Django developers
> (Contributions to Django itself) <mailto:django-developers@googlegroups.com>> wrote:
>
&g
would like to start and I
believe, this small change might be a good start. If you agree, I could
open a ticket in trac.
Best Regards,
Jann
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To u
ap
> with override_settings(SECRET_KEY=other_key) around your call to
> PasswordResetTokenGenerator.make_token.
>
> On 17 March 2017 at 20:54, jann.haber via Django developers (Contributions
> to Django itself) > wrote:
>
>> Hi everybody,
>>
>> I have two sites in my project. One is for i
t; some concrete APIs to discuss might be helpful.
>>
>> thanks
>> tobias
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group an
the best,
Adam
On Sun, Apr 24, 2022 at 3:27 PM Satyabrata Sbr
wrote:
> How can i stop auto increment of primary key field of a model when some
> exception occurs inside transaction.atomic()?
>
> --
> You received this message because you are subscribed to the Google Groups
>
#x27;]
> delete_student// [name='delete_student']
> delete_issue// [name='delete_issue']
> ^media/(?P.*)$
>
> The current path, delete_issue//, didn’t match any of these.
>
> --
> You received this message because you are subscribed to the Google Groups
>
d 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:/
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
e:
> This is still the wrong place. Try django-users mailing list.
>
> El dc., 11 de maig 2022, 17:53, 'Noxx' via Django developers
> (Contributions to Django itself) va
> escriure:
>
>> Story
>>
>> Our application supports many file uploads.
>> In
>
>>
>>
>> Mit freundlichen Grüßen,
>>
>> DI Mag. Maxim Danilov
>>
>>
>>
>> +43(681)207 447 76
>>
>> ma...@wpsoft.at
>>
>>
>>
>> *From:* django-d...@googlegroups.com [mailto:django-d...@googlegroups.com]
>
expect this isn’t something Django could or should do.
>>
> --
> 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, sen
o Django's eight-monthly
release cycle.
On Thu, May 12, 2022 at 1:09 AM 'Tobias McNulty' via Django developers
(Contributions to Django itself) wrote:
> Hi Yonas,
>
> Thanks for sharing this list. Even so, in my opinion, this feature lives
> best outside of Django whe
s 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
ht
py project?
>
> Any feedback from your experience would be most appreciated.
>
> Regards,
> Tom (@taldcroft on GitHub)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
&
to file a new ticket?
>
> Thanks,
> Uri.
> אורי
> u...@speedy.net
>
> --
> 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 receivi
arning (it was with
> `python -W error::DeprecationWarning` that I didn't see the warning).
>
> Thanks,
> Uri.
> אורי
> u...@speedy.net
>
>
> On Thu, May 19, 2022 at 10:52 PM 'Adam Johnson' via Django developers
> (Contributions to Dj
angoproject.com/ticket/33732
>
> --
> 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-d
>>
>> *From:* django-developers@googlegroups.com <
>> django-developers@googlegroups.com> *On Behalf Of *mohamad ali mehdizadeh
>> *Sent:* Wednesday, May 25, 2022 1:23 AM
>> *To:* Django developers (Contributions to Django itself) <
>> django-developer
//docs.djangoproject.com/en/4.0/ref/utils/>.
>>
>> Is this the recommended way to generate secret keys for Django apps?
>> If that's the case wouldn't it make sense to write a piece of
>> documentation for that?
>>
>> Kind regards,
>> Samuel✌
>
functionality, or it is a stupid idea?
>
> Thank you
>
> --
> 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
>
ttp/response.py#L676
>>
>> Is there any reason not to do this? Feels like it wont break backwards
>> compatibility.
>>
>> Regards,
>>
>> Fab
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Django
h default but i need to use from email as
>> login user email
>> can any one clear my issue.
>>
>> Thanks
>> Arun
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django developers (Contributions to Dja
d you please show me the correct path so that I can start contributing.
>
> --
> 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 ema
es a much better use case for this
> additional positional argument to dbshell.
>
> Has this been discussed before?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)"
veral -0 in the previous thread (Shai, Florian) and you can
> count -1 from me.
>
> Best,
> Mariusz
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from
hat they might
>> benefit from the order described in the articles, I was wondering what
>> was the reason for putting them at the end.
>>
>>
>> -f
>> --
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Django deve
ilable during the template’s rendering process.
>
> *using*
>
> An optional template engine *NAME*
> <https://docs.djangoproject.com/en/4.0/ref/settings/#std-setting-TEMPLATES-NAME>.
> The search for the template will be restricted to that engine.
>
>
> --
> You received this
dateutil is
>>> stable and I think exists even before Django. I recently started using
>>> Django's timesince function in my own website, and I like the way it's
>>> translated (currently only to English and Hebrew). Do you think it's worth
>>> us
t doesn't allow something like that.
>
> Do you have any minimalist examples?
>
> --
> 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 s
;
>> Best,
>>
>> Teklit
>>
>>
>>
>> *From:* django-developers@googlegroups.com <
>> django-developers@googlegroups.com> *On Behalf Of *Kali Raja
>> *Sent:* August 11, 2022 1:10
>> *To:* Django developers (Contributions to Django itself) &l
onen
>
> --
> 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...@googlegr
cts to be
> deleted is
>
> expanded into the confirmation page. This also prevents having to scroll
>
> down to the end of a potentially very long page in order to confirm the
>
> deletion by clicking on "Yes I'm sure".
>
>
>
> [image: Screenshot
ps://docs.djangoproject.com/en/4.1/topics/http/sessions/#using-database-backed-sessions>
> sessions) (4mlo) or Django admin logs (66mlo).
>
>
>
>
>
> Mit freundlichen Grüßen,
>
> DI Mag. Maxim Danilov
>
>
>
> +43(681)207 447 76
>
> ma...@wpso
-undefined-template-variables/
. I hope that helps.
On Sat, Aug 20, 2022 at 2:34 PM 'Michael Hübner' via Django developers
(Contributions to Django itself) wrote:
> I was struggeling with a get query that just wouldn't throw any
> exceptions. Then I stubled
t passed
through, and there doesn't seem to be any reason to add further arguments.
Users who need to pass a kwarg called 'using' could always construct a
partial() themselves.
Thoughts?
Adam
--
You received this message because you are subscribed to the Google Groups
"Django
Mon, 22 Aug 2022 at 14:11, 'Adam Johnson' via Django developers
> (Contributions to Django itself)
> wrote:
>
>> Hi
>>
>> I just wrote a blog post on a late-binding bug that can occur with using
>> transaction.on_commit() with a function or lambda with
the iterable holding the backends nevertheless
> is called `engines`.
>
> If people feel this is a correct assessment, I can try improving on the
> wording.
>
> Thanks,
> Peter
>
> --
> https://desec.io/
>
> --
> You received this message because you are subscribed to
potential patches. The
> pull requests include tests and documentation.
>
> GitHub links:
> * https://github.com/shjohnson-pi/django/pull/1 (Pretty, complex)
> * https://github.com/shjohnson-pi/django/pull/2 (Ugly, simple)
> Relevant docs:
> *
> https://docs.
return f"{slug.slugged_name}-{slug.sku}"
>
>
> register_converter(Slug, "my-slug")
> ```
>
> Could changing the converter interface be something to consider?
> At least I couldn’t see any obvious problems with expecting these 2
> methods as `@classme
6)::real
Can Django have a RealField that automatically does the cast?
--
<https://swampup.jfrog.com/?utm_source=email&utm_medium=footer&utm_campaign=emea_sales&utm_term=city-tour-22>
--
You received this message because you are subscribed to the Google Groups
"Django devel
k?
>
> --
> 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+uns
pendency is problematic, however,
in most case, someone using Django will end up with this dependency anyway
as it is widely used. Django GeoIP2 contrib uses it for instance.
Best regards,
Julien
--
You received this message because you are subscribed to the Google Groups
"Django develope
ators in a third party
package, do some advocacy for why projects would need it, and show some
adoption. This would make the case for Django itself stronger.
On Thu, Sep 1, 2022 at 4:18 PM 'Julien Bernard' via Django developers
(Contributions to Django itself) wrote:
> Hi,
> I'
st at this point: implement idna validators in a third party
> package, do some advocacy for why projects would need it, and show some
> adoption. This would make the case for Django itself stronger.
>
> On Thu, Sep 1, 2022 at 4:18 PM 'Julien Bernard' via Django developers
>
> whether that should be included in Django itself. (Taking on an extra
> dependency for a small subset of users is always going to be up for debate
> — it's not a blocker per se, but it does need weighing...)
>
> Kind Regards,
>
> Carlton
>
> On Fri, 2 Sept 2022
) is the easiest way forward?
>
> Others may yet agree that this is something needed.
>
> Kind Regards,
>
> Carlton
>
> On Tue, 6 Sept 2022 at 20:23, 'Julien Bernard' via Django developers
> (Contributions to Django itself) wrote:
>
>> Thanks Carlton.
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.c
full detail of the
>> code and how to use.
>
> --
> 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
> ema
concrete cases...
>
> Thanks!
>
> Kind Regards,
>
> Carlton
>
>
>
> On Wednesday, 7 September 2022 at 08:18:13 UTC+2 Carlton Gibson wrote:
>
>> Hey Julien.
>>
>> Thanks, OK... 📖
>>
>> The Python docs have it
>> <https:
void breaking existing projects. I
> definitely think this should be part of Django rather than having the
> developers need to add this logic to each of their Django projects that
> need it.
>
> Thoughts?
>
> --
> You received this message because you are subscribed to the G
7;s the default behaviour now to orient.
>>
>> I guess it's a question of whether/how to be backwards compatible?
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)"
implement the same thing in so little time.
>>>
>>> So I tried implementing the form without using Django forms but I find
>>> it hard to deal with files as there is no documentation I can look up to.
>>>
>>> So can we add these to the documentation or
ags across many threads. I’m raising this on the mailing list not
>>>> necessarily to revisit those arguments but to ask:
>>>>
>>>>1. Is a DEP indeed the best way forward for this at this point in
>>>>time? If so I will volunteer to author it (c
Estonian).
>> On Monday, September 19, 2022 at 4:07:26 PM UTC+2 matthew.pava wrote:
>>
>>> I wonder if maybe you should look at the APPEND_SLASH setting.
>>>
>>> https://docs.djangoproject.com/en/4.1/ref/settings/#append-slash
>>>
>>>
>>&
ed 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 discu
base64
encoded, and potentially compressed.
The second section is the encoded timestamp, used to determine if it was
created too long ago on decode
The third section is the HMAC signature, base64 encoded.
- John
On Wed, Oct 5, 2022 at 4:45 PM 'Adam Johnson' via Django develop
definition so you
> don't have to repeat it. DRF ships with ModelSerializer, which does the
> same thing for its validation/conversion layer. I would strongly urge
> people to use them. Trying to force all that validation back into the model
> layer misses the bigger picture of
L}']..."
> instead of "...ARRAY[ARRAY[NULL,NULL]]..."
>
> I wonder whether this is due to django or psycopg2. Indeed, the bug is not
> reproduced
> if at least one of the element in the nested array is not null.
>
> Is the bug worth creating a ticket?
>
uite
> (https://github.com/pricemoov/django/pull/2/files)
> Would you like me to open a PR in Django or should I wait for the fix of
> the test being developed first?
>
>
> Le lun. 10 oct. 2022 à 09:39, 'Adam Johnson' via Django developers
> (Contributions to Django i
Thank you for diving into this John! All seems sensible then.
On Wed, Oct 5, 2022 at 11:53 PM 'John Whitlock' via Django developers
(Contributions to Django itself) wrote:
> Looking at the code, the hard-coded salt seems OK to me. The encoding is
> done by SessionBase.e
gt;
> To my knowledge, as things are now, there's no other way to determine
> this. The best you can do is check for a flag on AppConfig that you setattr
> if it wasn't, but there's no way to directly tell which process you're in.
>
> Thoughts?
>
> --
>
Diego with Josh Thomas and Mariusz Felisiak proposed to us to ask here on
> this list.
>
> What do you think about adding an in-memory data storage backend directly
> in the Django core?
>
> Ciao,
> Paolo
>
> --
> You received this message because you are subscribed to the
think about adding an in-memory data storage backend directly
>> in the Django core?
>>
>> Ciao,
>> Paolo
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django developers (Contributions to Django itself
e
> sections would help with clarification.
>
> --
> 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
>
1/ref/models/instances/#deleting-objects>only
>>> contains items about `delete`. Is this intentional or not, and if it is
>>> intentional, perhaps a specific call-out in both queryset and model delete
>>> sections would help with clarification.
>>>
>>&
ces/#deleting-objects>only
>>>> contains items about `delete`. Is this intentional or not, and if it is
>>>> intentional, perhaps a specific call-out in both queryset and model delete
>>>> sections would help with clarification.
>>>>
>>&g
n an article and would also like to
> > have the opinions of the Django community members interested in the
> > idea:
> >
> https://www.paulox.net/2022/10/26/about-my-proposal-for-the-django-core-sprints/
>
> --
> Paolo Melchiorre
>
> https://www.paulox.net
>
--
rted. So the solution is to use a dynamic filtering.
>>
>> Could be a good idea to include some warning about this in the
>> documentation?
>>
>> Thanks,
>> Daniel
>>
>> --
>> You received this message because you are subscribed to the Google Gro
vers (any servers) can't
>>>>>>> provide a runserver command (or a django-* mini-package to go with it)
>>>>>>> and
>>>>>>> offer what they offer in development as well as production. (Obviously
>>>>>>> that
>>>>>>&
ge_settings_dicts(a[key], b[key], path + [str(key)],
> overwrite_conflicts=overwrite_conflicts)
> elif a[key] == b[key]:
> pass # same leaf value
> else:
> if overwrite_conflicts:
> a[key] = b[key]
> else:
> conflict_path = '.'.join(path + [str(key)])
> r
the env/file loading and the instance becomes your `env` object. Rather
>> than having a CONFIG_LOADERS setting, you could define them on the Config
>> class or when you instantiate it. This is pretty similar to how goodconf
>> works today. https://github.com/lincolnloop/goodc
kwargs)sql = f'LOWER({sql})'
> return sql, paramsdef process_rhs(self, qn, connection):
> rhs, params = super().process_rhs(qn, connection)params =
> tuple(p.lower() for p in params)return rhs, params*
>
> --
> You received this message be
django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/1038c5e4-1d86-4c50-90e2-2df7b8c9894dn%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/1038c5e4-1d86-4c50-90e2-2df7b8c9894d
IR, 'static'),)
>
> Project URl - http://54.242.38.208/
> Github- https://github.com/Nishant-Sagar/BaskinSolar
>
> Thank you for your help,
> Nishant
>
>
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
&
ypes can parse request.body as they'd need
>> to do now.
>> Having a list of request.parsers, configurable in e.g. View.setup(), or a
>> middleware, or even a custom request class — essentially at any point
>> before accessing request.data — would be the follow-up
ovide parsed data from
>>>> the request body, for all request methods, together with `application/json`
>>>> content type handling (and multipart parsing for `application/json` parts
>>>> as well) **but** I would like to leave the configurable parsers step for a
>>>> la
>>> In order to get this done, I'd like to introduce this **without also
>>>>> solving the pluggable parsers issue** in the first version.
>>>>>
>>>>> That is, I would like to add `request.data` to provide parsed data
>>>&g
uest()
>> and get_language_from_path() do check the LANGUAGES setting. It is
>> likely that including the check in activate() will do some double work.
>> And yet, we found ourselves introducing the security fix.
>>
>> (I should note that this suggestion was also, independently, r
a good reason for that.
>
> Christian
>
> --
> Dr. Christian González
> https://nerdocs.at
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from t
lookups.
>
> - Rate-limiting is a no-go I think: we couldn't come to any decent
> agreement on scope,
> so it's better to live as a third-party package.
>
> - I've tried to include folks from the wider ecosystem in previous years.
> Two years ago
> we h
1 - 100 of 554 matches
Mail list logo
