Not sure exactly how to phrase this, but James told me to bring these tickets
up
here to get some feedback on them - such as what exactly needs done to bring
them to 'ready for checkin' as myself and others would like to get them in :)
I did the basics of making sure the patches were updated,
Jean-Christophe Kermagoret said the following:
> I need this meta model to generate automatically django code from models.
>
> If there is no meta model, is there presently some code which would
> permit to have code automatically generated from xml (or properly
> properties) configuration file
U Want To Search From Your Desktop?
You can now search anything from your Desktop with just One Click.
Download Searchbar Search from Your Desktop now at http://eixuth.notlong.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Goo
I need this meta model to generate automatically django code from models.
If there is no meta model, is there presently some code which would
permit to have code automatically generated from xml (or properly
properties) configuration files ?
Thanks
--
Jean-Christophe Kermagoret
Directeur ass
On Wed, Jun 11, 2008 at 11:17 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I have to ask why must Django prevent work in this regard?
To be perfectly fair, it's not really "prevented". Django supports the
use of database backends not defined in Django itself, so third-party
development of b
Sexy nayan photos ,videos, stills ,wallpapers
http://www.funny-games2all.page.tl/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develo
> This is a call for comments on the proposed Django 1.0 roadmap and schedule.
[snip]
> Must-have features
I love that this list is small and concentrated. This is exactly what
is needed in order to get a release out quickly and focus development
effort.
+1 from me.
> "Maybe" features
These al
On Wed, Jun 11, 2008 at 11:29 PM, Russell Keith-Magee <
[EMAIL PROTECTED]> wrote:
>
> On Thu, Jun 12, 2008 at 10:54 AM, Jacob Kaplan-Moss
> <[EMAIL PROTECTED]> wrote:
> >
> > On Wed, Jun 11, 2008 at 9:46 PM, Karen Tracey <[EMAIL PROTECTED]>
> wrote:
> >> One thing I don't see mentioned anywhere is
On Thu, Jun 12, 2008 at 10:54 AM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
>
> On Wed, Jun 11, 2008 at 9:46 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
>> One thing I don't see mentioned anywhere is defect #6755 "Model Inheritance
>> doesn't work in the admin" (whereas GenericForeignKey admin
That list seems perfect to me. I'll be around in San Francisco to
help on the sprint, so if #6095 isn't merged by then I can focus on
whatever needs to be done to get it to where it needs to be.
-Eric Florenzano
--~--~-~--~~~---~--~~
You received this message beca
برنامج VMware Workstation 6.0
http://www.antya7la.com/vb/t26858.html#post286993
برنامج يعالج فيروسات auto run و folder option
http://www.antya7la.com/vb/t26859.html#post286996
ضع صورتك داخل هذة الساعة
http://www.antya7la.com/vb/t26860.html#post286997
زيد سرعة ال Ftp ؟ 64 % + الطريقة مضمونة و
On Wed, Jun 11, 2008 at 9:59 PM, George Vilches <[EMAIL PROTECTED]> wrote:
>> 8. Many-to-many intermediates (#6905).
>>
> Shouldn't that be #6095? http://code.djangoproject.com/ticket/6095
Yup; thanks.
Jacob
--~--~-~--~~~---~--~~
You received this message becaus
On Wed, Jun 11, 2008 at 9:56 PM, Julien <[EMAIL PROTECTED]> wrote:
> In the must-have features, or at least in the maybes, I'd put the bugs
> introduced by, or not properly fixed by, the merge of the queryset-
> refactor branch. A list of related open tickets has been given in [1].
A better list
Just one fix to this list:
On Jun 11, 2008, at 10:03 PM, Jacob Kaplan-Moss wrote:
> 8. Many-to-many intermediates (#6905).
>
Shouldn't that be #6095? http://code.djangoproject.com/ticket/6095
George
--~--~-~--~~~---~--~~
You received this message because you a
Seems like a very good roadmap, and it must clear a lot of concern and
uncertainty some people may have.
In the must-have features, or at least in the maybes, I'd put the bugs
introduced by, or not properly fixed by, the merge of the queryset-
refactor branch. A list of related open tickets has b
On Wed, Jun 11, 2008 at 9:27 PM, Jeff Anderson <[EMAIL PROTECTED]> wrote:
> I'm curious: is there a reason that the milestone feature was disabled on
> the trac page?
> Would it be good/beneficial to put these "must-haves" in a 1.0 milestone,
> and (some of) the "No" features in a 1.1 milestone?
On Wed, Jun 11, 2008 at 9:46 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> One thing I don't see mentioned anywhere is defect #6755 "Model Inheritance
> doesn't work in the admin" (whereas GenericForeignKey admin support is
> specifically called out). I don't know if #6755 is classified as must h
On Wed, Jun 11, 2008 at 10:03 PM, Jacob Kaplan-Moss <
[EMAIL PROTECTED]> wrote:
>
> This is a call for comments on the proposed Django 1.0 roadmap and
> schedule.
>
> ...
> Must-have features
> --
>
...
> 2. Replacement of ``oldforms`` throughout Django.
>
> Nothing in Django 1.
Very reasonable set for 1.0 release. The list of must-haves totally
matches my expectations. +1.
Thanks,
Eugene
Jacob Kaplan-Moss wrote:
> This is a call for comments on the proposed Django 1.0 roadmap and schedule.
>
> Note that though this is worded in the future perfect tense, it is only
This hits the nail right on the head. +1 from me.
On Jun 11, 2008, at 8:03 PM, Jacob Kaplan-Moss wrote:
> 2. Replacement of ``oldforms`` throughout Django.
>
> Nothing in Django 1.0 should rely on the deprecated ``oldforms``
> package.
> We'll need to replace ``oldforms`` usage in generic
On Wed, Jun 11, 2008 at 9:23 PM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
> This does mean newforms-comments will be a late feature to the trunk (although
> only 3 weeks after the feature cutoff for other features), but if we encourage
> testing in its own branch, we should be able to mitigate
On Wed, Jun 11, 2008 at 9:26 PM, Marty Alchin <[EMAIL PROTECTED]> wrote:
> I think I know what you mean here, but "dropped" sounds an awful lot
> like an all or nothing deal: either it makes it into 1.0 or it never
> makes it at all. It's probably best to clarify that "dropped" just
> means "dropp
Jacob Kaplan-Moss wrote:
This is a call for comments on the proposed Django 1.0 roadmap and schedule.
Note that though this is worded in the future perfect tense, it is only a draft;
I'm looking for feedback and comments from the community before the core
developers and I post a the final versio
I like it, but mainly that's because I'm not the "maybe" list, and I'm
sure I can get it done in time. I do have one suggestion, though.
On Wed, Jun 11, 2008 at 10:03 PM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
> * "Maybe" features: things that *should* be in 1.0 and should be worked on
> i
On Wed, Jun 11, 2008 at 9:13 PM, Russell Keith-Magee
<[EMAIL PROTECTED]> wrote:
>
> On Thu, Jun 12, 2008 at 10:03 AM, Jacob Kaplan-Moss
> <[EMAIL PROTECTED]> wrote:
>>
>> ``django.contrib.comments`` still uses ``oldforms`` as well, but there's
>> special situation here; see below.
>
> Jacob -
برنامج VMware Workstation 6.0
http://www.antya7la.com/vb/t26858.html#post286993
برنامج يعالج فيروسات auto run و folder option
http://www.antya7la.com/vb/t26859.html#post286996
ضع صورتك داخل هذة الساعة
http://www.antya7la.com/vb/t26860.html#post286997
زيد سرعة ال Ftp ؟ 64 % + الطريقة مضمونة و
On Thu, Jun 12, 2008 at 10:03 AM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
>
> ``django.contrib.comments`` still uses ``oldforms`` as well, but there's
> special situation here; see below.
Jacob - unless I'm going blind, you've missed out the 'below' section
that this refers to.
Russ %-)
Hi all --
It's apparent from the recent blog and list activity that some members of the
Django community feel that we've screwed up in waiting so long to make another
release; some have started to despair that we'll ever ship 1.0. This uncertainty
has been confounded by our failure to be more tra
This is a call for comments on the proposed Django 1.0 roadmap and schedule.
Note that though this is worded in the future perfect tense, it is only a draft;
I'm looking for feedback and comments from the community before the core
developers and I post a the final version of this document (which
On Wed, Jun 11, 2008 at 6:44 PM, Jeff Anderson <[EMAIL PROTECTED]> wrote:
> I went to subscribe to django-updates so I can do what I can with furthering
> django, but it seems that whatever script posts to the list hasn't been
> working since March. Is this accurate? Has the django-updates informa
I went to subscribe to django-updates so I can do what I can with
furthering django, but it seems that whatever script posts to the list
hasn't been working since March. Is this accurate? Has the
django-updates information moved to another medium?
Thanks!
Jeff Anderson
signature.asc
Descr
Has any headway been made on this? Should I reopen the ticket that was
referenced above?
thanks,
Matt
On Jun 5, 7:54 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> Ok, I see it when I start with just python, not if I use manage.py
> though.
>
> On Jun 5, 7:46 pm, Collin Grady <[EMAIL PROTE
On Tue, Jun 10, 2008 at 11:33 PM, Gary Wilson Jr. <[EMAIL PROTECTED]> wrote:
>
> Nicolas E. Lara G. wrote:
>> I was wondering if there was some sort of design decision on this or
>> was just not implemented (yet).
>
> I would say it just hasn't been implemented yet.
I note that ValuesQuerySet.ite
On Wed, Jun 11, 2008 at 5:17 AM, Patryk Zawadzki <[EMAIL PROTECTED]> wrote:
...
> It starts to get ugly if you consider languages such as pl_PL. For
> example "computer" in Polish:
>
> * 1 komputer
> * 2 komputery
...
Patryk,
While I am dimly aware that pluralization is often more involved
than
Nathaniel Whiteinge said the following:
> Either way, this is a bike-shed issue.
In fact, he can simply do this:
from django.views.generic.simple import direct_to_template as render_response
and get the name he wants without patching anything :)
--
Collin Grady
--~--~-~--~~--
For the record, this issue really bothered me too until I found
direct_to_template. Now it is a non-issue.
On Jun 11, 1:22 pm, Gabriel Farrell <[EMAIL PROTECTED]> wrote:
> It's fairly clear that we're setting
> up a dictionary of variables for the template, pulling data from the
> Profile model.
On Tue, Jun 10, 2008 at 7:13 PM, Russell Keith-Magee
<[EMAIL PROTECTED]> wrote:
>
> However, I'm happy to defer to
> someone with a higher degree in grammarnazism.
With that in mind, I whipped out my copies of the Chicago Manual of
Style and Garner's Modern American Usage last night.
And came up
On Jun 10, 5:44 pm, "Rajeev J Sebastian" <[EMAIL PROTECTED]>
wrote:
> On Tue, Jun 10, 2008 at 11:20 PM, Gabriel Sean Farrell <[EMAIL PROTECTED]>
> wrote:
>
> > direct_to_template, I'd rather avoid abusing a function by ignoring
> > its name and exercising largely undocumented functionality. Afte
Get over it. No one writes a blog post as the first crack at a
problem. He's brought the stuff up before and did not meet with
satisfaction. For the record, I can't stand the passive-aggresiveness
of attacking someones honest attempt at criticism just because it
didn't enter the channel you des
Marc Fargas wrote:
> m = TestModel()
> m.get_previous_by_date()
>
> Will fail with an exception which says "Cannot use None as a query",
> maybe that error could be a bit more self-explicative, like "Cannot
> query next/previous items without being saved".
Agreed, please create a ticket for this
On Wed, Jun 11, 2008 at 1:11 PM, Jeff Anderson <[EMAIL PROTECTED]>
wrote:
> Joseph Kocherhans wrote:
>
>>
>> Commented. http://code.djangoproject.com/ticket/5731#comment:7
>>
>> You might want to hop on #django-dev on irc.freenode.net to ask Brian
>> (brosner) if he's looked at it recently since t
On Mon, Jun 9, 2008 at 3:57 PM, J. Cliff Dyer <[EMAIL PROTECTED]> wrote:
> As mentioned in my previous post, if it's indeed three months, I agree,
> but if it's only "hopefully" three months, then do we want to end up six
> or nine months out still waiting for 1.0 to land "in a couple months?"
We
On Jun 11, 2008, at 11:11 AM, Jeff Anderson wrote:
> Joseph Kocherhans wrote:
>>
>> Commented. http://code.djangoproject.com/ticket/5731#comment:7
>>
>> You might want to hop on #django-dev on irc.freenode.net to ask Brian
>> (brosner) if he's looked at it recently since the ticket is still
>> a
Joseph Kocherhans wrote:
Commented. http://code.djangoproject.com/ticket/5731#comment:7
You might want to hop on #django-dev on irc.freenode.net to ask Brian
(brosner) if he's looked at it recently since the ticket is still
assigned to him.
It looks like he assigned himself this morning-- I
On Wed, Jun 11, 2008 at 11:55 AM, Jeff Anderson
<[EMAIL PROTECTED]> wrote:
> Hello.
>
> I'm interested in helping out with getting newforms-admin rolling (with 1.0
> in mind)
>
> Last night I went through some of the tickets and I'm comfortable re-working
> the patch for #5731.
>
> I'm contacting
Hello.
I'm interested in helping out with getting newforms-admin rolling (with
1.0 in mind)
Last night I went through some of the tickets and I'm comfortable
re-working the patch for #5731.
I'm contacting the list because the comments say to contact Joseph about
the proposal to remove the
On 6/10/08, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> However, if we _ever_ want to get v1.0 out the door, we're going to
> have to draw the line somewhere. This wouldn't be a trivial change -
> at the very least, it will require a bit of discussion to work out
> exactly what we should
On Jun 11, 2008, at 7:06 AM, patS wrote:
> {{ m.z.pool }} prints: something in z
>
> but if i put {{ m.z.pool }} after {{ m.y.pool }} it will print
> something in y not something in z
This appears just like a problem that was solved in SVN trunk a couple
weeks ago with improper caching on One
Nicolas Lara wrote:
> The ticket is in the tracking sistem: #7256. I have claimed it, but am
> not planning to start working on it until I'm done with aggregation
> (or maybe in EuroPython's sprint), so if anybody bits me to it, it
> would be great.
>
>
In that case you would be better off leav
Hello,
First - sorry for my english ;)
Second, example:
class m(models.Model):
something = models.CharField(max_length=100)
class y(models.Model):
m = models.OneToOneField(m,primary_key=True,related_name='y')
pool = models.CharField(max_length=100)#example data: "something
in y"
c
On Wed, Jun 11, 2008 at 2:13 AM, Russell Keith-Magee
<[EMAIL PROTECTED]> wrote:
> You could be right. Examples are a bit hard to think of, but to my
> understanding:
>
> * It was 1.1 meters tall
> * It weighs 1.1 kilograms
It starts to get ugly if you consider languages such as pl_PL. For
example
Could someone of the core devs give his opinion on this?
--~--~-~--~~~---~--~~
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 unsubscrib
On Wed, Jun 11, 2008 at 12:18 AM, Peter Melvyn <[EMAIL PROTECTED]> wrote:
>
> On 6/9/08, Ian Kelly <[EMAIL PROTECTED]> wrote:
>
>> I don't know why this is so mysterious. A small amount of browsing
>> turns up that the code was added in revision [4916] and specifically
>> enabled for Oracle on
Thanks for the links, I was sure someone had done this before. Looks
like they're scanning the models.py source code and finding the
information there. I think it would be easier and cleaner to generate
it dynamically.
@oggie rob, @russ magee
Yep, it would only ever be needed once, and cluttering
54 matches
Mail list logo