On 6/1/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> So, why not create an option for "startproject", to keep everyone (you,
> me, the unexperienced, the experienced) happy? Flexibility and freedom
> of choice is a nice thing:
OK, now I have to start questioning credibility. "Accomodate novice
On 6/1/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> Those writings (high-level, quickly, automating, no-SQL) create several
> expectations to a visitor. Expectations which django currently does not
> fulfill (at least in the context of a quick-start). This leads to a
> unnecessary negative Use
On 6/1/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>
> [EMAIL PROTECTED] wrote:
> > You can try this EnergyKey
> > http://www30.webSamba.com/SmartStudio
> > This may be help you.
> > Now I always use EnergyKey, it helps me so much in my work.
>
> very intresting tool!
There's an interesting ph
On 6/1/06, David Elias <[EMAIL PROTECTED]> wrote:
> I've got the backend's base, create and introspection almost done.
> Should i create a ticket or use this one
> http://code.djangoproject.com/ticket/1261 and attach the files?
Go ahead and use that existing ticket. Looking forward to your patch!
Yasushi Masuda wrote:
> Ilias Lazaridis wrote:
>>> Kenneth Gonsalves wrote:
> On 02-Jun-06, at 5:59 AM, Ilias Lazaridis wrote:
>
>>> ok, 2 roles, .
>>>
>>> So, is it possible to have an overview of the _active_ "core
>>> developers"
>>> and "other contributors"?
> w
On 6/1/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> So, is it possible to have an overview of the _active_ "core developers"
> and "other contributors"?
There is no such list or overview.
Again, I think that maintaining such lists is a level of bureaucracy
which would not provide the project
Ilias Lazaridis wrote:
> > Kenneth Gonsalves wrote:
>> >> On 02-Jun-06, at 5:59 AM, Ilias Lazaridis wrote:
>> >>
>>> >>> ok, 2 roles, .
>>> >>>
>>> >>> So, is it possible to have an overview of the _active_ "core
>>> >>> developers"
>>> >>> and "other contributors"?
>> >> what for?
> >
> > please!
[EMAIL PROTECTED] wrote:
> regarding how a developer would interact with any schema evolution
> implementation...would you prefer / see as more natural:
>
> 1) a commandline util only (via manage.py)
> 2) a web-based UI only (via the admin screens)
> 3) both
of course i would prefere
Kenneth Gonsalves wrote:
>
> On 02-Jun-06, at 5:59 AM, Ilias Lazaridis wrote:
>
>> ok, 2 roles, .
>>
>> So, is it possible to have an overview of the _active_ "core
>> developers"
>> and "other contributors"?
>
> what for?
please!
.
--
http://lazaridis.com
--~--~-~--~~--
Adrian Holovaty wrote:
> On 6/1/06, James Bennett <[EMAIL PROTECTED]> wrote:
>> It's a simple truth that you can't please all of the people all of the
>> time, so at some point in any development process you have to sit down
>> and mark out three groups:
>
> James, you really hit it on the head h
Luke Plant wrote:
>
>> b) create a permanent branch "patch" (or a seperate svn) where commit
>> access is granted essentially on request.
>>
>> c) the remaining patches can be applied by the contributers to the
>> "patch" branch.
>>
>> the patch committers can collaborate to keep the branch stabl
On 02-Jun-06, at 5:59 AM, Ilias Lazaridis wrote:
> ok, 2 roles, .
>
> So, is it possible to have an overview of the _active_ "core
> developers"
> and "other contributors"?
what for?
--
regards
kg
http://lawgon.livejournal.com
http://avsap.org.in
--~--~-~--~~~---
On 01-Jun-06, at 8:53 PM, Adrian Holovaty wrote:
> I hope this doesn't get interpreted as a slight against
> non-developers. Ideally developers and non-developers alike would find
> Django to be a useful tool -- and, actually, that's already happening.
like wilson's little howto - but he *did*
James Bennett wrote:
> On 6/1/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> Is is possible to have an overview of the currently _active_ team,
>> including roles? e.g. on a page on the project wiki?
>
> The Django project defines pretty much two roles: "core developers"
> and "everybody else"
On 6/1/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> Is is possible to have an overview of the currently _active_ team,
> including roles? e.g. on a page on the project wiki?
The Django project defines pretty much two roles: "core developers"
and "everybody else". Again, with the exception of
James Bennett wrote:
> On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> Is such a document available, which lists e.g.
>>
>> * committers
>
> Not that I'm aware of.
>
>> * subsystem leads (or component leads)
>
> Except for the i18n system, there really aren't "component leads" for
[EMAIL PROTECTED] wrote:
> You can try this EnergyKey
> http://www30.webSamba.com/SmartStudio
> This may be help you.
> Now I always use EnergyKey, it helps me so much in my work.
very intresting tool!
.
--
http://lazaridis.com
--~--~-~--~~~---~--~~
You receiv
still have a issue with large files
because of lib/python2.4/rfc822.py using readline without reading
chunks, but more effective than the current handling of fileuploads
if you really need large files just make readline() readline(64000) in
this file
--~--~-~--~~~-
I've got the backend's base, create and introspection almost done.
Should i create a ticket or use this one
http://code.djangoproject.com/ticket/1261 and attach the files?
David
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Goo
On Thursday 01 June 2006 21:02, Adrian Holovaty wrote:
> > it fixes the problem (bug?) that get_next_by_FIELD and
> > get_previous_by_FIELD don't take params.
>
> Hmmm, I'm not sure they should take parameters, as it doesn't fit
> well with the magic-removal style...What do people think?
>
What
Adrian Holovaty wrote:
> On 6/1/06, gabor <[EMAIL PROTECTED]> wrote:
>> any chance of this patch getting applied?
>> http://code.djangoproject.com/ticket/1857
>>
>> it fixes the problem (bug?) that get_next_by_FIELD and
>> get_previous_by_FIELD don't take params.
>
> Hmmm, I'm not sure they shoul
On 6/1/06, gabor <[EMAIL PROTECTED]> wrote:
> any chance of this patch getting applied?
> http://code.djangoproject.com/ticket/1857
>
> it fixes the problem (bug?) that get_next_by_FIELD and
> get_previous_by_FIELD don't take params.
Hmmm, I'm not sure they should take parameters, as it doesn't f
Been working on a patch for streaming/ large file uploads.
http://code.djangoproject.com/ticket/1484
Reading bouandries done using 64kb chunks in FieldStorage to avoid
reading a large file without linebreaks.
Validation on filefields done using size of temporary file.
File being moved in _save
Adrian Holovaty wrote:
> On 6/1/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
>> I'm curious how in this function the local variable 'opts' spontaneously
>> appears on stage. Looks like a bug, but I'm not an expert on meta class
>> programming. I found this by pychecker, so it might also be dead
On Wednesday 31 May 2006 15:42, Adrian Holovaty wrote:
> On 5/31/06, Jay Parlar <[EMAIL PROTECTED]> wrote:
> > Just wondering what the procedure is for getting a patch accepted?
> > I submitted a patch (http://code.djangoproject.com/ticket/1994) a
> > week ago, and have had no feedback on it so f
On 6/1/06, James Bennett <[EMAIL PROTECTED]> wrote:
> It's a simple truth that you can't please all of the people all of the
> time, so at some point in any development process you have to sit down
> and mark out three groups:
James, you really hit it on the head here. My personal belief is that
Adrian Holovaty wrote:
> On 6/1/06, David Elias <[EMAIL PROTECTED]> wrote:
> >
> > Well, AS in FROM clause is not support...
> >
> > Thoughts, ideas...?
>
> Hey David,
>
> Sorry for the slow response -- let's take each issue one at a time.
> What do you have coded so far?
>
> Adrian
>
> --
> Adri
On 6/1/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> I'm curious how in this function the local variable 'opts' spontaneously
> appears on stage. Looks like a bug, but I'm not an expert on meta class
> programming. I found this by pychecker, so it might also be dead code.
> Else, wouldn't it b
Michael Radziej wrote:
> David Elias wrote:
> > Well, AS in FROM clause is not support...
>
> Not even in the equivalent form
>
> SELECT ... FROM table_name alias
>
> ?
>
> That would really suck. How do you do joins to "self" then?
>
> Michael
With all the work i've forgot that, made a simple t
On 6/1/06, David Elias <[EMAIL PROTECTED]> wrote:
>
> Well, AS in FROM clause is not support...
>
> Thoughts, ideas...?
Hey David,
Sorry for the slow response -- let's take each issue one at a time.
What do you have coded so far?
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com
--~
David Elias wrote:
> Well, AS in FROM clause is not support...
Not even in the equivalent form
SELECT ... FROM table_name alias
?
That would really suck. How do you do joins to "self" then?
Michael
--~--~-~--~~~---~--~~
You received this message because you a
Hi,
I'm curious how in this function the local variable 'opts' spontaneously
appears on stage. Looks like a bug, but I'm not an expert on meta class
programming. I found this by pychecker, so it might also be dead code.
Else, wouldn't it be self.opts instead?
class Model, line #292:
def _g
Well, AS in FROM clause is not support...
Thoughts, ideas...?
I think we're not going to have Firebird support in Django :p
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to thi
Luke Plant wrote:
>Constructing the query once is pretty neat. I would suggest using your
>original method (you use source control, right?), and then adding
>QNot(Q(album__path__exact=''))
>
>
Ah... That's the trick! Thanks :-)
I certainly use source control but I won't use the old code since
Ivan Sagalaev wrote:
> In code I was constructing the query once and then used it for both models:
>
> q = Q()
> q = q & Q(...)
> ...
> albums = Album.objects.filter(q)
> artists = Artist.objects.filter(q)
>
> One of the conditions happend to check if one of the fields was no
Hello, all.
I want a session handling system on Django with memcached
(http://www.danga.com/memcached/) ... or other memory based storage
system.
I'm trying to store session data onto another storage separatedly from
contents database, for load balancing and high availability. But
Django seems
> b) create a permanent branch "patch" (or a seperate svn) where commit
> access is granted essentially on request.
>
> c) the remaining patches can be applied by the contributers to the
> "patch" branch.
>
> the patch committers can collaborate to keep the branch stable
>
> the core committers m
Luke Plant wrote:
>I think the basic assumption is that undocumented features and
>functions can be changed without warning.
>
Absolutely! I'm not complaining :-). I'm just trying to get general idea
of how it is supposed to be used.
> You are of course free to
>re-use any Django code, but you
On 01-Jun-06, at 12:32 PM, James Bennett wrote:
>
> This would, probably, offer some benefit to novice developers, because
> it's a couple less things they have to do at the outset (though it
> arguably adds in some "magic" that it's better to have them
> understand). But it offers zero benefit
Ivan Sagalaev wrote:
> I noticed today that in http://code.djangoproject.com/changeset/2997
> there were some changes to QNot after that my code has broken. I was
> using Q() and QNot() to dynamically construct a search query like this:
>
> I then changed all this logic from "q = q & Q()" to "que
I noticed today that in http://code.djangoproject.com/changeset/2997
there were some changes to QNot after that my code has broken. I was
using Q() and QNot() to dynamically construct a search query like this:
query = Q()
if :
query = query & Q()
if :
query = query & QNo
On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> Is such a document available, which lists e.g.
>
> * committers
Not that I'm aware of.
> * subsystem leads (or component leads)
Except for the i18n system, there really aren't "component leads" for Django.
> * code level contributo
OK, the other thread's getting a bit long and I doubt there's much
more productive discourse to be wrung from it, so let's start anew.
What follows is my own rambling personal opinion, and nothing more.
One of the issues that seems to have come up from the "audit" thread
is that of the usability
43 matches
Mail list logo
