On Sep 10, 2:43 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
> Just a quick note: I've
> redirectedhttp://www.djangoproject.com/documentation/and everything below that
> URL tree to the new docs subdomain,http://docs.djangoproject.com/.
> Rather than spending the time to redirect individual
Hi there,
With the promise of forwards compatibility [1] that's coming with the
release of 1.0, I was wondering if there was going to be a special
mechanism to ensure no incompatibilities are mistakenly introduced in
the life of 1.x.
For example, how about forking a branch of tests (in the
On Sep 8, 7:20 pm, ikshefem <[EMAIL PROTECTED]> wrote:
> Hi, I've seen the multiple deletion proposal for djangocon.
>
> The next step after multiple delete would be multiple edits.
> In parallel, the next step concerning related objects would be adding
> some filtering to them.
>
> If you're
On Aug 19, 8:19 am, Antonio Ognio <[EMAIL PROTECTED]> wrote:
> In the login form I ask the user to type an e-mail address and then I
> wrap the view at django.contrib.auth.views.login with another view
> that copies the POST QueryDict of the request in order to make it
> mutable and have the
I'm also +1 for the change (and in fact, for any change that we would
regret not having done after 1.0 goes live). To back this up, the
above note has been hanging in the documentation for several months
(more than 8, as far as I can track back), so people could not say
that they weren't warned.
Hi,
For months, there has been a mention in the url tag's documentation:
"Note that the syntax for this tag may change in the future, as we
make it more robust." [1]
Is that mention still relevant for 1.0 and beyond?
Julien
[1] http://www.djangoproject.com/documentation/templates/#url
Errr, isn't that a duplicate of #5775?
http://code.djangoproject.com/ticket/5775
On Jul 19, 6:19 am, Rozza <[EMAIL PROTECTED]> wrote:
> New patch with tests added to the ticket.
>
> Shows the reason for the triage process!
>
> All the best
>
> Ross
>
> On Jul 18, 2:54 pm, Rozza <[EMAIL
Thanks Brian, Karen and all the NFA team for this massive
contribution!!
On Jul 19, 10:01 am, Brian Rosner <[EMAIL PROTECTED]> wrote:
> I have just recently merged the newforms-admin branch into trunk as of
> r7967 [1]. This is an extremely backward incompatible change. The
> entire admin
m, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Thu, 2008-07-10 at 22:31 -0700, Julien Phalip wrote:
> > Hi,
>
> > I see what may be a gap in the new upload system's API. Please correct
> > me or point me to the right place if I'm wrong.
>
> > Once the file
Hi,
I couldn't find a precise indication for that in the mailing list, but
please point me out if I missed it.
The roadmap clearly says that "nothing should rely on the deprecated
oldforms". Does it mean that after 1.0 goes live, oldforms will go
altogether and there won't be the need to do the
Hi,
I've spotted what I think is a bug. See ticket #7651.
Basically, there is a duplicate entry in the file list (i.e.
request.FILES.getlist(file_input_name)), when using the jQuery
MultiFile plugin. It used to work just fine before #2070 was merged.
Cheers,
Julien
[1]
To add to the case, redefining fields in ModelForm can introduce
serious problems and do more than just compromise DRY.
E.g. if you have a model field that's optional (blank=True), you need
not to forget to add 'required=False' to your form field re-
declaration...
As for dynamic choices, I
> ## Proposal
>
> To fix this I was thinking along the lines of:
>
> class ArticleForm(ModelForm):
> class Meta:
> model = Article
> fields = ['author', 'text']
> widgets = {
> 'text': Textarea(...),
> }
>
> Sound
Thanks Jacob and Jeremy for these suggestions ;)
On Jun 26, 2:30 am, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 25, 2008 at 11:24 AM, Jacob Kaplan-Moss<[EMAIL PROTECTED]> wrote:
>
> ...
>
> > I don't know that it'll make it in before 1.0 since we're focusing on
> > stuff on the
Hi all,
If you're interested and would like to see this checked in, you can
have a look at ticket #1105 [1]. There is now fully functional code +
documentation + tests.
I personally think it's a good enhancement for simple_tag as it'd make
creation of most template tags (in particular tags
developers/browse_thread/thread/62d0cefde54a50a3#
[6] http://code.djangoproject.com/ticket/1105
On Jun 18, 5:24 pm, Julien Phalip <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have just posted a patch that improves the simple_tag by allowing it
> to take the context and/or the inner bl
Hi,
I have just posted a patch that improves the simple_tag by allowing it
to take the context and/or the inner block. See the patch in ticket
#1105 [1].
It is backward compatible, and while the patch is quite simple it
would make the creation of template tag even more super easy. For
example:
Hi,
I updated the patch with regression tests and documentation. Any
feedback welcome!
Julien
On Jun 16, 9:08 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Mon, Jun 16, 2008 at 6:40 PM, Julien Phalip <[EMAIL PROTECTED]> wrote:
>
> > Hi Simon,
>
Hi Simon,
I'm a bit unsure where to stick the regression test for this. Could
you give any pointer?
Thanks!
Julien
On Jun 16, 8:16 pm, Simon Willison <[EMAIL PROTECTED]> wrote:
> On Jun 16, 10:00 am, Julien Phalip <[EMAIL PROTECTED]> wrote:
>
> > I have just a
Hi all,
I have just added a patch that allows a simple_tag to receive the
context as first argument, like inclusion_tag already does. It is
backward compatible.
I'd like to get some feedback on the code, so feel free to check it
out [1].
That issue has been raised at several occasions both on
101 - 120 of 120 matches
Mail list logo
