On Thu, Mar 17, 2011 at 9:26 PM, Calvin Spealman wrote:
> -1 On django manipulating PYTHONPATH
+1 On encouraging people to keep their applications out of their project!
>
I think, it's a good idea to add new option to startapp command for create
Django application out the
On Fri, Mar 18, 2011 at 12:05 AM, Carl Meyer wrote:
>
>
> On 03/17/2011 05:36 AM, Tom Evans wrote:
>> I strongly disagree here. Django shouldn't be doing magic with my
>> PYTHONPATH, if I want stuff in my PYTHONPATH, I'll darn well put it
>> there.
>
> Hear, hear! I'm only a
On Thu, Mar 17, 2011 at 09:33:43AM -0500, Jacob Kaplan-Moss wrote:
> On Wed, Mar 16, 2011 at 4:24 AM, Johannes Dollinger
> wrote:
> > I would be nice if support for composite primary keys would be
> > implemented as a special case of general composite fields. There
> >
-1 On django manipulating PYTHONPATH
+1 On encouraging people to keep their applications out of their project!
On Thu, Mar 17, 2011 at 1:08 AM, Tai Lee wrote:
> If we're talking about the lowest common denominator and keeping
> things simple, this is what I think we'd
On 17 March 2011 16:58, Carl Meyer wrote:
> Hi Marco,
>
> On 03/17/2011 10:44 AM, Marco Louro wrote:
>> I don't really know how to approach this issue the best way, so I'm
>> just going to be direct, I'd love to see Django provide support for
>> django.core.urlresolvers.reverse
On 03/17/2011 05:36 AM, Tom Evans wrote:
> I strongly disagree here. Django shouldn't be doing magic with my
> PYTHONPATH, if I want stuff in my PYTHONPATH, I'll darn well put it
> there.
Hear, hear! I'm only a weak +0 on the entire idea of documenting a
"standard" project layout, as I think
Hi Marco,
On 03/17/2011 10:44 AM, Marco Louro wrote:
> I don't really know how to approach this issue the best way, so I'm
> just going to be direct, I'd love to see Django provide support for
> django.core.urlresolvers.reverse (at least) on the client (in
> JavaScript).
I think this is really
On 17 March 2011 16:18, Mike Axiak wrote:
> Just to be clear, for this to be valid syntax doesn't this idea have to be
> written as::
> class Foo(Model):
> x = models.FloatField()
> y = models.FloatField()
> coords = models.CompositeField(('x', 'y'),
Just to be clear, for this to be valid syntax doesn't this idea have to be
written as::
class Foo(Model):
x = models.FloatField()
y = models.FloatField()
coords = models.CompositeField(('x', 'y'), db_index=True)
a = models.ForeignKey(A)
b = models.ForeignKey(B)
I don't really know how to approach this issue the best way, so I'm
just going to be direct, I'd love to see Django provide support for
django.core.urlresolvers.reverse (at least) on the client (in
JavaScript).
I'm pretty sure all who have needed to make AJAX queries have dealt
with the issue of
On Wed, Mar 16, 2011 at 4:24 AM, Johannes Dollinger
wrote:
> I would be nice if support for composite primary keys would be implemented as
> a special case of general composite fields. There would be no need for new
> Meta options:
>
> class Foo(Model):
> x =
On Thu, Mar 17, 2011 at 5:08 AM, Tai Lee wrote:
> If we're talking about the lowest common denominator and keeping
> things simple, this is what I think we'd have:
>
> myapp1/
> myapp2/
> myproject/
> -django.wsgi.sample
> -manage.py
> -management/
> --commands/
>
On 03/15/2011 01:49 PM, Michael A. Ryan wrote:
In a typical client app, your User object is most
likely one robust object which you have to express in Django as both
User and UserProfile.
It's kind of hard to talk about "typical" Django app because there are
so many different of them :-).
Hi,
This is my proposal for the customizable serialization idea:
There are two formats - A formatted Google Docs version that's easy on
the eyes (
https://docs.google.com/a/vivekn.co.cc/document/pub?id=1GMWW42sY8cLZ2XRtVEDA9BQzmsqnCNULzskDMwqSUXI
) and a plain text version that follows.
On Mar 17, 3:11 am, Alexander Schepanovski wrote:
> Can you find that patch and post somewhere?
> If not still thanks for this idea.
Unfortunately, no. Gone with my old laptop.
- Anssi
--
You received this message because you are subscribed to the Google Groups
"Django
15 matches
Mail list logo