s that with a correctly configured system, this
is not a problem on windows at all.
If there are any changes to make to Django, perhaps the install docs could
suggest the additions to the path I mention about as specific to installing
on windows.
--
Waylan Limberg
--
You received this message because you are
e options, visit https://groups.google.com/groups/opt_out.
>
>
If I'm not mistaken, the only part of the download url that changes
with each release is the version number -- which is referenced only a
few lines up. Why isn't the url dynamically created using version?
That's what I do for my pr
this list and you'll find various
discussions about this - mostly proposals to update the tutorials to
not use the "project" concept. Unfortunately, no one has stepped up to
do the work.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--
You received this message because you are subscri
lopers@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.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--
You receiv
h. Although I might suggest wrapping the
entire model def in a single if statement rather than individual
fields.
That way, we get the immediate needs (longer email, etc) addressed
with an interim solution but have only one path (Apps re-factor) to
the broad solution down the road.
--
\X/ /-
ince worked out the kinks.
> --
> Vernon
>
> --
> 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, se
ld be added to the
"bugs-and-features" section? Just a thought.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develo
code.djangoproject.com home page. A range of other queries have always
> been there, but there wasn't a simple "needs review" query.
>
> [1] http://code.djangoproject.com/wiki/Reports
>
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--
You received this message be
arning in the docs that create() and get_or_create() do
not run validation before writing to the db may be appropriate.
[1]: http://docs.djangoproject.com/en/dev/ref/models/querysets/#create
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--
You received this message because you are subscribed to the Goog
)
I don't know what the situation is. Will the community redux change
this?
[1]: http://code.djangoproject.com/wiki/WikiStart?action=diff=259
--
----
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post
But that hardly makes clear exactly what "accepted" actually means.
The text in that section is helpful to understanding the basic
process, but if someone changes the status of my ticket, there's no
definitive place to go and see exactly what that status means.
In fact, in reading the list o
expect is the case with
many, I just don't bother trying later if it didn't work the first
time.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to djang
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.
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups
s, 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-develop...@go
lways
go to django-users.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send
serForm(ModelForm):
> class Meta:
> # Defaults to False
> validate_model = True
Well, what if one view uses that ModelForm one way and another view
uses the same ModelForm the other way? What about
``form.is_valid(validate_model=True)``?
--
\X/ /-\ `/ |_ /-
on into core.
[1]: http://code.djangoproject.com/wiki/LoggingProposal
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googleg
within the template system.
But wouldn't that really come under a future proposal for a
better/replacement site app? Or should the current proposal be set
aside until that is solved first?
Personally, I'd prefer this proposal to land now and hope for a better
solution to the limitations of the site
On Thu, Dec 3, 2009 at 10:23 AM, Luke Plant <l.plant...@cantab.net> wrote:
> On Thursday 03 December 2009 14:18:10 Waylan Limberg wrote:
>
>> Looking though this patch I couldn't help but notice the new
>> get_messages function. What if a project has neither the
essages be wrapped in a check that request.user
exists like the new add_message function does?
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group,
tes (green lines added, red lines removed).
In fact, at first glance, that's what I thought I was looking at. One
more reason to change the colors I suppose.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~~~---~--~~
You received this message because you are sub
On Thu, Oct 29, 2009 at 11:07 AM, Waylan Limberg <way...@gmail.com> wrote:
> On Thu, Oct 29, 2009 at 10:37 AM, Johan <djjord...@gmail.com> wrote:
>>
>> I am
>> wanting to use the template engine outside the context of a django
>> project so I would not h
re() or
DJANGO_SETTINGS_MODULE is required) of the docs linked above. As
Russell mentioned settings is lazy so you don't get an import error
but you will get a RuntimeError if settings have not been configured
properly when you actually try to use your templates.
--
----
\X/ /-
case-insensitive sorting, just create your own
custom filter that does just that. You could even copy the built-in
filter to your own project/app and use it with a one or two line
change.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~~~---~--~~
ay fix a
failing test, it could cause some other test to fail that previously
passed. So I'm going to run the whole test suite anyway - or at least
all the tests for that module, etc.
Alex suggestion of --failfast seems like a much more useful way to
shorten test runs.
--
\X/ /-\ `/
rked those out
and our wrapper seems to work ok now. Yes - ok - I get the sense it
could be better.
Ever since then, any mention of logging leaves a bad taste in my
mouth. Perhaps if I was working only in 2.6 or such, this wouldn't be
an issue, but we have promised support back to 2.3.
Of course, it is
/#django.db.models.DateField
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~~~---~--~~
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
this reference to relative urls. Relative to what? The site
root? The app root? The currently viewed page? "get_relative_url" is
probably not what you actually want. "get_url_path" is.
Of course, this all really a bikeshed issue. Generally, 'he who bu
djangoproject.com/en/dev/ref/contrib/comments/custom/#django.contrib.comments.get_model
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" gr
Sigh! I guess I sent this out a little prematurely.
On Wed, Aug 12, 2009 at 3:50 PM, Waylan Limberg<way...@gmail.com> wrote:
[snip]
>
> 2. Implement ticket #11625 -- Add admin actions to the comments admin.
>
[snip]
>
> 3. Using a proxy model and custom manager, create a se
.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~~~---~--~~
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 fro
e, Django will not support
the option at all. However, if, at some point in the future the
ability to make that guarantee becomes available, then they will
reconsider this feature. Until then, the way to address this is by
improving Forms.
--
the record, no, I'm not anyone important and
don't have any inside info on the core devs opinion, but I've seen
their silence before, and given Django current state (feature freeze),
well... there minds are focused elsewhere.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~
wer is no. Of course, I'm not a core dev, so I could be
wrong, but my recollection of previous similar requests would seem to
indicate otherwise.
--
----
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~~~---~--~~
You received this message because you are subscribed
"Multiple Database Support in Django"
Mentor: Russell Keith-Magee
In any event, congrats to all.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"
t in part, the answer is for
historical reasons.
See other reasons discussed elsewhere [1]. Particularly the last
section of that post.
[1]: http://www.b-list.org/weblog/2006/jun/06/django-tips-extending-user-model/
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~~
h middlewhere and
only call it the first time. Not fun, but it's got to be better than
dealing with DJANGO_SETTINGS_MODULE and settings.py.
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
So, I would say if it worked before, that was a bug. Now it's fixed.
You'll have to edit your tag to coerce the string to an integer. Not
to hard to do, but a good idea even if it's not necessary.
[1]:
http://docs.djangoproject.com/en/dev/howto/custom-template-tags/#template-filters-that-expe
the message in the db, set "is_public" to False, but also
recognize that it has already been moderated (I believe
`comment.is_removed = True` does that).
[1]: http://code.google.com/p/django-spambayes/
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~~
e only way that will work is to accept
kwargs. So, using the above example:
>>> e.body.save_markup(formatter='markdown.markdown',
kwargs={'safe_mode': True})
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~~~---~--~~
You received this messa
/markup.py
--
----
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~~~---~--~~
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 unsub
t there.
2. ForeignKey dependent default or not.
Again, the obvious way would be with different fields.
But what about checking to see if the string passed in matches an
existing foreignkey on the model, and using that if it does - falling
back to the current behavior if
od. It would be nice to just pass that in on declaring the
field without creating my own subclass etc.
[1]: http://www.freewisdom.org/projects/python-markdown/Available_Extensions
--
----
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~~~---~--~~
You received this m
ssed here before!?
> Can i try dev this new models class or classes!?
>
> sorry about my english...
>
> att,
>
> Marcello Bontempo Salgueiro.
>
> >
>
--
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~~~---~--~~
You recei
unts/register/
[2]: http://code.djangoproject.com/settings
[3]: http://code.djangoproject.com/wiki/ServerArrangements
--
----
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers&
of scenario in a cleaner way. Or perhaps there's a more
> django-y way of doing it?
>
> Any info/pointers/tips would be appreciated.
>
> //Ed
>
> >
>
--
Waylan Limberg
way...@gmail.com
--~--~-~--~~~---~--~~
You received this message bec
Hi Dmitri,
Welcome to Django. However, this list for the development of Django
itself, not development with Django. Please ask your question on the
django-users list. <http://groups.google.com/group/django-users>
--
Waylan Limberg
way...@gmail.com
On Thu, Dec 25, 2008 at 10
. That's bad.
You see, anyone can use Django any way they want and don't have to use
any of the "shortcut" helper functions. However, everyone has to use
the request and response objects, so the code needs to make as few
restrictive assumptions as
n my production
sites. I'd say the developers time is better spent elsewhere.
Especially considering there are already working solutions out there.
I seem to recall at least one management command someone put together
that runs a multithreaded cherrypy server. Why reinvent the wheel?
Lets focus on real, usefu
though, I do see that the documentation specific to the
login_required view does not specifically mention the behavior.
Perhaps a note there would be beneficial.
[1]: http://docs.djangoproject.com/en/dev/topics/auth/#api-reference
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~---
ode.djangoproject.com/wiki/InstalledAppsRevision
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to dja
while
testing not in an egg first, but it is a real possibility. Perhaps we
shouldn't care about that one though.
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django develope
dmin to one of them. How can I contribute the modified
> templates and subclass to the Django project, that is if there is any
> interest in adding this to django ?
>
> >
>
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this
whoever asked didn't really want this, but
something else. Therefore, I don't believe anyone has provided a valid
use case for such a signal. I'd suggest searching the archives.
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received thi
is with CPython
> 2.6. I know that it should work fine anyway, but I thought it a good
> idea just to check. Has anyone looked into this?
>
> Regards,
> Zack
> >
>
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received
ng the default
get_connection method though. We'd probably still be referring to a
callable by 'dotted.path.to.a.function' syntax. And it would apply to
all models in an app, not just some.
Just a thought.
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
Yo
other way anywhere - and would find that confusing.
--
----
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django
On Thu, Aug 21, 2008 at 12:22 PM, Ian Kelly <[EMAIL PROTECTED]> wrote:
>
> On Thu, Aug 21, 2008 at 10:00 AM, Waylan Limberg <[EMAIL PROTECTED]> wrote:
>> I had thought that I read from that same source that formatting is
>> faster than concatenation (and tha
r + '/'? I can think
> of some reasons: 1) consistency with other code, 2) certainty of
> string concatenation. But is the second expression not much faster?
> (This is an honest question, no criticism or anything.)
>
> Regards,
>
an old-style `class Admin` your
> request declaration in an example in "Django at a glance" and I'm not
> sure if such bugs are known.
>
There's already a ticket for this: #8150. Although the patch might
need to be adjusted for the new docs.
added to a users app, which can then be used
in place of the one that ships with Django.
If your interested in more specifics as to why Django has chosen
silent failure, search the list archives. Seems there was a recent
discussion about it.
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~
> It's also heavily documented - *everything* has a docstring. I hope
> you enjoy,
I'll say. What, less that 50 lines of code in a 500+ line document? Wow.
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you
template, format,
> returned_dict, RequestContext(request))
>
> As I said above, the mechanism (in my case, a decorator) should
> probably try to investigate what the request looks like, rather than
> checking for stuff in the URL/other parameters but as I said, i
'2','3'])
^
SyntaxError: invalid syntax
>>> ''.join([a for a in ['1','2','3']])
'123'
However in 2.4:
Python 2.4.3 (#3, Jun 8 2007, 04:52:26)
[GCC 3.4.6 20060404 (Red Hat 3.4.6-8)] on linux2
Type "help", "copyright", "credits" or "licen
with the thought processes on Django
> development. Could someone here please elaborate on why ticket 7591 is a
> bad idea? Or better yet why its a worse idea than other approaches?
>
>
> Thanks,
> --
> - Paul
>
> >
>
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~
On Tue, Jul 1, 2008 at 8:28 PM, Arien <[EMAIL PROTECTED]> wrote:
>
> On Tue, Jul 1, 2008 at 6:10 PM, Waylan Limberg <[EMAIL PROTECTED]> wrote:
>>
>> On Tue, Jul 1, 2008 at 5:59 PM, David Durham, Jr.
>> <[EMAIL PROTECTED]> wrote:
>>>
>&g
d it. For one, that could result
in some long urls (perhaps even longer than the limit). A multi-part
form could add up to a lot pretty quick. Second, those would be some
ugly urls. And third, as mentioned above, it's not really the proper
use of GET anyway.
So, unless a strong use-case is provided, I'
ot;Settings" links up in
the top right corner.
If that doesn't work - then perhaps a dancing animation across the
newticket page. Ok, maybe not. :-D
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are su
]:
http://www.selenic.com/mercurial/wiki/index.cgi/WorkingWithSubversion#head-15564b76f3172721218d34c912aa0c31e156a94b
[2]: http://www.kernel.org/pub/software/scm/git/docs/git-svn.html
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this mess
don't want to waste
resources on every request when it's not needed. A templatetag makes
the most sense to me. It could easily be loaded into any template and
used from any app. Additionally, while its a nice-to-have feature, I
don't see it as a pre-1.0 deal breaker. Anyone could add a templatetag
to th
ings.
>
> This would also make it simpler to unify the handling of variables and
> filter expressions in django/template/__init__.py.
> >
>
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are su
On Wed, May 21, 2008 at 2:32 PM, Waylan Limberg <[EMAIL PROTECTED]> wrote:
[snip]
> in mind that markdown knows (almost) nothing about encodings. It only
> works with unicode (or ascii) text. You *must* give markdown unicode
> text and it *only* outputs unicode text. It is your
I am pretty new to django, and dont have much experience working with
> unicode, so I wanted to post here to see if anyone thought that this
> looked like a bug? If so I will log it.
>
> mike
>
>
> >
>
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~--
y were
explicitly set. Of course, this opens up a whole can-of-worms
regarding whether one tag affects the whole template, inherited
templates, a block in the template, or just a single variable lookup
or some combination of them all. Ug - don't want to go through that
again.
Hmm, before I posted this
ister, create a session [2] to get the
spam filter to go easy on you.
[1]: http://www.djangoproject.com/accounts/register/
[2]: http://code.djangoproject.com/settings
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message becaus
think again about IIS support expecially given the good
> alternatives).
>
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this grou
On Tue, May 6, 2008 at 10:45 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
> On Tue, May 6, 2008 at 8:21 PM, Waylan Limberg <[EMAIL PROTECTED]> wrote:
> >
> > Yeah, we probably should mention this in the docs, along with an
> > explanation of how to ena
bly should mention this in the docs, along with an
explanation of how to enable Markdown's safe_mode. Sure, it's
explained in the source, but the other markup filters don't offer any
extra features so I doubt most people even look unless they encounter
a problem.
t?) of your questions.
[1]:
http://groups.google.com/group/django-developers/browse_thread/thread/f4cd02d8d9389669
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django d
l
(again as mentioned previously). The data (shopping cart) would need
to be attached to the session for anonymous users, but attached to the
user for logged in users. Part of logging a user in would be to make
that transition of the data from session to user. Then deleting
> P.S. : Sorry if you get more than one copy of this message. I'm having
> problems with my mail server.
>
>
> Regards,
> Alberto
> >
>
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message
. IIRC, with queary-set refactor coming the core is not
likely to ever include support for an sqlalchemy backend. The core
devs have indicated that if and when is matures, it will remain a
third party plugin. At most it could be distributed as a contrib ap
participated in the
> lists for quite a while I do read them daily.
>
> I'd gladly volunteer as a moderator.
>
Same with me. I'm also a long-time reader with little participation.
Although I only subscribe to the digest for the users list, I read
every dev message daily. I'll vo
s adding a page to the appropriate section of the wiki
[3] would be more helpful.
[1]: http://code.djangoproject.com/simpleticket
[2]: http://www.djangosnippets.org
[3]:http://code.djangoproject.com/wiki/DjangoResources
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~-
e a few things we
obviously wouldn't want, it provides a decent starting point. I'd
suggest ignoring all the "updates" and scrolling down to the basic
tutorial at the bottom of the page for the general idea.
[1]: http://lukearno.com/projects/selector/
--
Waylan Limberg
[EMAIL PROTE
quot; %
> ENVIRONMENT_VARIABLE
> EnvironmentError: Environment variable DJANGO_SETTINGS_MODULE is
> undefined.
>
>
> i'm new to using django ,
> i would like to proceed with it ,
>
> your help will be more then appreciated
>
> firedancer
>
> >
>
--
Waylan Limb
django doesn't support markdown extensions
out of the box (there are a few legitimate exceptions).
Thank you.
[1]: http://code.djangoproject.com/ticket/2910
[2]: http://www.freewisdom.org/projects/python-markdown/Available_Extensions
--
Waylan Limberg
[EMAIL PROTECTED
t; http://developer.yahoo.com/search/ )
>
>
> >
>
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-dev
Which is not so consistent. I get the impression that this is the
motivation for dcramer's argument. If is works for create, why not for
get? Perhaps it shouldn't work for create either, although we probably
don't want to go there for backwards compatibility issues.
Just my $0.02
--
----
Wayla
ocs right, and release only when we're ready.
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email
ooking at the wiki, I couldn't help but notice that the list of
BackwardsIncompatibleChanges since the last release is longer than any
other. If the list gets to long, it can make it a real headache to
upgrade for those who only use official releases. Just a thought.
--
W
clusion is that auto_now_add should set the date only if it is
> None. Or, another solution: it should set the date upon instance
> creation, not upon saving.
>
> Do you agree?
>
> Noam
>
>
> >
>
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~---
file, which should happen
> pretty quickly. It's definitely an approach I hadn't considered, so
> I'll add it to the list of options.
>
> -Gul
>
> [1]
> http://www.modpython.org/live/mod_python-3.3.1/doc-html/pyapi-apmeth.html#l2h-32
>
> >
>
--
Wayl
there other decent solutions available?
> >
> > -Gul
> >
> > [1] http://www.modpython.org/pipermail/mod_python/2006-August/021939.html
> > [2] http://sourceforge.net/projects/poshmodule/
> > [3] http://www.zope.org/Products/ZODB3.2
> >
>
> Forgive my i
>
> I've also been reading this thread on the google developers group, and
> I'm now completely confused as to what is going on.
>
> unicode issues in multiple tickets
>
> If anyone can tell me if there is some current status on this, or how
> it works right now I'd be
th or without leading zeroes, etc.
>
This can all be done with a basic CharField in the model and some
custom newforms widgets. Which brings the question, why do we even
need a PhoneNumberField at the db level? Although I suppose it helps
with the admin, form_for_model, etc.
--
Waylan
uld django support it? At Version One?
>
>
> >
>
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
ngs, so it would be impossible to
> > autogenerate a form with choice groupings without falling back on a
> > field callback.
> >
> > Given that the groups can be safely ignored on the model, I'm not sure
> > I see the practical harm in allowing them in a model definition.
> >
On Thu, 2007-05-10 at 22:58 +, [EMAIL PROTECTED] wrote:
>
> I think what you're overlooking is that in some cases the issue of
> whether its the "best solution" is irrelevant. If the database is
> already in production or the policies are already set or controlled by
> an external entity,
angoproject.com/documentation/contributing/#submitting-patches
>
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, sen
1 - 100 of 123 matches
Mail list logo
