I'm currently looking at a bug in our application, caused by
autocomplete_fields on a ModelAdmin. It seemingly removes the field from
self.cleaned_data, which means we can no longer validate it.
I can reproduce this by removing/adding the field from/to
autocomplete_fields and resubmitting the form
unreadable mess.
--
Melvyn Sopacua
--
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...
wrote:
> Please create a new ticket (where you can reference the original one).
> If you can provide a failing test case, it would be great.
>
> Claude
>
> Le lundi 15 avril 2019 13:40:53 UTC+2, Melvyn Sopacua | 3YOURMIND a écrit :
>
>> Hi,
>>
>> I've add
Hi,
I've added a comment on the commit:
https://github.com/django/django/commit/3c4ff2176323dd20507e35658599da220fbe1741
Should I reopen the bug or create a new one? Also it would help to know
what the return type is supposed to be or what the intention of the code
is? Should the if clause be `no
rewrite them to test for a 400
response.
I don't see an easy way to restore the old behavior and stick to official
API's. Am I
missing something or is this correct?
--
Melvyn Sopacua
[1] https://gist.github.com/tschellenbach/925270
--
You received this message becau
On dinsdag 10 juli 2018 21:09:21 CEST Tim Graham wrote:
> There's an open ticket. Perhaps you would like to finish the patch.
>
> https://code.djangoproject.com/ticket/28766
> https://github.com/django/django/pull/9323
I will have a look.
--
Melvyn Sopacua
--
You rece
tpRequest.
I'm apparently not alone in this[2]. And I'm wondering why it's not stored. I
basically
would have to setup a local url pattern cache tied to view name and resolve it
again.
Is there a reason it's not stored on the resolver match?
--
Melvyn Sopacua
[1] https
Thanks, I'll see what I can integrate and I got the forms for you.
I've built mine on top of my typeshed fork (for now not bothering with
py2):
https://github.com/melvyn-sopacua/typeshed/tree/django/third_party/3/django
On Mon, Sep 18, 2017 at 1:00 AM, Maxim Kurnikov
wrote:
> https
This is merely my stick and carrot.
As mentioned on the typeshed project page and it being good practice
in general, it's a good idea to ask - before or in early stage of a
large undertaking - if someone is doing the same thing.
And I also like to ask if anyone is willing and able to contribut
with user specific key before sending.
I researched it for an upcoming project and all the hooks are in place to
create such a model and you're right, it goes beyond "batteries included".
--
Melvyn Sopacua
--
You received this message because you are subscribed to the Google Gr
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:
Hi and thanks Aemeric,
On Tue, Jun 27, 2017 at 7:55 AM, Aymeric Augustin
wrote:
> Hello Melvyn,
>
>> On 26 Jun 2017, at 12:21, Melvyn Sopacua wrote:
>>
>> keep STATIC_URL (which I rarely change) but remove STATIC_ROOT (which is
>> different per project and
On Monday 26 June 2017 20:25:58 Curtis Maloney wrote:
> On 26/06/17 20:21, Melvyn Sopacua wrote:
> > On Thursday 15 June 2017 08:14:02 Aymeric Augustin wrote:
> >
> > I see the point for the number of useless files. But in every
> > release, settings.py has been trimmed
Cause I'm seeing plenty of downsides for both new and veteran
users.
Not to mention the choice of what to remove. To keep STATIC_URL (which I rarely
change)
but remove STATIC_ROOT (which is different per project and sometimes even per
install)
is beyond me.
--
Melvyn Sopacua
--
You r
()" and inject
the right one?
You asked fr thoughts, so there's my 2c stream.
--
Melvyn Sopacua
--
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
ou already get watchdog support for
free
and can probably build on that integration to pick up watchman. Also, it's used
in
devpi[1], so it gets some scruteny from there (and devpi is awesome to
distribute
internal or augmented Django apps amongst projects).
--
Melvyn Sopacua
[1
On Tuesday 28 March 2017 03:52:59 guettli wrote:
> Am Montag, 27. März 2017 16:11:06 UTC+2 schrieb Melvyn Sopacua:
> > On Friday 24 March 2017 04:31:32 guettli wrote:
> > > I know this is a crazy idea, and it will get the "won't fix"
mbine it with all the users that have the permission assigned
directly.
The "one query" requirement conflicts with your performance requirement.
--
Melvyn Sopacua
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions t
e
exceptions and I don't think Django should cater to the exceptions.
--
Melvyn Sopacua
--
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
On Wednesday 22 March 2017 06:12:49 Tim Graham
wrote:
> This is already implemented in Django 1.11:
> https://code.djangoproject.com/ticket/27061.
Fantastic, thank you.
--
Melvyn Sopacua
--
You received this message because you are subscribed to the Google Groups
"Django
SE ... TEMPLATE ..)?
--
Melvyn Sopacua
--
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
On Wednesday 08 March 2017 18:18:26 Melvyn Sopacua wrote:
> On Monday 06 March 2017 10:10:41 David Seddon wrote:
> > Hi all,
> >
> > One thing I've always found challenging with Django is to adjust the
> > functionality of forms from other apps. An example might b
final_url.params, query.urlencode*()*,
final_url.fragment*)
*self.action_url *= *urlunparse*(*parts*)
*
--
Melvyn Sopacua
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscri
as they
should, they should not generate exceptions unless Django provides a way
to catch them. For example, if a service is unavailable that makes up a
small part of a page, I do not want the whole page to crash or information to
leak.
--
Melvyn Sopacua
--
You received this message because
*
So my objective below is to either not have anything in Storage that deals with
a
hierarchy or support a hierarchy completely.
>
> On Monday, January 30, 2017 at 11:43:27 AM UTC-5, Melvyn Sopacua wrote:
> > On Monday 30 January 2017 08:16:20 Tim Graham wrote:
> >
AM UTC-5, Melvyn Sopacua wrote:
> > Hello,
> >
> >
> >
> > the current Storage API has some inconsistencies and in short it's
> > impossible to write anything that requires a directory to be made
> > (if
> > storage is FileSystemStorage) in
x64). In doing so I had to
go
outside FieldFile.storage to have the intermediate directory created, so my
code now
isn't portable to different Storage subclasses.
Is there any interest in either of these (another?) approach and if so, what
preference?
--
Melvyn Sopacua
--
You re
ll being sent back to the server.
The solution is to use SRP, originally coined by Stanford University[1]. There
used to
be a Django enabled implementation[2], but it died a long time ago.
I don't know a well-maintained alternative and would welcome it in contrib.
--
Melvyn Sopacua
---
ed with a createcommand
management command.
--
Melvyn Sopacua
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-
ecify that form field on the
ModelForm.
So my approach would be to pass all these attributes on to ModelForm and
the widgets and for the default form fields simply ignore the attributes
you're not interested in.
I'm willing to come up with a patch if there is interest in this appr
t the devs would like to
do with above issues and what the problems are implementing or not
implementing the proposed fixes.
[1] https://code.djangoproject.com/ticket/16226
--
Melvyn Sopacua
--
You received this message because you are subscribed to the Google Groups
"Django developers&quo
31 matches
Mail list logo
