I'm curious if there are any plans to support simple urls for "RESTful
resources" in Django, especially before the 1.0 release.
See discussion here:
http://lethain.com/entry/2008/jun/13/a-django-anti-pattern-rolling-your-own-rest/
--~--~-~--~~~---~--~~
You received
It seems to me like the biggest problem with a settings module not
importing is that it's not safe to display a full error message about
that file. You can't tell if DEBUG is on, and there may well be
information in the settings that is a Bad Idea to leak on a production
server.
Also, as a friend
I'm mostly just a user, and maybe I'm being dense, here, but I just
don't see the point of this change. Why is {%%} any harder a syntax
than {{{}}} is? Is it an issue of key placement (% is shift-5 for US
keyboards)? And why would you type {%%} and then go back to insert
the keyword when you can
g {%
> stuff %}.
>
> i guess i'll spend more time studyin' pydev. switching editors every
> weekend kinda sucks, and generally with autocomplete I prefer things
> to just work.
>
> @Mike: didn't even know people were including Latex within Django.. I
> don
My apologies, I did not intend to trigger an offtopic discussion, even
a semi-related one. My intent was merely to point out that Django's
templating system is far from perfect, and that improving it is
definitely a goal of Django, even if we reject a particular change
that may appear to be for th
My interpretation of the "version" field is "the most recent version
in which the problem has been confirmed". If a user spots something
in an older version, it could be fixed or made irrelevant in SVN,
leading to a search for a problem which doesn't exist. By that
interpretation, updating the ve
> That doesn't make any sense since a fixed bug would be closed.
Not until after time is spent trying to reproduce/understand the bug.
If you know when it was last seen, you can confirm that you are
triggering it correctly, but that it no longer exists in the current
version.
>> interpretation, u
I think that http://code.djangoproject.com/ticket/13480 may be
relevant to your interests.
-FM
On Fri, May 28, 2010 at 8:22 AM, Arthur Koziel wrote:
> Hey there,
>
> my name is Arthur Koziel and I'll be working on the app loading refactor for
> this year's gsoc program. I'm currently a business
It was suggested in bug #13480 that I raise this issue "during the 1.3
feature discussion phase", which we seem to have entered.
Essentially, the issue is that a typo in my_app/views.py or any of its
dependencies can raise an error on module import and break the entire
site, leaving the user with
On Thu, Jun 3, 2010 at 4:38 AM, Russell Keith-Magee
wrote:
> [...]
> Regarding #13480 specifically -- I haven't dug into the problem in
> detail, but the approach of telling exceptions apart by inspecting the
> number of arguments doesn't fill me with joy. One of the changes in
> 1.2 was to improv
I tend to agree that #6362 should be reconsidered. Realistically
speaking, almost all form fields aren't going to want leading or
trailing spaces. The default case, therefore, should strip them,
while allowing the app writer to override that behaviour in the small
minority of cases where the whit
How do you evaluate if something is common enough to warrant inclusion?
-Charlie
On Tuesday, October 30, 2007 at 9:14:09 PM UTC-5, Malcolm Tredinnick wrote:
>
> On Tue, 2007-10-30 at 17:03 -0400, George Vilches wrote:
> > What I want to do: Assume I have an integer column in
Django supports many-to-one relationships -- the foreign keys live on
the "many", and point to the "one". So, in a simple app where you
have Comments that can get Flagged, one Comment can have many Flag's,
but each Flag refers to one and only one Comment:
class Comment(models.Model):
text = m
et".
Under the hood, it uses a standalone javascript WKT <-> OL map
translator that strips some of the magic of the current
contrib.gis.admin implementation, and a django app with some pretty
light-weight django classes to integrate with forms an
ckar...@googlemail.com wrote:
> Wow, excellent job!
>
> I've tested olwidget successful on my OpenWebGIS Project (Visit
> http://gka.homelinux.org, Login: demo demo)
>
> But I have some questions, how can I reach you?
Feel free to email me at this address. (cha..
7440e5dc4f12c11e90ec7b34cfe95eca42fb32de/doc/doc.rst#common-options
thanks,
Charlie
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-de
Russell Keith-Magee wrote:
> On Mon, Jul 27, 2009 at 9:12 AM, Charlie DeTar wrote:
>> Hi,
>>
>> I'm writing a reusable Django app that interfaces with a standalone
>> javascript library, which I hope eventually to submit for inclusion in
>> Django. I&#
plete, let
someone take over or explain what else needs to be implemented before
acceptance is gained. Closing it as won't fix is irrational and discourages
the community (and adoption of the framework).
-Charlie
PS: I can't add this as a comment to the ticket because:
<https://lh
, that code complains about the lack of __unicode__ under
CPython or Jython with your changes in place, so I must be missing
something.
Charlie
On 9/21/07, Tristan King <[EMAIL PROTECTED]> wrote:
> Ok I've been working on the problem quoted at the end of this email and have
&g
I'd like to see something like this too: my suggestion is here:
https://gist.github.com/1957251
This implementation also allows you to play with the request, args and
kwargs before they are saved on the model.
On Mar 1, 6:38 pm, Marc Tamlyn wrote:
> Hi all,
>
> Apologies if this has been raised
I would like to see something like this too. I my suggestion is here:
https://gist.github.com/1957251
This method has two advantages:
1. You can modify the request, args, and kwargs before they get saved to
the view.
2. You can execute code after request, args, and kwargs are saved but
before t
Firstly, please excuse my double post: I didn't realise posts are vetted,
so I thought it had been lost.
The very significant advantage of this being a hook (instead of overriding
dispatch) is that it allows you to call methods that require dispatch to
have already set variables (eg: self.kwarg
22 matches
Mail list logo
