I agree with Eric and my experiences back it up. Most of the people
who want to custom form widgets are the ones who are unprepared to dig
into Django/Python code. The easier we can make creating/extending
form widgets the better.
This looks like what I'll be sprinting on at DjangoCon. :)
Danny
ontrols are out of the hands of the designer
and in the hands of the developer.
Until I get around to refactoring django-uni-form,
Daniel Greenfeld
pydanny.com
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To pos
atomic.
I leave all the magic stuff to smart people. ;)
--
'Knowledge is Power'
Daniel Greenfeld
http://pydanny.blogspot.com
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to djang
hed by
django.contrib.admin. I think this is is the better, easier way to go
because it keeps Django's core scope smaller. Which makes advancement
of the framework easier for the hard-working people who contribute to
it.
--
'Knowledge is Power'
Daniel Greenfeld
http://pydanny.bl
On Wednesday, April 4, 2012 9:41:23 AM UTC-7, Adrian Holovaty wrote:
> 2012/4/3 Łukasz Langa :
> > Explicit choice values::
> >
> > GENDER_MALE = 0
> > GENDER_FEMALE = 1
> > GENDER_NOT_SPECIFIED = 2
> >
> > GENDER_CHOICES = (
> > (GENDER_MALE, _('male')),
> > (GENDER_FEMALE, _('femal
s stuck on Django 1.3, which has some security implications.
2. django-nonrel is unsupported. It switched maintainers and the
current maintainer is not working on it.
3. [pydanny opinion warning] django-nonrel wasn't adopted in Django
core because it lacked adequate documentation and tests.
4. [pyd
On Sunday, June 24, 2012 10:31:41 PM UTC+8, Cezar Jenkins wrote:
>
> I'm only lightly involved in the project, but there is some misinformation
> going around about it.
>
> On Sun, Jun 24, 2012 at 5:47 AM, Daniel Greenfeld
> wrote:
>
>>
>>
>> We eva
When we changed over to Heroku for hosting and went with the 'www' prefix,
somehow the redirects to the new location have been failing. I submitted
the changed url to https://www.djangoproject.com/community/ but it hasn't
picked up the change. I'll try again.
On Thursday, July 19, 2012 2:41:28
I'll toss in our own djangopackages.com as well as a resource. :-)
On Monday, September 17, 2012 10:00:39 PM UTC+2, AJHMvanRatingen wrote:
>
> I'm not an expert in packaging, I've released a few apps, but my novice
> eyes caught some things:
> * Bullet 6 under "Packaging your app" mentions the ma
is to make the Python installation story on Windows easier.
It's not the fun or easy answer, and maybe we need to convince Microsoft to
throw money and resources at the problem. Since Python and Django supported
on Azure, this may be the perfect time to make such a request.
--
'Knowledge
mprovement besides an official
working implementation of the app. Off the top of my head here are a couple
of items:
1. The new tutorial intros are nice but missing some pieces. I'll document
this in tickets soon.
2. Page 2 of the tutorial is too long. People start copy/pasting very
early, an
I agree that email-as-username should be a built-in User abstract model (or
something) in Django. It's an incredibly common use case and for once I
think Django could use some additional functionality.
+1 to email as username model in core.
Danny
On Sunday, March 3, 2013 10:21:55 AM UTC-8, Flo
No modern project uses ifequal. No one recommends it. I argue it is taking
up valuable bytes in the project. Let's remove it.
Reference https://code.djangoproject.com/ticket/25236
In there you'll see Tim Graham mentions that older Django projects may push
back on it, and suggests that a good me
step towards NoSQL
> in Django.
NoSQL != cloud, so I changed the name, slug, and description for
http://www.djangopackages.com/grids/g/cloud/
It is now: http://www.djangopackages.com/grids/g/nosql/
Perhaps it should even be nosql-backends?
Daniel Greenfeld
--
You received this message because
of use to
them or if it needs to be updated to the latest code base.
Thanks!
--
'Knowledge is Power'
Daniel Greenfeld
http://pydanny.com
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group
y done his homework and put a lot of thought into this critical part
of Django.
I'm not a core developer my vote doesn't count, but I'm giving it anyway. +1
from me.
Daniel Greenfeld
pyda...@gmail.com
--
You received this message because you are subscribed to the Google Groups
Which means the task of moving data from one
database to another, or applying non-Django tools to the data suddenly has
become much more complicated - to the point that non-Django people looking
at the database will rightly wonder why the framework is obfuscating data.
Daniel Greenfeld
One of the things that I think would be wonderful is to see this and other
issues such as server specific settings actually described in a Django best
practices document. And not as part of the wiki.
--
You received this message because you are subscribed to the Google Groups
"Django developer
Can we assume it will be separated out? While none of us on the list use
admindocs or care, a decent number of beginners seem to like to use it.
--Daniel Greenfeld
On Thursday, July 25, 2013 7:21:08 PM UTC+2, Julien Phalip wrote:
>
> On Jul 25, 2013, at 5:29 AM, Aymeric Augustin <
7;ve had this request several times for security-related
packages, database connectors, and other things. We're not sure about the
API yet, but there you go.
--
'Knowledge is Power'
Daniel Greenfeld
Principal at Cartwheel Web; co-author of Two Scoops of Django; Maintainer
of Djang
Seth,
I like it a lot. Is there any chance you can provide a focused version per
Class-Based View?
Daniel Greenfeld
On Sunday, August 18, 2013 10:03:59 PM UTC+2, Seth Moon wrote:
>
> I believe it would be beneficial to the Django developers and users if the
> documentation included
Javair,
Not to put a fine point on it, but did you actually bother to look at
djangobook.com? It says: "A warning about this edition" on the front page
and then goes into asking that users not work on it. Is this why you don't
want to work on it?
Daniel Greenfeld
On Monday, O
t happen, just as it would be nice to see
djangobook.com taken off the wikipedia page until it does get updated.
In the meantime, unless no core developer objects, after getting yet
another emailed question about mod_apache deployment (thanks to
http://www.djangobook.com/en/2.0/chapter12.html)
27;ll find some
attempts).
Fourth, because of the third issue, we risk complaints of plagiarism. The
content already exists, it's just a matter of finding it. GSOC funding for
code examples that already exist? No. No. No. Bad idea!
Daniel Greenfeld
On Monday, February 24, 2014 2:28:41 AM UTC-
2013. I can only guess that
djangobook.com will be updated as well.
I apologize for not considering the ownership issues in my first email in
this discussion.
Daniel Greenfeld
On Monday, February 24, 2014 8:39:41 AM UTC-8, Daniel Greenfeld wrote:
>
> After due consideration, I think up
ocumentation of django.contrib.auth.
--Daniel Greenfeld
On Friday, August 1, 2014 9:17:30 AM UTC-7, Collin Anderson wrote:
>
> It seems to me, in any case, the first step is to get django-registration
> actively maintained again. James Bennett is welcoming proposals of people
> to take over
On Sunday, August 10, 2014 2:37:01 AM UTC-7, Aymeric Augustin wrote:
Using GitHub for auth a giant +1 from me.
For me, this ranks up with the SVN to Github move as a: "Why hasn't this
been done already?"
Daniel Greenfeld
co-author Two Scoops of Django
--
You received this
Thanks for the mention, but I haven't had time to work or maintain that for
months. I'm not sure how it works with the upcoming Django 1.7. Also, for
the sake of simplicity, the default skin for it is bootstrap 3. Any CSS in
there is per skin, and probably doesn't belong in this discussion.
On
28 matches
Mail list logo
