No one ready to weigh in on this?
:-(
On Thu, Aug 23, 2012 at 4:17 PM, Klaas van Schelven <
klaasvanschel...@gmail.com> wrote:
> Hi all,
>
> I'm not really ready to post this as a bug, please help me correct any
> possible misunderstandings before I do so.
>
> I
Hi all,
I'm not really ready to post this as a bug, please help me correct any
possible misunderstandings before I do so.
I was gently pushed towards the future url template tag due to my
screen filling up with DeprecationWarnings
There isn't a whole lot of documentation about the new url tag. T
Hi all,
I've reopened an old issue that I keep running into:
https://code.djangoproject.com/ticket/15084#comment:20
The comment indicates quite clearly what the problem is, how it can be
reproduced and has a patch included. Can we move this forward? Would
be much appreciated.
regards,
Klaas
--
> Regards
> Serge G. Spaolonzi
>
>
>
>
>
>
>
> On Fri, Jun 22, 2012 at 9:16 AM, Karen Tracey wrote:
> > On Fri, Jun 22, 2012 at 7:23 AM, Klaas van Schelven <
> > klaasvanschel...@gmail.com> wrote:
>
> >> I've created a ticket, but
Thanks for the info
On Jun 21, 2:04 pm, Andrew Godwin wrote:
> On 21/06/12 11:58, Klaas van Schelven wrote:
>
> > Hi all,
>
> > I'm not entirely sure about the forum to ask this question: the
> > motivation is "django-users" like; but since it's
, i.e. years will
automatically be recognized as such and we no longer need to
explicitly mark them as non-localized each time they're used in a
template. But maybe that's ground for another ticket.
regards,
Klaas van Schelven
--
You received this message because you are subscribed to
our own code untill we know what the new canonical way
of doing this is.
Klaas van Schelven
--
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
Hi all,
I'm sure you've all heard of the upcoming DjangoCon Europe. Of special
interest to Django Developers will be the sprints, on the 9th & 10th
of June. We've got a very special location:
http://djangocon.eu/venues/#sprint_venue
Of further interest: the sprints will run for 48 hours straight.
Thanks!
I might add that, for someone who just wants to jump in and do some
random good for the project I found it hard to find pointers to "easy
but necessary (perhaps slightly boring) tasks" on Trac.
Maybe I'm just an edge case :-)
On Feb 1, 6:05 am, Russell Keith-Magee
wrote:
> On Tue, Feb 1
Hi all,
Maybe I wasn't clear enough last time... I've provided patches for
both these old problems and would appreciate either a brutal Linus
style rant for being such an idiot or would like to see the patches
applied. Silence... not so much.
ciao,
Klaas
On Jan 14, 6:28 pm, Klaas va
Hi,
Thanks for the tip... that obviously makes it better since
"verbose_name" is no longer there. Obviously still not perfect, since
every line still repeats itself, but thanks anyway.
Klaas
On Jan 15, 4:16 am, Sergiy Kuzmenko wrote:
> It sounds like the concern here are repetitive and untidy l
Hi all,
I've been looking into a few old unresolved issues.
http://code.djangoproject.com/ticket/11667
"Full traceback if import error before model validation" is a simple
annoyance. On the issue page (one year old) various solutions are
suggested, each with a patch. Can someone take a decision o
.
Is there any particular reason this is the case?
Has this been discussed before? I can't find any such discussion, but
that might just be my lack of google skills.
If there are no fundamental objections against fixing this I'd gladly
dive in an provide a patch.
regards,
Klaas van
gt;
> d) I think the documentation text can be changed to make it clear that
> no translation searching with short circuit is done but rather a
> build of a unique translation by merging in/overriding the different
> parts in the order documented. Also, the note about the
>
's "obviously broken")
ciao,
Klaas
On Dec 23 2010, 5:00 pm, Klaas van Schelven
wrote:
> Thanks for the notification!
>
> On Dec 23, 2:24 pm, Ramiro Morales wrote:
>
>
>
>
>
>
>
> > Klaas,
>
> > On Thu, Dec 23, 2010 at 7:43 AM, KlaasvanSch
Thanks for the notification!
On Dec 23, 2:24 pm, Ramiro Morales wrote:
> Klaas,
>
> On Thu, Dec 23, 2010 at 7:43 AM, Klaas van Schelven
>
> wrote:
> > Hi all,
>
> > Thanks for checking in 14910!
>
> > Could anyone take a serious look at
> >http://cod
uld be great if the fix could still make it to 1.3
thanks,
Klaas
On Dec 20, 2:22 pm, Klaas van Schelven
wrote:
> Ok, I split it out:
>
> Documentation incorrect: (incl.
> patch)http://code.djangoproject.com/ticket/14910
>
> Code incorrect: (patch w/ test) http://code.djangopr
Ok, I split it out:
Documentation incorrect: (incl. patch)
http://code.djangoproject.com/ticket/14910
Code incorrect: (patch w/ test)
http://code.djangoproject.com/ticket/14924
Please review,
Klaas
On Dec 19, 1:13 pm, Klaas van Schelven
wrote:
> Hi all,
>
> To be a bit more specific:
Klaas
On Dec 16, 3:25 pm, Klaas van Schelven
wrote:
> ♫ Tom ♩ tie ♭♬ tom ♪
>
> http://code.djangoproject.com/ticket/14910
>
> On Dec 5, 11:37 am,Klaasvan Schelven
> wrote:
>
>
>
>
>
>
>
> > Replying to myself here.
>
> > I'm quite su
♫ Tom ♩ tie ♭♬ tom ♪
http://code.djangoproject.com/ticket/14910
On Dec 5, 11:37 am, Klaas van Schelven
wrote:
> Replying to myself here.
>
> I'm quite sure the docs are wrong by now.
>
> Also: I think the documented behavior is not desirable. Changing
> translations per
158 for appname in settings.INSTALLED_APPS:
or making the update of a 'merge' non-destructive.
Agreed? Should I move forward w/ tests, documentation update etc. in a
bug report?
On Dec 5, 11:21 am, Klaas van Schelven
wrote:
> Hi,
>
> According
> tohttp://docs.djang
Hi,
According to
http://docs.djangoproject.com/en/1.2/howto/i18n/#using-translations-in-your-own-projects
and
http://docs.djangoproject.com/en/1.2/topics/i18n/deployment/#how-django-discovers-translations
At runtime, Django looks for translations by following this algorithm:
* First, it looks fo
Hi all,
Subtly drawing attention to
http://code.djangoproject.com/ticket/14807
A minor fix including test.
Klaas
--
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
Hi,
I believe it is customary to politely ask for attention for bugs on
this list.
http://code.djangoproject.com/ticket/14704
Contains a minor patch to the documentation that would have saved me
some headaches this afternoon.
Klaas van Schelven
--
You received this message because you are
http://code.djangoproject.com/ticket/14513
Now give me my bonus points :-)
On Oct 20, 1:05 pm, Russell Keith-Magee
wrote:
> On Wed, Oct 20, 2010 at 6:43 PM, Klaas van Schelven
>
> wrote:
> > Hi,
>
> > I'm not sure I'm following protocol here, but here it goes.
Hi,
I'm not sure I'm following protocol here, but here it goes...
django/core/management/validation.py, both in the current trunk and in
1.2.3
It says in the accompanying comment:
# Skip ordering in the format field1__field2 (FIXME:
checking
# this format would be
Sorry, missed your reply somehow,
>
> The line in question, however, should respect subclasses. So your
> example wouldn't fail in the case of a proper subclass.
>
I've heard this claim before,
But per my example above it doesn't. What am I doing wrong there?
--
You received this message because
the solution is much
appreciated.
Klaas
On Sep 27, 7:57 pm, "subs...@gmail.com" wrote:
> I thought that's what get_model did?
>
> You specify your own comments app and register your own (subclass or
> other) model within that function and its used throughout the original
&
roughout.
>
> On Sep 26, 8:28 am, Klaas van Schelven
> wrote:
>
>
>
> > Hi all,
>
> > I'm looking for a bit of input for making Django's apps a bit more
> > extendable, either by modifying Django or (preferably) by coming up
> > with a common
Hi all,
I'm looking for a bit of input for making Django's apps a bit more
extendable, either by modifying Django or (preferably) by coming up
with a common language on top op Django. The main painpoint are
extendable models. The idea of 'extendable' is that models from
reusable apps can be extend
Some more cases that would be important (not just ForeignKey):
inheriting from the VirtualModel
any kind of relationship to it (manytomany)
ModelForms
On Sep 25, 7:47 pm, Carl Meyer wrote:
> Hi all,
>
> I've seen some level of interest in the idea of a lazy foreign key
> (one whose target table
Hi all,
My 2 cents.
I think the fact that you cannot have Foreign Keys link to specific
models is a specific instance of a larger problem. It's currently not
possible to make an app which has models with any kind of extended
(subclassed) behavior. Say I create a tagging app. Now I might want
to:
32 matches
Mail list logo
