t 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 me
hile setting it to False
would leave 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
orked 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/#templat
On Tue, Mar 24, 2009 at 3:14 PM, eXt wrote:
>
> On 24 Mar, 15:26, Waylan Limberg wrote:
>> Well, you are using the `stringfilter` decorator, which, according to
>> the docs [1], "will convert an object to its string value before
>> being passed to your function.&
e 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 the Googl
torical 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
--~--~-~--~~~---~--~~
You receiv
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
"Django developers" group.
To p
7;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 to the Google Groups
nd bring it up during the next
proposal phase if it matters that much to you.
I don't mean to be dismissive of something some of you obvious care a
lot about, but this discussion has gone on endlessly and hasn't really
gone anywhere. And for the record, no, I'm not anyone importa
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.
--
----
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg
--~--~-~--~~~---
My point is 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 thi
.
[1]:
http://groups.google.com/group/django-users/browse_thread/thread/0fe48a0b635f59ee
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" g
.
> >
> > 2) form_for_model can't invent groupings, 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 se
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
s, with 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.
--
Wa
uce for you) then
> for now you should explicitly encode from it to utf-8 until Django
> starts doing it automatically.
>
> 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 iss
r had a need to do something like this? If so,
> > are 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://ww
only reload the one 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
>
&g
t;
> The conclusion 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]
--~--~-
e then;
Looking 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 thoug
a 180 on this. Lets get
the docs 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
d=3)
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 $
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
le %s is undefined." %
> 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
>
> >
tensions - mostly because 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
--
W
this. Although, there are 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/
--
--
ippet, perhaps 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]
--~--~-~--~---
ngo 0.90 -- and although I haven't 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 li
ntication/#default-permissions
>
> The docs state that the permissions only show up "are created" when
> you have in your model
> "class Admin"
>
> However this is not the case. Even if you you don't denote class Admin
> the permissions are
on this list about
the branch. 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
pplication settings from it.
>
> ¿What do you think about it?
>
> 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 PROTEC
crafted model
(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
r all (most?) 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
&quo
, we probably 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
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
ybe you
> should 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.
what to register, 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
ult and fail silently only 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
aga
7;pre')
>
> 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]
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 re
s an easy mistake for newer users to make. Now
that you've been filled in on the details, you'll know how to proceed
next time. Don't ever hesitate to contribute to Django.
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received
) un-escaped and un-quoted strings.
>
> 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 t
101 - 142 of 142 matches
Mail list logo
