On 6/28/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> Am I missing something or isn't ``request.raw_post_data`` what you
> need? AFAIK, ``request.POST`` and friends are lazy-loading, and you
> can just access ``request.raw_post_data`` to get the, um, raw post data.
>
> (See http://www.djangop
On 6/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Is it appropriate to have a test that requires sqlite, or should tests
> always use the database engine(s) specified in settings?
Tests should always use the database engines in settings.
> If they should always use the engines in settin
On 6/27/06, Mikko Nylén <[EMAIL PROTECTED]> wrote:
>
> As said in the ticket, the current behavior would probably be quite trivial
> to change and would result in more natural way to filter/get objects -- not
> to mention, it would allow the get_or_create() to work properly.
I've had a look at th
Before I check in too much more stuff to the new branch, I wanted to
poll everyone on how to properly handle the sorts of tests that
multiple db support is going to need.
I've checked in the basic config-level changes (supporting
settings.DATABASES and django.db.connections), and test file for th
On Jun 28, 2006, at 11:45 AM, Malcolm Tredinnick wrote:
> For things like applications/atomserv+xml and related ones (basically,
> everything else), data should be left unprocessed by the Django
> layers,
> I would have thought. For example, an Atom publishing request contains
> XML data that ca
Just wanted to bring attention back to this issue. A few months ago,
Ian Clelland and I submitted a ticket to allow templates to be extended
programatically, i.e. not necessarily on the filesystem. I love the
Django templating system but it seems strange that this capability is
not already in Djan
On 6/28/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> Just a quick note that I've merged Joseph's multi-auth branch to
> trunk. As far as I've seen over the past few weeks this doesn't
> break anything, but if it does let me/him know.
>
> Thanks, Joseph.
No problem. Now I get to move my p
On 28 Jun 2006, at 17:45, Malcolm Tredinnick wrote:
> But I wanted to find out if there was a reason for this behaviour
> in the
> original design (Adrian? Jacob? Simon?). Did you have something in
> mind
> to work around it? Or was it a case of "never came up before"?
I can't think of any
I've been writing an application this evening to add the Atom Publishing
Protocol to my blog and some other projects I have in mind and hit a
problem that I now realise Hugo, and no doubt others, have stumbled
across in the past, too: Django wants to treat all incoming HTTP as
though it was a form
Howdy folks --
Just a quick note that I've merged Joseph's multi-auth branch to
trunk. As far as I've seen over the past few weeks this doesn't
break anything, but if it does let me/him know.
Thanks, Joseph.
Jacob
--~--~-~--~~~---~--~~
You received this mes
Hi,
> I think we should do this.
>
> We are, after all, perfectionists.
>
> Not only do we want to show even more love toward the international
> community, I just like the idea of passing Unicode strings everywhere.
> It seems so clean.
I whole-heartedly agree! It's just much cleaner and actual
Hi all, longtime listener, first time caller...
We're learning Django now and hope to use it for next gen online surveys
later this year. We're doing an 8-language app now in Unicode in Active
Server Pages and while so far it hasn't been as painful as I'd expected,
I'd be even more drawn to Dj
On 28 Jun 2006, at 15:32, Adrian Holovaty wrote:
> The only big problem I see is that it could confuse the (unfortunately
> large) mass of programmers who don't understand Unicode yet. That is a
> big potential pitfall.
That's very true. The documentation overhead will be considerable. It
shou
On 6/28/06, Andrey Golovizin <[EMAIL PROTECTED]> wrote:
> I am using Django for about half a year and it rocks. Indeed, it would rock
> even more if it switched from using UTF-8 bytestrings to use unicode strings
> everywhere.
Some quick thoughts --
I think we should do this.
We are, after all,
On Jun 28, 2006, at 9:03 AM, Simon Willison wrote:
> As far as engineering goes, developing a water-tight test suite seems
> like a critical component for confidently adding unicode support.
I couldn't agree more strongly.
Sucks that writing good tests is so damn hard :)
Jacob
--~--~-~
On Jun 28, 2006, at 8:08 AM, Gábor Farkas wrote:
> let's imagine for a second that the unicode-django patch is done and
> available (it's not, but let's imagine it is)
>
> would there be a chance to get it applied?
Obviously that would depend on the quality of the patch and the
ramifications of
On 28 Jun 2006, at 14:43, Andrey Golovizin wrote:
> Unicode awareness may seem not a big issue for English-speakers
> (for whom
> plain ASCII is perfectly enough :)), but for others (like me) it's
> of crucial
> importance.
I don't think that's true. On today's Web there's no guarantee at al
Jacob Kaplan-Moss wrote:
> "... with too many backwards-incompatible changes ..." -- as Hugo
> points out, this will break a lot of existing code.
Well, some day Django will have to switch to unicode anyway (even Python-3000
is going to use unicode strings everywhere). Right now is a good time f
Gábor Farkas wrote:
> Jacob Kaplan-Moss wrote:
>>
>> So I think -- for now -- there are more important places to spend our
>> energy.
>
>
> 2. 'to spend our energy'. i think it's a little more complicated. if
> someone is willing to help-with/work-on django-unicode, it does not mean
> that ot
Jacob Kaplan-Moss wrote:
> On Jun 28, 2006, at 6:07 AM, Gábor Farkas wrote:
>> what i think we are missing the most is to hear about the "main"
>> developers (project owners?) (adrian, malcolm, jacob etc.) opinion
>> about
>> unicode-ification. if they think we should switch django completely to
Jacob Kaplan-Moss wrote:
> Just one
> example is the issue of template encodings -- do we need to start
> indicating that a certain template is UTF-8 or whatever?
May be I don't understand what do you mean... But this problem is not
related to internals being in unicode or not. Most templat
On Jun 28, 2006, at 6:07 AM, Gábor Farkas wrote:
> what i think we are missing the most is to hear about the "main"
> developers (project owners?) (adrian, malcolm, jacob etc.) opinion
> about
> unicode-ification. if they think we should switch django completely to
> unicode, then fine. but if t
Tom,
On Wed, 2006-06-28 at 03:09 -0700, tomass wrote:
> Hi Folks,
>
> I've just tried to add a time field to one of my models, and then I
> ran:
>
> ALTER TABLE blah ADD COLUMN blah_blah TIME;
> UPDATE blah SET blah_blah='09:00:00'
>
> I restarted apache, and I can see my current entries are s
hugo wrote:
> Hi,
>
>> So, what's stopping Django from switching to unicode? Is someone working on
>> it? And finally, what should I do to see my sweet Django fully
>> unicode-aware? :)
>
> Well, as a start, take a look at the impact analysis page at
> http://code.djangoproject.com/wiki/UnicodeI
Hi,
> So, what's stopping Django from switching to unicode? Is someone working on
> it? And finally, what should I do to see my sweet Django fully
> unicode-aware? :)
Well, as a start, take a look at the impact analysis page at
http://code.djangoproject.com/wiki/UnicodeInDjango and contribute
up
Hi,
I am using Django for about half a year and it rocks. Indeed, it would rock
even more if it switched from using UTF-8 bytestrings to use unicode strings
everywhere.
The main drawbacks of using UTF-8 strings are:
- regexps won't work on utf-8 bytestrings containing non-ASCII characters;
- l
Hi Tom,
On Wed, 2006-06-28 at 03:09 -0700, tomass wrote:
> Hi Folks,
>
> I've just tried to add a time field to one of my models, and then I
> ran:
>
> ALTER TABLE blah ADD COLUMN blah_blah TIME;
> UPDATE blah SET blah_blah='09:00:00'
>
> I restarted apache, and I can see my current entries ar
Hi Folks,
I've just tried to add a time field to one of my models, and then I
ran:
ALTER TABLE blah ADD COLUMN blah_blah TIME;
UPDATE blah SET blah_blah='09:00:00'
I restarted apache, and I can see my current entries are showing 9am
correctly in the new "blah_blah" field, but when I try to add
28 matches
Mail list logo
