View this page "Exoweb is looking for geeky Software Engineers (Django

Dear all, We are aware that this posting is boarder case, and smells a bit like SPAM. However, we double checked with Jacob and decided to post it. If some of you guys feel qualified and tempted to join our team and work on some Django projects: great, we are looking forward to receiving your res

Re: reverse caching of foreign keys #3369

On Fri, Feb 09, 2007 at 04:35:37AM -, Gary Wilson wrote: > > On Jan 29, 4:25 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > b = Blog.objects.get(id=1) > > for entry in b.entry_set.all(): > > entry.blog is b # True > > So what if the blog with id=1 changes in between ac

Re: reverse caching of foreign keys #3369

On Feb 8, 11:10 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Does anyone else have any thoughts on this? Oh, and I forgot to mention that there is a similar ticket wanting the same thing for select_related: Ticket #17 - Metasystem optimization: Share select_related in memory http://code.d

Re: Import Statement Causes View to Fail

On Feb 6, 3:47 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Any ideas on how to proceed and diagnose this would be greatly > appreciated. You would probably have a better chance for a response by posting your issue in the django-users group: http://groups.google.com/group/django-users -

Re: Developer documentation?

On Feb 8, 10:57 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > (although it might be an idea to have a 'code cleanup' category for > reporting inline comments and bad/inefficient coding idioms). +1 --~--~-~--~~~---~--~~ You received this message because y

Re: Developer documentation?

On 2/9/07, Gary Wilson <[EMAIL PROTECTED]> wrote: > > Anyone have opinions on what would be best, file new tickets for each > instance, or maybe collect everything on a wiki page? Open tickets. Reporting problems is what tickets are for, and there is already a value of documentation for the compo

Re: Developer documentation?

On Feb 8, 9:27 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > It's not like there has been a conscious effort to _not_ comment code > - if there is an area that is lacking inline documentation, its > because whoever checked the code in thought it _was_ obvious (at the > time, at least). Po

Re: Regarding the use of sha in contrib.auth

Malcolm Tredinnick wrote: > Be careful to ensure backwards compatibility. Otherwise an > inconsequential Python upgrade (to 2.5) will mean all your previously > recorded passwords are now unusable. You need to at least be able to > check for SHA1-style hashes and use those if necessary no matter w

Re: Developer documentation?

On Feb 8, 9:27 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > Tell us where we need more comments. This is possibly one: http://code.djangoproject.com/ticket/2256 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Gro

Re: changeset 4394 broke QuerySet.iterator() interface

On Feb 8, 10:12 pm, Vadim Macagon <[EMAIL PROTECTED]> wrote: > Gary Wilson wrote: > > google ate "[4394]" off of my subject > > Err, no it didn't. Only in the web display I guess, which is what I use. --~--~-~--~~~---~--~~ You received this message because you ar

Re: reverse caching of foreign keys #3369

On Jan 29, 4:25 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > b = Blog.objects.get(id=1) > for entry in b.entry_set.all(): > entry.blog is b # True So what if the blog with id=1 changes in between accesses? What if I had b = Blog.objects.get(id=1) [ I do some other things

Re: changeset 4394 broke QuerySet.iterator() interface

Gary Wilson wrote: > google ate "[4394]" off of my subject > Err, no it didn't. --~--~-~--~~~---~--~~ 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@goog

changeset 4394 broke QuerySet.iterator() interface

google ate "[4394]" off of my subject --~--~-~--~~~---~--~~ 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 group

[4394] broke QuerySet.iterator() interface

I have opened a ticket about it: #3463 - EmptyQuerySet's iterator() method does not return a generator http://code.djangoproject.com/ticket/3463 Please review. Thanks, Gary --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google

Re: Regarding the use of sha in contrib.auth

On Thu, 2007-02-08 at 23:35 +, Rob Hudson wrote: > Should I file a bug to eventually use hashlib for >= Python 2.5? > Should I provide a patch which attempts to import hashlib and use it > if available, but otherwise falls back on md5/sha1? Be careful to ensure backwards compatibility. Otherw

Re: Regarding the use of sha in contrib.auth

On Feb 8, 5:35 pm, "Rob Hudson" <[EMAIL PROTECTED]> wrote: > Should I file a bug to eventually use hashlib for >= Python 2.5? > Should I provide a patch which attempts to import hashlib and use it > if available, but otherwise falls back on md5/sha1? Yes, file a bug so the idea is not forgotten.

Re: Developer documentation?

On 2/9/07, Gary Wilson <[EMAIL PROTECTED]> wrote: > > Now, that's actually useful. I think Django developers would benefit > from more comments like these. Granted. However, what this discussion needs is the specific, not abstract. We're all agreed that "missing comments bad, helpful comments go

Re: Developer documentation?

On Feb 8, 5:28 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > # set the current line number to 3 > line_number = 3 > > But this kind of stupidity is exactly what documentation metrics reward. I 100% agree that comments such as these are worthless. > Thats not to say that document

IntegrityError patch

Just wanted to point out that I submitted a small patch to make IntegrityError available directly from django.db. I've tested it on the postgresql and postgresql_psycopg2 backends, and it'd be nice if people could test it on the other backends. Tha

Re: Please encourage PsycoPG 2 usage (not 1!)

On 08-Feb-07, at 9:00 PM, Nicola Larosa (tekNico) wrote: > There's still people around that do not use PsycoPG 2, because of that > obsolete note in doc/install.txt . i still use psycopg1 because i prefer it -- regards kg http://lawgon.livejournal.com http://nrcfosshelpline.in/web/ --~--~

Re: Regarding the use of sha in contrib.auth

Should I file a bug to eventually use hashlib for >= Python 2.5? Should I provide a patch which attempts to import hashlib and use it if available, but otherwise falls back on md5/sha1? Some general confusion about what's going on in contrib.auth.models... There's 2 check_password methods in the

Re: Developer documentation?

On 2/8/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > Your plan seems sensible: let's make sure all the external stuff is > documented. Let's also look at stuff that is on the boundary between > internal and external -- an obvious one here is the Field class, since > we've talked previously

Re: Developer documentation?

On 2/9/07, Gary Wilson <[EMAIL PROTECTED]> wrote: > > ohloh thinks so too [1]: > "Across all Python projects on Ohloh, 13% of all source code lines are > comments. For Django, this figure is only 6%. ... and yet, for all the lack of documentation, I discovered Django in late November 2005, and by

<:::> New Data Entry Jobs $250 per month <:::>

*if you wanna Data Entry Jobs please visit this site* *http://best-job-search.50webs.com/jobs/data_entry_jobs/* If you need any information about *Data Entry Jobs* please reply me. Thanks *Tania * -- Tania Rajpot --~--~-~--~~~---~--~~ You received this messag

Re: Developer documentation?

On Feb 8, 10:22 am, "Rob Hudson" <[EMAIL PROTECTED]> wrote: > I'd like to see more inline documentation of the code. Some .py files > have this but some don't. Just an overview of what the file does, how > things are organized, maybe some concrete examples via doctests. > Something for the avera

Re: psycopg2, connection setup performance, and other issues

I've updated http://code.djangoproject.com/ticket/3459 and http://code.djangoproject.com/ticket/3460 with an improved patch that fixes any issues with weird default database settings. For the SET TIMEZONE the patch will not have any effect on django. For the autocommit patch, the implied BEG

Re: Regarding the use of sha in contrib.auth

On 2/8/07, TR <[EMAIL PROTECTED]> wrote: > Which would be right, if you couldn't use a broken hash algorithm to > login without the right password, but something that just generates > the same hash - in other words, knowing the hash (poking at the db, > SQL injection, anything) you don't need the

Re: Regarding the use of sha in contrib.auth

On 8 Feb., 18:36, "James Bennett" <[EMAIL PROTECTED]> wrote: > On 2/8/07, Rob Hudson <[EMAIL PROTECTED]> wrote: > > > Since SHA-1 was recently found to have some collisions, and since sha > > is deprecated in Python 2.5 in favor of hashlib, should an attempt to > > import hashlib be added to contr

Re: psycopg2, connection setup performance, and other issues

> Since the effect of SET TIME ZONE is reverted when the transaction > aborts, you need to COMMIT after setting it. I'll add that to the patch after I test this case. Certainly this is true if the default isolation mode isn't changed. > Regarding SET TRANSACTION ISOLATION LEVEL, this only works

Re: Regarding the use of sha in contrib.auth

On Feb 8, 9:36 am, "James Bennett" <[EMAIL PROTECTED]> wrote: > Using hashlib to generate SHA1 when it's available is something I > could get behind. Deprecating SHA1 hashes, not so much Totally agree... the news about SHA-1 made me want to look up Python's cryptographic functions as a curiosity.

Re: psycopg2, connection setup performance, and other issues

[EMAIL PROTECTED]: >> Sounds like a valid approach. Is anyone aware of a problem? I only >> remember that there were strange bugs if you don't set it up with each >> connection. Please go ahead and file a ticket for it. > > I'll file a ticket with the patch. We applied a patch yesterday for > th

Re: Regarding the use of sha in contrib.auth

On 2/8/07, Rob Hudson <[EMAIL PROTECTED]> wrote: > Since SHA-1 was recently found to have some collisions, and since sha > is deprecated in Python 2.5 in favor of hashlib, should an attempt to > import hashlib be added to contrib.auth.models (both check_password > and set_password) so when Python

Re: Developer documentation?

Rob Hudson wrote: > I'd like to see more inline documentation of the code. Some .py files > have this but some don't. Just an overview of what the file does, how > things are organized, maybe some concrete examples via doctests. > Something for the average python programmer to get a toehold into

Regarding the use of sha in contrib.auth

Since SHA-1 was recently found to have some collisions, and since sha is deprecated in Python 2.5 in favor of hashlib, should an attempt to import hashlib be added to contrib.auth.models (both check_password and set_password) so when Python 2.5 becomes more mainstream, this will be picked up by de

Re: reverse caching of foreign keys #3369

Does anyone else have any thoughts on this? On Jan 29, 4:25 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > It's a lot more efficient, for one. > > select_related() generates more code to query the database. It also > goes as "far as possible", so if the blog has a lot more relationships >

Download weather toolbar

Download Weather Toolbar - Instant weather reports, forecasts, and radar images anytime for FREE! - http://surl.in/HLWTD238206SVRAKSX --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To pos

Download weather toolbar

Download Weather Toolbar - Instant weather reports, forecasts, and radar images anytime for FREE! - http://surl.in/HLWTD238206SVRAKSX --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To pos

Re: psycopg2, connection setup performance, and other issues

> Sounds like a valid approach. Is anyone aware of a problem? I only > remember that there were strange bugs if you don't set it up with each > connection. Please go ahead and file a ticket for it. I'll file a ticket with the patch. We applied a patch yesterday for this to our local copy and its

Re: Fwd: passing arguments to the login_required decorator

#3185 fixes these also: #3372, #3407 (there may be others). That patch would make me happy. Thanks, Rob On Feb 7, 12:12 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > Forwarding this here, because the problem would go away if we could > get some attention on ticket #3185: > > http://code.djan

Re: Developer documentation?

I'd like to see more inline documentation of the code. Some .py files have this but some don't. Just an overview of what the file does, how things are organized, maybe some concrete examples via doctests. Something for the average python programmer to get a toehold into what the code is doing.

Please encourage PsycoPG 2 usage (not 1!)

Dear devs, please apply the patch in ticket #3364 as soon as possible. There's still people around that do not use PsycoPG 2, because of that obsolete note in doc/install.txt . Thank you. -- Nicola Larosa - http://www.tekNico.net/ I've heard that some people have a saying: "Pain is weakness le

Re: Developer documentation?

2007/2/8, James Bennett <[EMAIL PROTECTED]>: > > Anybody got strong feelings on this? > It takes a lot of time and it depends on the target. If it's to recruit django devs, ok. Otherwise, your django tips are maybe more appropriated. I know it's not the "official" doc but, except if you decide t

Re: Documentation issues hit list

2007/2/8, James Bennett <[EMAIL PROTECTED]>: > > Anybody else got a list like this? I'd love to aggregate as many of > them as possible and get together a "hit list" of this stuff to > document as we go forward. A complete tutorial (not just a todo-list or a blog) with customized middleware, tem

Re: File upload in newforms

Any progress on FileFields and form_for_model in newforms? Just waiting for this to make the switch to newforms. On 21 Jan, 19:30, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote: > On 1/17/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > It seems like the difference for me anyway is that even

Re: Developer documentation?

On Wed, 2007-02-07 at 23:44 -0600, James Bennett wrote: > (unrelated to the other message about documentation I just sent) [...] > One shining example is the _meta attribute on models -- there's useful > stuff in there, but unless you read the code or do some heavy-duty > introspection, you'll nev

Re: specifying newforms-admin options

If I seem lunatic, that is just because I just discovered Django. On 31 tammi, 06:24, Nate Straz <[EMAIL PROTECTED]> wrote: > With this method we could support the old style of Admin class in > models and whatever new way we want for extending the ModelAdmin class > using admin.py in each app.

Re: Documentation issues hit list

Good idea, one thing I've been meaning to do is to go through the tutorials and fix up the various glitchs (there were 4 outstanding tickets on tutorial 2 last time I looked) and merge in the information from the comments on djangoproject.com for them. Why - because the tutorials are the pretty m

Re: Developer documentation?

On Feb 8, 2007, at 06:44 , James Bennett wrote: > One shining example is the _meta attribute on models -- there's useful > stuff in there, but unless you read the code or do some heavy-duty > introspection, you'll never learn about it. Using the dispatcher to > hook into various phases of the req