Re: UNICODE and newforms

> I see several ways how to solve this problem: > > 1) migrate django to unicode aka big bang approach +1 from me. I'm also working with Django with a language that has many "funky characters". I, too, am not very experienced with Python and unicode, but it's still a major pain sometimes. It wou

That would be *cookieless* [was: Stateless sessions almost here]

Brian Beck wrote: > So I'm working on a stateless sessions app that people will be able to > swap with django.contrib.sessions in their settings if they need that > (a recent post mentioned mobile phone browsers for example, apparently > they don't support cookies?). I don't actually care that muc

Stateless sessions almost here

Hey, So I'm working on a stateless sessions app that people will be able to swap with django.contrib.sessions in their settings if they need that (a recent post mentioned mobile phone browsers for example, apparently they don't support cookies?). I don't actually care that much but I thought it w

<<= END OF THE WORLD =>>

[image: Ending Began]End of the World !!! Begins[image: Ending Began] [image: Cracking Starts]<

Re: Newforms and hidden fields

Thanks for the quick implementation. I've played around with it a bit already and it works as expected. Thanks! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, se

UNICODE and newforms

Hi there, disclaimer: I am not very familiar with python's unicode implementation, it may be that I am overreacting, but after solving one unicode issue after another for the past week when I desperately need to finish my project hasn't exactly improved my patience. So if anybody sees a solution I

Re: New newforms code

> > Have you guys checked out the Widget class / capability in newforms? > That's the part that lets you define how a field should be output as > HTML. I'm definitely interested in hearing whether/how that doesn't > let you do what you want to do. I have toyed around with newforms a bit. We sho

Possible bug? Conflict between filter with related table and extra-tables?

I was trying to write a fairly complicated query to pull in content across tables in one query rather than having to break it up into many queries. In playing with this I think I found a bug. Note: I've simplified the call slightly by using a different part of the data model than what I'm rea

Model object as dict

I was retrieving field/value info from a Model object today. The docs list how to obtain the information from a query: Blog.objects.values() If I want to get a single dict from the query (ignoring error checking): blog_dict = Blog.objects.filter(pk=1).values()[:1] However, if I already have

Re: select_related() changes

It seems there are some issues with the code. Although I'm not sure why it's happening, this was causing servers to get extremely loaded, and the SQL queries werent executing properly. I had no issues when running it on runserver before we pushed it onto a live environment though. Going to look i

Proposal: Named auth backends and backend specific profiles

1. Named auth backends Right now, user logins are coupled to the actual location of an auth backend. The python dotted path of the backend is stored in the user's session when they login. If you were to move the backend to a different module, any user who was logged in via that backend would get

Re: Feature request for newforms: HTML 4

Ivan Sagalaev schrieb: > Then I don't understand why you still insist on some artificial DTD > validity that doesn't matter anything to anyone except the tool that > checks for it. Ignoring "/>" IS a reality. Whether HTML5 approves it > next year or in ten years won't change a thing... For me,

Re: Feature request for newforms: HTML 4

James Bennett wrote: > 1. I've done the content-negotiation thing before, and I don't really > want to go there again. > 2. I don't have need of any XML-specific features, so I don't really > have a valid reason to dump something that's been working remarkably > well up until now. > 3. HTML 4.01 l

Re: Feature request for newforms: HTML 4

On 1/10/07 11:06 AM, James Bennett wrote: > 4. I just feel like being ornery sometimes. Don't let him fool you -- this is actually reason #1 :) Jacob --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django devel

Re: Feature request for newforms: HTML 4

On 1/10/07, Rob Hudson <[EMAIL PROTECTED]> wrote: > I'm in the same boat. I'm curious why you don't use XHTML? In no particular order: 1. I've done the content-negotiation thing before, and I don't really want to go there again. 2. I don't have need of any XML-specific features, so I don't real

Re: select_related() changes

David Cramer schrieb: > I can do the docs, but it'd be a great time saver if you could do the > tests. I'm up to my elbows in work at the moment so :) Fine for me, then I take the tests. Michael -- noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg - Tel +49-911-9352-0 - Fax +49-9

Re: Feature request for newforms: HTML 4

James Bennett wrote: > I'm using HTML 4.01 (quite happily, I might add) and running into > annoyance with the fact that both Django's newforms and the old > manipulator system default to XHTML-style tags with no way to override > that. James, I'm in the same boat. I'm curious why you don't use

Re: select_related() changes

I can do the docs, but it'd be a great time saver if you could do the tests. I'm up to my elbows in work at the moment so :) On Jan 10, 4:37 pm, Michael Radziej <[EMAIL PROTECTED]> wrote: > Hi David, > > if you want me to write the docs or the tests, let me know. I > could deliver within a day or

Re: Feature request for newforms: HTML 4

On 1/10/07, Anne van Kesteren <[EMAIL PROTECTED]> wrote: > Well, it's reflects what's been implemented for years in browsers. Yes, but it's still not right ;) When HTML5 finalizes, then I'll feel a little more comfortable migrating to it and this won't be an issue anymore. For now, though, I'm u

Re: select_related() changes

Hi David, if you want me to write the docs or the tests, let me know. I could deliver within a day or two. Michael -- noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg - Tel +49-911-9352-0 - Fax +49-911-9352-100 http://www.noris.de - The IT-Outsourcing Company --~--~-~

Re: select_related() changes

On 1/10/07 9:23 AM, David Cramer wrote: > Not quite sure what to write in terms of the documentation :) Essentially you just need to add a few paragraphs and examples to the db_api doc (http://www.djangoproject.com/documentation/db_api/#select-related) explaining what the parameters are, and wh

Re: select_related() changes

Not quite sure what to write in terms of the documentation :) On Jan 10, 4:07 pm, "Waylan Limberg" <[EMAIL PROTECTED]> wrote: > On 1/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > I'd like this to become core functionality as I feel its needed.For that > > to happen, you will lik

Re: select_related() changes

On 1/10/07 9:07 AM, Waylan Limberg wrote: > On 1/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> I'd like this to become core functionality as I feel its needed. On the surface it looks pretty good, so I'd say you're pretty close to getting this considered for inclusion. > For that to h

Re: select_related() changes

Waylan Limberg schrieb: > On 1/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> I'd like this to become core functionality as I feel its needed. > > For that to happen, you will likely need to do everything listed here > [1]. That includes writing some unit tests for the new functionality

Re: select_related() changes

On 1/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I'd like this to become core functionality as I feel its needed. For that to happen, you will likely need to do everything listed here [1]. That includes writing some unit tests for the new functionality and documentation explaining ho

Re: Feature request for newforms: HTML 4

James Bennett wrote: > WHAT-WG's HTML5 will do away with this and make the closing slash > semantically meaningless in HTML, but that's still a ways off in the > future. Well, it's reflects what's been implemented for years in browsers. --~--~-~--~~~---~--~~ You

Re: Feature request for newforms: HTML 4

Rob Hudson wrote: > James Bennett wrote: > > So I've been poking around in the newforms code, and it appears that > > the pre-defined widgets will be producing XHTML-style output. > > I had the same thought but I wrote a quick test with an HTML 4 strict > doc-type, put an input tag in it like this

Re: select_related() changes

http://code.djangoproject.com/ticket/3275 Thanks :) On Jan 10, 2:50 pm, Nikolaus Schlemm <[EMAIL PROTECTED]> wrote: > > Any links to an example ticket so I can keep a normal format for what > > im going to post? :)take a look at the tickets with patches: > >http://code.djangoproject.com/

Re: select_related() changes

> Any links to an example ticket so I can keep a normal format for what > im going to post? :) take a look at the tickets with patches: http://code.djangoproject.com/report/12 -- cheers, Nikl --~--~-~--~~~---~--~~ You received this message becau

Re: select_related() changes

David Cramer schrieb: > Any links to an example ticket so I can keep a normal format for what > im going to post? :) General information about contributions: http://www.djangoproject.com/documentation/contributing/ There are plenty of tickets in the timeline: http://code.djangoproject.com/timeli

Re: select_related() changes

Any links to an example ticket so I can keep a normal format for what im going to post? :) On Jan 10, 11:40 am, "Honza Král" <[EMAIL PROTECTED]> wrote: > On 1/10/07, David Cramer <[EMAIL PROTECTED]> wrote: > > > > > What's the svn command for generating the diff?svn diff > > you go into the top-l

Re: Have a look at django.newforms

Ok, thank you for the answer. I am using newforms with an older django codebase so thats why I ran into this. On Jan 9, 3:38 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote: > On 1/9/07, serbaut <[EMAIL PROTECTED]> wrote: > > > fields.py tries to get settings.URL_VALIDATOR_USER_AGENT with: > > >

Re: select_related() changes

On 1/10/07, David Cramer <[EMAIL PROTECTED]> wrote: > > What's the svn command for generating the diff? svn diff you go into the top-level directory of your checked-out django, do svn diff and capture the output > > On Jan 10, 11:07 am, Michael Radziej <[EMAIL PROTECTED]> wrote: > > [EMAIL P

Re: select_related() changes

What's the svn command for generating the diff? On Jan 10, 11:07 am, Michael Radziej <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] schrieb: > > > Updated paste:http://dpaste.com/hold/4539/Thanks for your code, and I would > > have good use for some > improvements on select_related. But it's har

Re: newforms - handling foreignkeys

Hi Philipp, On 1/10/07, Philipp Keller <[EMAIL PROTECTED]> wrote: > > Hi there > > There's a problem with newforms with foreignkey/choicefield. > > In the following example, category is a ForeignKey field: > > >>> EntryForm = forms.models.form_for_model(Entry) > >>> print EntryForm.fields.keys() >

Re: select_related() changes

[EMAIL PROTECTED] schrieb: > Updated paste: http://dpaste.com/hold/4539/ Thanks for your code, and I would have good use for some improvements on select_related. But it's hard for me to see what changed in the paste. The common way to suggest or discuss changes on this list is to open a ticke

Re: select_related() changes

http://dpaste.com/hold/4541/ :) On Jan 10, 8:39 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Updated paste:http://dpaste.com/hold/4539/ > > Should be no problems now :) > > On Jan 10, 8:22 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > > Code Source:http://dpaste.com/hold/4538/ >

newforms - handling foreignkeys

Hi there There's a problem with newforms with foreignkey/choicefield. In the following example, category is a ForeignKey field: >>> EntryForm = forms.models.form_for_model(Entry) >>> print EntryForm.fields.keys() ['title', 'body', 'category'] >>> data = dict(title="lorem", body="lorem ipsum dol