Got interested in this after a referral from the tricket tracker. Couldn't
this specific case be solved with a simple change to __getattr__ on
QuerySet?
def __getattr__(self, attr):
try:
qmethod = getattr(self.manager, attr).im_func
is_querymethod = qmethod.is_querymethod
Hi all,
New to this list but I saw this post and thought I would chime in with my
two cents. I'm not really a Django contributor (yet) but I have a fair bit
of experience using Git and Django both personally and professionally.
I can understand the hesitation for using rebase on public commits.
pitch in. Thanks!
Cheers,
--
Michael Mior
michael.m...@gmail.com
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@goog
27;ll do my
> best.
>
> Jacob
>
>
> On Tue, Jul 9, 2013 at 11:00 AM, Michael Mior
>
> > wrote:
>
>> Just wondering if there's an ETA on Django 1.5.2. Currently there's one
>> blocking issue in 1.5.1 that's preventing me from upgrading from
In light of BREACH[1] it might be worth looking into having the option of
adding a one-time pad to the CSRF token as well. Has anyone started
development on any of the suggestions in this thread yet? If not, it's
something I'd be interested in exploring.
Cheers,
--
Michael Mior
Given that, what about incorporating something like DJ-Database-URL[1] into
Django? It would be great if this could be the default if DATABASES was
left unspecified.
[1] https://github.com/kennethreitz/dj-database-url
Le mercredi 25 septembre 2013 19:45:20 UTC-4, Russell Keith-Magee a écrit :
>
he same as set_unusable_password(). It might be worth
noting more prominently in the release notes since if this is the case,
there are obvious security implications.
--
Michael Mior
michael.m...@gmail.com
Le mardi 22 octobre 2013 23:08:33 UTC-4, James Bennett a écrit :
>
> It's almost here!
>
I've used django-jsonify (https://pypi.python.org/pypi/django-jsonify/) in
the the past for this successfully. I'm not certain of the security of the
code since unfortunately I didn't have the time to do a proper audit, but
it seemed to handle some common cases.
--
Michael M
ld be considered.
--
Michael Mior
On Sunday, August 3, 2014 9:15:15 PM UTC-4, Adam Brenecki wrote:
>
> Hi all,
>
> So, a while ago, BREACH happened, and Django's CSRF implementation was
> vulnerable, as was Rails'. The paper that discussed it described a
> mitigation (a
