On 8/28/07, Rob Hudson <[EMAIL PROTECTED]> wrote:
>
> I've approached this like the following, though I'd be interested to
> hear if there is a better way. I like putting the environ settings in
> the script itself so everything is self contained (could be run from
> cron, etc)...
cron can set e
On 8/28/07, George Vilches <[EMAIL PROTECTED]> wrote:
...
> Something seems very wrong about this situation, that debugging could
> cause another query to execute (especially an unintended query), but I
> don't know what the correct way to go about fixing or preventing it.
> I've tried a bunch of
On 7/16/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
...
>
> I'll go through that diff and revert the places that are likely to
> affect something like this.
I know Malcolm's busy with QS refactor, but I wanted to note, I've
made this a ticket so it doesn't get lost:
http://code.djangoprojec
On 8/29/07, Graham Dumpleton <[EMAIL PROTECTED]> wrote:
>
> Seems I can no longer add to Django tickets as the system rejects me
> saying I am trying to submit spam, so posting here instead.
I posted for you, including you on ticket CC:
http://code.djangoproject.com/ticket/5299
--~--~-~-
On 9/5/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> I propose Friday, September 14. Some reasoning:
I'm out town / busy until the 16th, but I'm happy to see the motion.
Don't mind me, I just hope to join the next one. :)
--~--~-~--~~~---~--~~
You received
On 9/21/07, msaelices <[EMAIL PROTECTED]> wrote:
>
> The problem is the [[TOC]] proccessor situated on top:
>
> http://code.djangoproject.com/wiki/Tutorials
Works for me (now).
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Googl
It's fairly well-known that decorators are useful, but raises some issues.
Example:
==
def decorate(f):
def wrap(*args, **kwargs):
print "called"
return f(*args, **kwargs)
return wrap
@decorate
def add_to(augend, addend):
"Adds stuff"
return augend + a
On 10/4/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> On Thu, 2007-10-04 at 15:15 -0500, Jeremy Dunck wrote:
> [...]
> > Is there any interest in a patch that modifies Django's built-in
> > decorators to use functools.wraps in order to preserve things li
On 10/4/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> On 10/4/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> >
> > On Thu, 2007-10-04 at 15:15 -0500, Jeremy Dunck wrote:
> > [...]
> > > Is there any interest in a patch that modifies Django's b
On 10/4/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> On Thu, 2007-10-04 at 15:15 -0500, Jeremy Dunck wrote:
> [...]
> > Is there any interest in a patch that modifies Django's built-in
> > decorators to use functools.wraps in order to preserve things li
On 10/8/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On 10/7/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> > I note that this is a (perhaps subtle-enough) backwards-incompatible change.
>
> Can you say a bit more about how this is backwards-incompatible? I&#
On 10/8/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On 10/7/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> > http://code.djangoproject.com/ticket/5701
>
> Oh yeah, and one other thing:
>
> IANAL, but I think the Python Software License is not comp
I have a use case in which I need an exception middleware to do
something custom, but would just like to annotate the response
provided by Django's normal request exception handling.
I see the exception handling code is fairly intricate, but I'm
thinking about working up a patch that would (attem
On 10/8/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> On 10/8/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> >
> > On 10/7/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> > > http://code.djangoproject.com/ticket/5701
> >
> > Oh yeah, and
On 10/11/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On 10/8/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> > Should I follow up on this with the Python mailing list, or will you?
>
> I'd love it if you could - thanks!
OK, I quickly dug through the mai
On 10/12/07, Joe <[EMAIL PROTECTED]> wrote:
>
> I don't know how many times I've wanted to to this:
>
> return render_to_response("template.html",
> {"object":Model.objects.get(parameter=value)})
>
> instead of that exception handling.
You want get_object_or_404.
http://www.djangoproject.com/docu
On 10/15/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> So, is there a reason for the current behaviour? I would have dismissed
> it as a bug on trunk except for the test that means somebody took the
> effort to think about the current behaviour and assert it's logical.
Cache invalidation?
On 10/15/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> Barring any good reason, I want to change _get_data() back to being an
> iterator. A whole bunch of things become easier if we do that.
>
> But nothing happens without a reason, so if the keepers of the
> institutional memory could enlig
We have a use case where we'd like to store some adhoc data that's
related to a user in their session.
I note that contrib.auth.logout just deletes these session keys:
SESSION_KEY = '_auth_user_id'
BACKEND_SESSION_KEY = '_auth_user_backend'
I'd like an additional batch of keys to be deleted (or,
Hello devs,
The current trunk addslashes filter is documented as "Adds slashes.
Useful for passing strings to JavaScript, for example."
However, there are many strings that can be passed through that
filter and sill will break javascript string literals.
4131 now has a patch (from Andy Dur
There is an ongoing discussion on the psycopg list and trac regarding
the use of psycopg with multiple interpreters.
fog is proposing dropping support for multiple interpreters rather
than dealing with the (notably sticky) issues.
Trac: http://www.initd.org/tracker/psycopg/ticket/192
Mail archi
On 10/19/07, James Bennett <[EMAIL PROTECTED]> wrote:
> At some point I'd like to see the get_absolute_url() method on the
> User model rewritten to use the permalink() decorator, which would do
> away with the need to override on a per-install basis. I'm not sure
> exactly how that'd work, though
On 10/19/07, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
> I didn't file a ticket for this yest because I vaguely remember some
> opposition to the whole idea of trying to optimize current conditional
> get behavior. I'd like to raise this issue again and if it turns out
> that people like the idea I
On 10/19/07, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
> As a solution I propose a view decorator taking as a parameter a
> function calculating Last-Modified and/or ETag that takes care of all
> the mechanic of checking request headers, returning 304 Not Modified
> and setting response headers. It
Devs,
I'd like to improve the quality of Django's documentation.
I'm sure there will be many opinions on what "improvement" would mean.
I'd like to solicit ideas from django-users regarding how people use
the docs and wish they were different.
OK? I don't want to start the torrent of su
On 10/19/07, Jared Flatow <[EMAIL PROTECTED]> wrote:
>
> On Oct 18, 2007, at 8:55 PM, Marty Alchin wrote:
> > On 10/18/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> >> I'd like to improve the quality of Django's documentation.
> >
> > I c
Over on the dj-users list, this thread just came up:
http://groups.google.com/group/django-users/browse_thread/thread/e3c6569ffba10d22/8d421810d0ee84d2#8d421810d0ee84d2
django-rest just uses the existing serialization tools.
My reply there should describe the issue at hand; I just wanted to
call
This sounds quite tasty:
http://developer.postgresql.org/pgdocs/postgres/wal-async-commit.html
I'd like to add support for that.
Obviously only for postgres and 8.3, but perhaps with a setting to
turn it on or off depending on the site's needs?
I think trying to implement or modify a transactio
On 10/22/07, Antoni Aloy <[EMAIL PROTECTED]> wrote:
> I've found that caches are not i18n friendly, that is the cache is the
> same for any language. In Django snippets there is a middleware to
> deal with this fact, and I have send a patch myself to the Django
> core.
Which cache are you talking
On 10/22/07, Antoni Aloy <[EMAIL PROTECTED]> wrote:
> ...
> Please take a look at
> http://www.djangosnippets.org/snippets/443/
> Perhaps he had the same problem with order, but in any case having the
> language on any key cache will made that snippet obsolete.
I commented on that snippet to ask
On 10/30/07, webjunkie <[EMAIL PROTECTED]> wrote:
>
> I had the same problem today. I can confirm that it's fixed with a
> newer mod_python.
> http://groups.google.com/group/django-users/browse_frm/thread/5718bb2a94ebec2
>
Err, what was the old version, and what's the new version?
"Upgrade" is k
It's always bugged me a little that choice lookups are based on the raw value.
Example for discussion:
CHOICES = (
(1, 'parrot'),
(2, 'argument'),
)
class Profile(models.Model):
user = FK(User)
favorite_skit = IntegerField(choices=CHOICES)
In staticly-typed languages, and paraphr
Consider:
class Place(Model):
...
class Retaurant(Model):
place = ForeignKey(Place, unique=True)
Currently, if you have a place reference and want to get to the (0 or
1) restaurant, you do something like this:
r = place.restaurant_set.get()
Slightly more idiomatic w/ relat
On 11/6/07, Thomas Guettler <[EMAIL PROTECTED]> wrote:
>
> You can use a property. Code not tested:
Of course. I just have about 30 places to do that legwork, which seems silly.
I understand Malcolm's argument, though. This is why I asked rather
than just making the small change in my local Dj
"I've written before on mailing lists that only about two out of every
five submitted patches I review go in unchanged on a good day and that
seems to match other maintainers' experiences, too"
--
http://www.pointy-stick.com/blog/2007/11/02/development-experiences-version-control/
This obviously
On Nov 10, 2007 9:32 PM, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> I dunno ... gut feeling is we need more layers here, we already have
> triagers who are volunteering and doing a pretty good job.
If I understood the rest of your reply correctly, you meant we *don't*
need more layers here.
I have a few places that override Model.save to do additional work
after the normal functionality.
I needed to add a post_save handler to do even more stuff after that
additional work, but ran into the obvious problem: post_save is
called at the end of Model.save, and that's before the additiona
On Nov 13, 2007 10:02 AM, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 11/12/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> > Perhaps Model.save(raw=False) should become Model.save(raw=False,
> > fire_signals=True), leaving it up to the overrider to decide the
&
I had been considering switching to the GIS branch before the sprint,
but the main concern I have is that getting up on GIS features and
bugfixes also means getting up on trunk features. As an example, in
[6671], auto-escape landed on trunk. I imagine that'll take me about
a week of work to adj
On Nov 14, 2007 8:37 AM, Forest Bond <[EMAIL PROTECTED]> wrote:
...
> This is neat and all, but I don't think at actually solves the problem at
> hand.
> If save is not overridden, when does queue.dispatch() get called?
The queue.dispatch is only necessary if dispatcher.queue has been
invoked; i
On Nov 14, 2007 3:00 PM, Marty Alchin <[EMAIL PROTECTED]> wrote:
...
> And no, I'm not making a ticket for it yet, because it occurred to me
> while working on it, that it doesn't require any changes to
> PyDispatcher itself. That means, Jeremy, that you can just drop this
> somewhere and use it a
On Nov 26, 2007 11:40 AM, Marty Alchin <[EMAIL PROTECTED]> wrote:
>
> I regret not having a recent trunk to test this with, but I think
> you'd be better off storing th evalue in the object's namespace
> dictionary instead. I've recently outlined[1] how this works, and you
> can also see a great e
Does it make sense for execute_sql to raise StopIteration even when
it's called with a result_type other than MULTI?
Encountered while porting GIS. :)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django develop
FWIW, I'm interested in this approach.
I haven't had time to poke at the design, but wanted to at least give
some indication of interest since the thread's been quiet.
On Dec 6, 2007 4:46 PM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> read this first:
> http://www.davidcramer.net/code/61/handl
On Dec 10, 2007 12:18 PM, oggie rob <[EMAIL PROTECTED]> wrote:
> Shouldn't this operation occur in the newforms framework, since the
> distrust comes from user-entered data, and the decisions on what
> should be trusted and what shouldn't come from the form developer?
I dunno about you, but I get
On Dec 12, 2007 9:49 PM, nick <[EMAIL PROTECTED]> wrote:
>
> What's the name of the book? I am looking for 1 to buy.
http://www.amazon.com/Definitive-Guide-Django-Development-Right/dp/1590597257/
--~--~-~--~~~---~--~~
You received this message because you are subs
On Dec 8, 2007 10:29 PM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> We briefly discussed adding row-level dependencies (this key is
> dependent on x, y and z keys. It would be handled by storing an extra
> object in memory that stored the dependencies for the object. A simple
> reverse mapping if
On Dec 13, 2007 11:14 AM, David Cramer <[EMAIL PROTECTED]> wrote:
...
> > Since inserts are undetected by the cache in the basic proposal, are
> > you accepting only short timeouts? I imagine with your traffic, even
> > small windows of caching have big benefits. I guess the per-manager
> > tim
Here's the IRC chat from today:
Most useful bits:
django-orm-cache.googlecode.com now exists.
todo:
[10:29pm] jdunck: Investigate whether ferringb (of curse) supplied
signal performance patch
[10:29pm] jdunck: Add multiget to all cache backends
[10:29pm] jdunck: Add max_key_length, max_value_le
On Jun 13, 2007 8:29 PM, Brian Harring <[EMAIL PROTECTED]> wrote:
...
> Either way, I'm still playing locally, but I strongly suspect I'll
> wind up chucking the main core of dispatch.dispatcher and folding it
> into per signal handling; may not pan out, but at this point it seems
> the logical ne
On Dec 24, 2007 4:17 PM, Ivan Illarionov <[EMAIL PROTECTED]> wrote:
>
> I suggest using python 2.5 standard library functools.partial when it
> is available instead of django.utils.functional.curry. This functions
> are technically the same with the exception that partial is written in
> C and is
On Dec 26, 2007 7:54 AM, Ivan Illarionov <[EMAIL PROTECTED]> wrote:
>
> Django documentation states that "For performance, (uploaded) files
> are not stored in the database" Is this really true? Research
> http://research.microsoft.com/research/pubs/view.aspx?msr_tr_id=MSR-TR-2006-45
> shows that
On Dec 27, 2007 9:22 AM, kevinski <[EMAIL PROTECTED]> wrote:
>
> This worked great, however shouldn't there be some uniformity in how
> the Login_Required argument is applied in all the generic views? This
> was not the most obvious solution, and I did not see it anywhere in
> the documentation.
>
On Dec 28, 2007 11:35 AM, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> I'm happy to take care of this -- I just don't know what's involved in
> registering a channel. Could you provide some more information on whom
> to talk to about getting it done?
>
http://freenode.net/group_registration.sht
FYI, there will be a Jython sprint at PyCon, with a specific emphasis
on getting applications running, including Django.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this grou
On Jan 21, 2008 4:10 PM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> So it seems I'm finally to the point of where the code is working as
> intended, at least for the initial phase.
>
Definitely going to test this locally.
We use admin; I guess we can just make Admin.objects = Manager() to
get t
On Jan 23, 2008 7:35 PM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> Some notes I shoved into a commit today:
...
>
> If you understand by gibberish, tell me what you think
I don't understand that gibberish, but am starting to poke at the code a bit.
Quick question on CacheManager.clean's commen
DId this ever get fixed for you? :-/
On Fri, Feb 1, 2008 at 8:41 PM, John DeRosa <[EMAIL PROTECTED]> wrote:
>
> I want to starting contributing to Django, and so I tried to create an
> account in the ticket system. But I discovered (via the registration
> error message) that I already have an
Err, sorry, meant for offlist. Even more :-//
On Wed, Mar 5, 2008 at 12:36 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> DId this ever get fixed for you? :-/
>
>
>
> On Fri, Feb 1, 2008 at 8:41 PM, John DeRosa <[EMAIL PROTECTED]> wrote:
> >
> > I
On Sat, Mar 22, 2008 at 3:04 PM, Leo Soto M. <[EMAIL PROTECTED]> wrote:
...
> On the other hand, all this gymnastic is done to allow receivers which
> do not conform to the full API of a signal (i.e., does not accept all
> signal arguments). What is the real reason behind this? Signal
> "exten
Ticket #6814 is working to improve signal performance.
Feature tradeoffs:
Strong/weak receiver connections - strong-only is a big win-- about 2x
performance. Any receivers going out of scope (and not to be called)
should be explicitly disconnected if we remove support for weak
receivers.
.send
On Mon, Mar 24, 2008 at 11:11 PM, Brian Harring <[EMAIL PROTECTED]> wrote:
> On Mon, Mar 24, 2008 at 10:55:03PM -0500, Jeremy Dunck wrote:
> > One other enhancement I thought might be good is to have a
> > Model.pre_init signal
>
> Such a signal exists already last I
On Thu, Mar 27, 2008 at 10:19 AM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
>
> On Thu, Mar 27, 2008 at 9:30 AM, Michael Radziej <[EMAIL PROTECTED]> wrote:
> > I see one possible problem: I observe that mysql always slurps in the
> > whole result set from the database when you only issue
I think with field subclassing, descriptors are a good way to add this
sort of thing, but it needn't be backwards imcompatible, because any
get_XXX_display could just translate to model.XXX.display, etc.
On Thu, Apr 10, 2008 at 12:05 PM, David Cramer <[EMAIL PROTECTED]> wrote:
> Let's move get_
On Wed, Apr 16, 2008 at 6:47 PM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> Can we start setting some milestones so SVN stops being SVN :)
>
> E.g. a .97 release, or .96.2 or something. It would make things a lot
> more sane to know where you're at, as everyones using SVN now, but SVN
> chang
On Thu, Apr 17, 2008 at 11:00 AM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
>
> On Thu, Apr 17, 2008 at 10:08 AM, mrts <[EMAIL PROTECTED]> wrote:
> > This is cumbersome and error-prone, thus I propose that a SecureForm
> > or CSRFSecureForm be added to newforms that would automate the step
I noticed that RequestContext uses the dictionary supplied in the
constructor as the base of the stack, then pushes on the the results
of each context processor in turn.
Was this design intentional?
It seems like it might be useful to have the view-specific dictionary
win-- the idea being that t
On Mon, Apr 28, 2008 at 1:49 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 28, 2008 at 2:41 PM, garrettjohnson <[EMAIL PROTECTED]> wrote:
>
> >
> > @login_required, redirects to '/accounts/login'
...
>
> See http://www.djangoproject.com/documentation/settings/#login-url
>
> But you
On Tue, Apr 29, 2008 at 1:48 PM, Ed Menendez <[EMAIL PROTECTED]> wrote:
...
> django_session.session_data is made a char(40) instead of a
> varchar(40) most DB engines will make that row a fixed length row
Ed, session_data uses various (non varchar) field types.
I think you must mean session_k
Markdown 1.7, released February 17, 2008, has a backwards-incompatible change.
"
Additionally, the encoding argument has been removed from both
markdown and Markdown. Markdown expects unicode (or ascii) input and
it is the users responsibility to ensure that's what is provided.
"
The current dja
On Tue, May 6, 2008 at 6:30 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> Markdown 1.7, released February 17, 2008, has a backwards-incompatible change.
>
> "
> Additionally, the encoding argument has been removed from both
> markdown and Markdown. Markdown expects un
On Tue, May 6, 2008 at 8:21 PM, Waylan Limberg <[EMAIL PROTECTED]> wrote:
>
> On Tue, May 6, 2008 at 7:30 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> >
> >
>
> > I think there should be a branch checking the markdown version, and
> > passing
On Wed, May 7, 2008 at 11:53 AM, rcs_comp <[EMAIL PROTECTED]> wrote:
...
> Maybe I am reading too much into the comment, but I would like to
> encourage you to steer clear of the attitude behind this statement.
And I'd encourage you to quote in context-- a user had repeatedly
marked the ticket
On Tue, May 13, 2008 at 10:24 PM, Mike Chambers <[EMAIL PROTECTED]> wrote:
...
> request.session['form_post_data'] = request.POST.copy()
> request.session['foo'] = "bar"
>
> Then, in another request:
>
> print request.session.keys()
> prints []
>
Definitely sounds like a bug.
What revision of Dj
On May 14, 2008, at 9:26, "Adrian R." <[EMAIL PROTECTED]>
wrote:
> the problem is as faras I understood it, that the view is first
> processed completely in the
> database before it returns the result-slice. So it takes as long as it
> takes without a LIMIT or WHERE. That's the reason why I
On Wed, May 14, 2008 at 10:31 AM, narendra.tumkur
<[EMAIL PROTECTED]> wrote:
>
> Hi guys,
> Trying to edit django code and keep running into indentation problems.
> Have tried XCode, Textmate and JEdit on Mac OS X.
>
> What do you guys use?
django-dev is a mailing list for discussion of developmen
Prior to PostgreSQL 8.3, non-text types were implicitly converted to text.
This allowed things like the following:
class Log(models.Model):
actor = models.CharField(...)
>>> Log.objects.filter(actor=1).count()
===
With 8.3, this fails because there's no operator between text and integer.
501 - 577 of 577 matches
Mail list logo
