Congratulations Idan! I look forward to see what you have in mind for the
admin and forms.
--
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
Just to add more confusion to this, how is truncation handled in other
languages? Is it always and ellipse? What about Chinese, Japanese,
Korean, and Arabic? I recently had to do some truncation stuff and
switch from an ellipse to an image overlay with CSS that faded out the
line at the end because
On Jan 15, 5:38 pm, Sebastian Bauer wrote:
> I think ORM supposed to have save insert and update:
>
> save(force_insert=False,force_update=False)
> update() == save(force_update=True)
> insert() == save(force_insert=True)
>
> in that situation we could have clean code and we know that update is
On Nov 25, 7:16 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
>
> However, even saying Django 1.1 is the last 2.3-compatible version and
> we drop it afterwards gives us a reasonable 3.0 support timeline, since
> our timeframe doesn't really encourage any official 3.0 support for 1.1.
I am +1
> You try making an implementation of the actual English title casing
> rules, and let me know how that goes. :P
I would prefer not, though that sounds like a challenge:)
>
> str.title is a very simple title casing function, and there's a
> reason for that.
I completely understand.
I was just
On Nov 7, 3:07 am, Ludvig Ericson <[EMAIL PROTECTED]> wrote:
> On Nov 4, 2008, at 15:26, H. de Vries wrote:
>
> > From a publishing point of view, I don't know for sure Python's method
> > is correct. Personally, I don't think so.
>
> I'd have to say, if Python's misbehaving, Python should be pa
On Oct 6, 7:11 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Mon, 2008-10-06 at 07:33 -0700, varikin wrote:
>
> [...]
>
> > I will test this, but I also want to point something out. I see a lot
> > of talk about developers not having access to Oracle, but
On Oct 6, 10:54 am, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> On Mon, Oct 6, 2008 at 9:33 AM, varikin <[EMAIL PROTECTED]> wrote:
> > Oracle is free for non production use.
>
> That's not what we mean when we say we don't have access to Orac
On Oct 5, 6:23 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> Can somebody with access to Oracle please try out the patch in #9307.
> It's an attempt to allow pickling of the Query class used by the Oracle
> backend.
>
> The most basic test is probably to create any kind of Queryset using
> "
On Aug 27, 9:34 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> The precise location is probably in ref/ although perhaps jacob could
> give a better answer. More importantly the way links are done has
> been changed, check out
> this:http://docs.djangoproject.com/en/dev/internals/documenta
Hi,
I grabbed ticket #6842 and added a patch that has some documentation
for the exceptions Django raises since I needed some of this info:)
The file I added, exceptions.txt is not in the right folder after the
docs refactor landed between my starting the patch last week and
today. I don't know
11 matches
Mail list logo