+1 even though I agree with what Babatunde said I support this change as
anything that minimizes a 'gotchas' during development is very good. I
raether get an exception instead of spending half an hour debuging why my
data is not being saved. Sure once I figure it out I would learn to pay
Donald
Backward compatibility can be maintained with just a log warning to give
developer time to clean up code or throwing an exception when
`settings.DEBUG=True` and only log warning when `False`; I am not sure how
this ought to be implemented but again I am big +1 for this proposal.
On Thu,
1. How does this proposal effect default values specified on model fields?
(ModelForm processing)
2. Forgive my ignorance but who has the final say if it goes in or not? And
since it should be a yes what's next?
On Thu, Jan 12, 2012 at 8:40 PM, Tai Lee wrote:
> Ian,
>
+1,
I think they ought to be auto imported just like models.py, views.py, etc. are.
From: Emil Stenström
Sent: Thursday, January 19, 2012 8:44 AM
To: django-developers@googlegroups.com
Subject: Re: Thoughts on defining and autoimporting signals.py
On Thursday, 22 December 2011 03:49:44
; "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/d
Your guidance is required!
Would someone be kind enough and take a look at
https://code.djangoproject.com/ticket/17756
and provide feedback.
Thank you
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to
+1 and reason as previously stated: it makes sense to brake down very long tags
for readability purposes.
From: Alex Gaynor
Sent: Friday, February 24, 2012 10:12 AM
To: django-developers@googlegroups.com
Subject: Re: Revisiting multiline tags
On Fri, Feb 24, 2012 at 10:01 AM, Daniel
Tom makes a good point, but you can already store emails in the username,
they are just limited to 30 characters or fewer. Lift this length
restriction and I will be able to do everything I need without having to
wait for contrib.auth2. In the 'I use django to make a living' world the
solution
Message-
From: Luke Sneeringer
Sent: Thursday, March 15, 2012 12:28 PM
To: django-developers@googlegroups.com
Subject: Re: authentication by email
On March 15, 2012, at 11:24 , Daniel Sokolowski wrote:
Tom makes a good point, but you can already store emails in the username,
they are just
That would be a workable compromise, yes?
-Original Message-
From: Daniel Sokolowski
Sent: Thursday, March 15, 2012 12:41 PM
To: django-developers@googlegroups.com
Subject: Re: authentication by email
Yes it clearly would, however I see two possible solutions to make it more
friendly
Carl, I sincerely appreciate your feedback, however again it seems no
answers are given except more questions and considerations to consider. Why
is it so unreasonable that we expect the end developer to be able to
manually adjust their schemas, it's part of an upgrade process and it's been
limitation on the username
ought to be increased?
-Original Message-
From: Luke Sneeringer
Sent: Thursday, March 15, 2012 2:11 PM
To: django-developers@googlegroups.com
Subject: Re: authentication by email
On March 15, 2012, at 12:23 , Daniel Sokolowski wrote:
Carl, I sincerely appreciate
FYI: for my development settings I set: TEMPLATE_STRING_IF_INVALID =
'UNDEFINED_VAR: %s' which tells me which variables are undefined.
It has some quirks (password reset form in admin link fails or something) but
it’s easy to live with during development.
From: Sachin Gupta
Sent: Tuesday,
Hi Lukash, I'm 0 to this.
I find it well thought out but in my use cases I fail to see the advantage
over the WAY 3 (or WAY 4 pointed out below) and it adds a layer of
abstraction where a straight tuple or a list does the job well enough.
The choice filtering could come in handy and in the
I agree with Luke that more explicit is better then implicit when dealing with
the user.data.
From: Luke Sneeringer
Sent: Tuesday, April 03, 2012 2:46 PM
To: django-developers@googlegroups.com
Subject: Re: auth.user refactor: the profile aproach
So, after reading this, I think I really only
Can someone give me an example please where a swappable model would benefit
me as opposed to one-to-one model inheritance, FKs, or even proxy models?
Django does this very well and allows
for seamless up/down traversal.
It seems that swappable models are nothing but a different way of doing
No I can not stomach a swappable User model or the LFK approach, so thank you
for voicing your concerns.
From: Tai Lee
Sent: Wednesday, April 04, 2012 9:37 PM
To: django-developers@googlegroups.com
Subject: Re: auth.user refactor: the profile aproach
Are we really sure that we can or should
How is the final approach chosen ?
From: Alex Ogier
Sent: Friday, April 06, 2012 2:31 PM
To: django-developers@googlegroups.com
Subject: Re: auth.user refactor: the profile aproach
Tai, read https://gist.github.com/2289395 for a summary of many reasons why I
think profiles are a bad idea, and
Would it be hard for django to check during syncdb and complain that a
schema migration is required for an app? I vaguely recall being stumped
myself after changing a model, running syndb and getting my first database
integrity error. I believe even a NOTE in the tutorial clarifying that
People won’t always read all the docs – it’s a fact – so sooner or later some
other new comer will experience this issue complain, gave up and worse even
blog his/hers negative experience. We do want the newbie experience to be as
painless as possible which means popularity and growth of the
You sir are Epic!
-Original Message-
From: Carl Meyer
Sent: Friday, April 13, 2012 10:33 AM
To: django-developers@googlegroups.com
Subject: Re: extra files in startproject
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To
Hi Carl,
Looks fine to me, and I think throwing the warning at the end is indeed a
good idea.
-Original Message-
From: Carl Meyer
Sent: Friday, April 13, 2012 2:20 PM
To: django-developers@googlegroups.com
Subject: Re: extra files in startproject
--
You received this message
ons, visit this group at
http://groups.google.com/group/django-developers?hl=en.
Daniel Sokolowski
Danols Web Engineering
http://webdesign.danols.com/
Kingston, ON K7L 1H3, Canada
Notice of Confidentiality:
The information transmitted is intended only for the person or entity to which
it is address
oups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
--
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
Thank you Alex and Max for your responses.
-Original Message-
From: Alex Ogier
Sent: Friday, April 20, 2012 3:15 PM
To: django-developers@googlegroups.com
Subject: Re: GitHub migration planning
On Fri, Apr 20, 2012 at 2:58 PM, Daniel Sokolowski
<daniel.sokolow...@klinsight.com>
Works for me, Aaron why not register for a username (or do it anonymously)
and have the honours of adding it yourself? :)
https://www.djangoproject.com/accounts/register/
-Original Message-
From: Aaron C. de Bruyn
Sent: Sunday, April 22, 2012 1:27 PM
To:
Thanks Luke for the clarification.
-Original Message-
From: Luke Plant
Sent: Saturday, April 21, 2012 8:52 AM
To: django-developers@googlegroups.com
Subject: Re: GitHub migration planning
On 20/04/12 19:58, Daniel Sokolowski wrote:
Was BitBucket (mercurial system which is python
Fantastic job on the performance benchmarks, the number 4-5 seconds per check
is scary. I’ve posted a comment on django-guradian in hopes the author can
chime in onto this conversation by posting
https://groups.google.com/forum/#!topic/django-developers/6UNjPu1mcgc/discussion.
Are there any
evelopers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
Daniel Sokolowski
Web Engineer
Danols Web Engineering
http://webdesign.danols.com/
--
email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
Daniel Sokolowski
Web Engineer
Danols Web Engineering
http://webdesign.danols.com/
--
You received this message because you are subscribed to the Goog
on the
site from: djangopeople.net/danols/ to djangopeople.net/
danielsokolowski/ ?
Daniel Sokolowski
--
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 unsubs
Please disregard this message, it was meant as a reply to a thread not a new
thread.
-Original Message-
From: Daniel Sokolowski
Sent: Wednesday, May 30, 2012 12:35 PM
To: Django developers
Subject: Glad site is being brought back.
I was just about to post a public message to Simon
Super legendary, thank you for your efforts.
-Original Message-
From: Bruno Renié
Sent: Wednesday, June 06, 2012 10:47 AM
To: django-developers@googlegroups.com
Subject: Re: Glad site is being brought back.
On Wed, May 30, 2012 at 10:30 PM, Daniel Sokolowski
<daniel.soko
p at
http://groups.google.com/group/django-developers?hl=en.
Daniel Sokolowski
Web Engineer
Danols Web Engineering
http://webdesign.danols.com/
Office: 613-817-6833
Fax: 613-817-4553
Toll Free: 1-855-5DANOLS
Kingston, ON K7L 1H3, Canada
Notice of Confidentiality:
The information transmitted is inte
http://groups.google.com/group/django-developers?hl=en.
Daniel Sokolowski
Web Engineer
Danols Web Engineering
http://webdesign.danols.com/
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email t
rom this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
Daniel Sokolowski
Web Engineer
Danols Web Engineering
http://webdesign.danols.com/
--
You received this message becaus
this group at
http://groups.google.com/group/django-developers?hl=en.
--
Daniel Sokolowski
Web Engineer
Danols Web Engineering
http://webdesign.danols.com/
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To post to this group, send email to djan
ing that there is a bigger picture to consider, and one
showing how to paint that picture). However, that would leave native
Py3-only users high and dry, which isn't exactly ideal.
Yours,
Russ Magee %-)
--
Daniel Sokolowski
Web Engineer
Danols Web Engineering
http://webdesign.danols.com/
Office:
-model-blueprint
Cheers,
Jonathan
--
Daniel Sokolowski
http://webdesign.danols.com/
--
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 g
developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
Daniel Sokolowski
http://webdesign.danols.com/
--
You received this message because you are subscribed to the Google Groups "Django
developers&
quot;Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
Daniel
Yes, wheezy.web is much more bare metal compared to Django :
http://packages.python.org/wheezy.web/tutorial.html
From: Daniel Sokolowski
Sent: Wednesday, October 10, 2012 10:32 AM
To: django-developers@googlegroups.com
Subject: Re: URL dispatcher slow?
The middlewares appear to be disabled
...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
Daniel Sokolowski
http://webdesign.danols.com/
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, s
Was that necessary? I am tuning out of this conversion, it is becoming
hostile.
From: Alex Gaynor
Sent: Thursday, October 11, 2012 10:01 AM
To: django-developers@googlegroups.com
Subject: Re: URL dispatcher slow?
On Thu, Oct 11, 2012 at 6:52 AM, Daniel Sokolowski
<daniel.soko
om/group/django-developers?hl=en.
Daniel Sokolowski
http://webdesign.danols.com/
--
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,
-method-independent code
That pattern has nasty side-effects. It can be used in some cases but it fails
in most.
On Friday, November 9, 2012 8:28:47 AM UTC-7, Daniel Sokolowski wrote:
I’ve done the below in the past, the only issue with that is if you have side
effects in parent’s dispatch
as exceptional control flow. In addition, you can't do any preprocessing of the
request; for example, you can't set up any invariants before your actual view
method is called.
Best,
Alex Ogier
On Wed, Nov 14, 2012 at 8:48 AM, Daniel Sokolowski
<daniel.sokolow...@klinsight.com> wrote:
C
reason I would like this change, is so that I can do
something before dispatch that uses self.request/args/kwargs. Everything I
want can be accomplished within dispatch, but not as cleanly, or as DRY as if
this method hook existed.
On Wednesday, November 14, 2012 6:49:06 AM UTC-7, Daniel Sokolows
ers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
--
Daniel Sokolowski
http://webdesign.danols.com/
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To
uot; group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
Daniel Sokolowski
Would anyone know if there is still any momentum behind this? I like
Adamcik's approach.
On Saturday, 12 September 2009 07:42:40 UTC-4, adamcik wrote:
>
> On Thu, Sep 10, 2009 at 11:58:00AM -0400, Waylan Limberg wrote:
> >
> > Easy, get_url returns the entire url while get_url_path returns
Hi Russ, thank you for the update, yes it's a 'wish' list item, and
unfortunately my time is too limited right now to tackle the wiki.
On Monday, 25 February 2013 00:11:07 UTC-5, Russell Keith-Magee wrote:
>
>
> On Sun, Feb 24, 2013 at 12:18 AM, Daniel Sokolowski
> <elg...@danol
Dear Django Developers,
Is there any consensus on where to define your signals for models and
how to import them? I ask because to me it seems very odd that there
doesn't appear to be a standard way to add your own signals and have
them auto imported by the framework. I for example create a /
from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
--
Daniel Sokolowski
Web Engineer
KL Insight
http://klinsight.com/
Tel: 613-344-2116 | Fax: 613.63
> On Dec 29, 2011, at 8:12 AM, Daniel Sokolowski wrote:
>
> > So this would effect django because of the CSRF token check --- which
> requires the hash to be regenerated before comparing it yes?
>
> No, the problem is somewhat different. The attacker constructs a POST
>
o developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/djan
Thanks
On Thu, Dec 29, 2011 at 11:36 AM, Alex Gaynor <alex.gay...@gmail.com> wrote:
>
>
> On Thu, Dec 29, 2011 at 10:32 AM, Daniel Sokolowski <
> daniel.sokolow...@klinsight.com> wrote:
>
>> Would someone be so kind and explain why POST variables a
om.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>
--
Daniel Sokolowski
Web Engineer
KL Insight
http://klinsight.com/
Tel: 613-
58 matches
Mail list logo