Re: the so-called [AUDIT]
On 2-jun-2006, at 22:14, Carlo C8E Miron wrote: > > On 6/2/06, Julian 'Julik' Tarkhanov <[EMAIL PROTECTED]> > wrote: >> >> I would advise all respected Django contributors to follow the path >> mentioned here: >> >> http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/138966 > > and maybe also > > http://www.encyclopediadramatica.com/index.php/Ilias Quite a history: http://dev.eclipse.org/newslists/news.eclipse.foundation/msg00291.html http://www.intellij.net/forums/thread.jspa? forumID=27=3439721=122131= and a response from Hani is the best to date, hats off. -- Julian 'Julik' Tarkhanov please send all personal mail to me at julik.nl --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: the so-called [AUDIT]
and now: http://en.wikipedia.org/wiki/Ilias_Lazaridis Carlo C8E Miron wrote: > On 6/2/06, Julian 'Julik' Tarkhanov <[EMAIL PROTECTED]> wrote: >> I would advise all respected Django contributors to follow the path >> mentioned here: >> >> http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/138966 > > and maybe also > > http://www.encyclopediadramatica.com/index.php/Ilias > > ;) > > --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: the so-called [AUDIT]
On 2-jun-2006, at 22:14, Carlo C8E Miron wrote: > > On 6/2/06, Julian 'Julik' Tarkhanov <[EMAIL PROTECTED]> > wrote: >> >> I would advise all respected Django contributors to follow the path >> mentioned here: >> >> http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/138966 > > and maybe also > > http://www.encyclopediadramatica.com/index.php/Ilias Half of Google to be precise. Subject closed. -- Julian 'Julik' Tarkhanov please send all personal mail to me at julik.nl --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: the so-called [AUDIT]
C8E wrote: > and maybe also > > http://www.encyclopediadramatica.com/index.php/Ilias > > ;) Didn't want to steal your thunder, pal, but since you weren't speaking up, I did. Thanks for that URL! :-) -- Nicola Larosa - http://www.tekNico.net/ --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: the so-called [AUDIT]
On 6/2/06, Carlo C8E Miron <[EMAIL PROTECTED]> wrote: > > On 6/2/06, Julian 'Julik' Tarkhanov <[EMAIL PROTECTED]> wrote: > > > > I would advise all respected Django contributors to follow the path > > mentioned here: > > > > http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/138966 > > and maybe also > > http://www.encyclopediadramatica.com/index.php/Ilias > > ;) Something seemed "off" the whole time with that guy, but he seemed to be doing too much research into Django to be a real troll. He must have a LOT of free time. Jay P. --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: the so-called [AUDIT]
On 6/2/06, Julian 'Julik' Tarkhanov <[EMAIL PROTECTED]> wrote: > > I would advise all respected Django contributors to follow the path > mentioned here: > > http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/138966 and maybe also http://www.encyclopediadramatica.com/index.php/Ilias ;) -- Carlo C8E Miron, ICQ #26429731 -- Disclaimer: If I receive a message from you, you are agreeing that: 1. I am by definition, "the intended recipient". 2. All information in the email is mine to do with as I see fit and make such financial profit, political mileage, or good joke as it lends itself to. In particular, I may quote it on USENET or the WWW. 3. I may take the contents as representing the views of your company. 4. This overrides any disclaimer or statement of confidentiality that may be included on your message. --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: the so-called [AUDIT]
I would advise all respected Django contributors to follow the path mentioned here: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/138966 On 25-mei-2006, at 18:27, lazaridis_com wrote: > > For a long term project, I am selecting a python based persistency > system: -- Julian 'Julik' Tarkhanov please send all personal mail to me at julik.nl --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Patch review procedure?
On Friday 02 June 2006 17:15, Bill de hÓra wrote: > Luke, > > I summarized this as: > > Adrian/Jacob pick some people they trust to eval/weed patches. Those > people recommend patches for consideration. That way some of the work > is farmed out, but core technical decisions stay centralised. > > is that it? That's almost it, except you put about a million times better :-) I would just add that I think there should be a process/order for looking at patches to ensure they do get looked at, and a specific aim to to have *some* comment on a patch within a certain period of time. Luke -- "Underachievement: The tallest blade of grass is the first to be cut by the lawnmower." (despair.com) Luke Plant || L.Plant.98 (at) cantab.net || http://lukeplant.me.uk/ --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Patch review procedure?
Luke, I summarized this as: Adrian/Jacob pick some people they trust to eval/weed patches. Those people recommend patches for consideration. That way some of the work is farmed out, but core technical decisions stay centralised. is that it? cheers Bill Luke Plant wrote: Ideas for >> improving this system would be much appreciated! > > As a moderately experienced django hacker, I'm happy to help out with > this stuff (I have already been doing a bit, if in a rather haphazard > way), and I've had a think about it and detailed some ideas below. > > Problem > === > The basic problem, as I see it, is: > > People have no idea for a long time whether their patch is likely to be > accepted at all, and if it is, when. > > This is important because people need to know whether to use another > work around or continue with their patch. Also the wait-and-see game > can drag on people's patience -- there is a currently a ticket with a > patch that was opened 11 months ago, and it's still waiting for some > kind of review. (Of course don't think for a moment that this is a > criticism of Adrian and Jacob -- it is just what has happened with > limited resources and a lot of demand, but it nonetheless can be > frustrating for contributors, as already noted). > > Principles > == > The solutions to this problem have to be: > - low maintenance > - opt in, to allow experienced django developers to > contribute as much or as little as they want, as their > experience and time allows. > - rigorous -- patches shouldn't wait months with no feedback > while others get applied immediately, there should be some > system to ensure everything gets reviewed. > - actually remove work-load from Adrian and Jacob, including the > time spent looking through bug lists etc. > - integrate with existing stuff -- no extra mailing lists > or websites please. > > Suggestions > === > > I think it would be good to aim to add an initial comment to each > patch within N days (where Adrian and Jacob should decide the value of > N!). I would suggest that some of the experienced Django hackers should > be allowed to do this initial review (especially for obvious > WONTFIXes). I'll call these developers 'exp devs', Adrian and Jacob > and probably other commiters 'core devs', and both groups together 'all > devs'. > > A number of stock answers could be helpful. They would be > different for new feature patches and bug patches, and might be > something like below: > > For bugs: > - [core devs] patch looks OK, I aim to apply within N days/week > - [all devs] please add a test that supports the bug [obviously not > always feasible] > - [all devs] needs more review, I aim to do this in N days/weeks > - [exp devs] patch tests OK, I suggest to the core devs that this patch > (or my tidied up version) is applied immediately. > > For new features: > - [core devs] this patch is almost certain to be accepted, I aim to > apply it within N days/weeks. > - [all devs] this patch is likely to be accepted at some point, I aim > to review again in N days/weeks. > - [all devs] this is interesting, but will have to wait for Django 1.1 > - [all devs] this patch is unlikely to be accepted, as I don't see > that the need is common enough, or it can be implemented in other ways > (featuritis), unless you can convince me otherwise. > - [all devs] clean up your patch, add some documentation etc and I'll > have another look. > - [exp devs] - patch seems Good and Right, I suggest to the core devs > that this patch (or my tidied up version) is applied immediately. > > > For each case where there is an aim to review or apply, you could add a > todo-[yourname] to the Trac keywords, so you could search for these (I > guess this is what the 'assigned' field is for, but it just defaults > to a component owner, and most of them are 'Adrian' at the moment, far > more than I suppose he can deal with, so 'assigned = Adrian' is not > very useful for him. I think assigned here really means 'I will look > at this and decide what to do if no-one else does'. We need a way to > distinguish between the 'I will definitely do this' and 'this has just > been assigned to me by Trac' situations). > > There is the issue of which tickets to handle -- I am a big culprit > here, as my procedure is totally random -- if I happen to notice > something on django-updates I'll have a look. Maybe we need to be > pedantic about using http://code.djangoproject.com/report/12 and > starting from the bottom. > > The problem with that report is that it won't distinguish between > tickets where you are waiting for the ticket owner to get back to you > (fix their patch or whatever), tickets that are awaiting some > attention, and tickets that are on your todo list. I think we need > some more specialised reports: > > 1) active tickets with patches that are awaiting
Re: We're being had
> On 6/2/06, Nicola Larosa (tekNico) <[EMAIL PROTECTED]> wrote: >> Ilias Lazaridis is a known Internet troll. >> >> http://www.encyclopediadramatica.com/index.php/Ilias >> >> Let's stop feeding him/her/it, it's just a waste of time. > > Nice catch! > > Adrian yes, danke. :) -- derek --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: proposal for a new ValidationError
James Bennett wrote: > On 6/2/06, Gary Wilson <[EMAIL PROTECTED]> wrote: >> One issue would be what to name this >> more-critical-than-CriticalValidationError validation error. > > FatalValidationError. HeartAttack ;-) Michael --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: We're being had
On 6/2/06, Nicola Larosa (tekNico) <[EMAIL PROTECTED]> wrote: > Ilias Lazaridis is a known Internet troll. > > http://www.encyclopediadramatica.com/index.php/Ilias > > Let's stop feeding him/her/it, it's just a waste of time. Nice catch! Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: proposal for a new ValidationError
On 6/2/06, Gary Wilson <[EMAIL PROTECTED]> wrote: > One issue would be what to name this > more-critical-than-CriticalValidationError validation error. FatalValidationError. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
proposal for a new ValidationError
What do you think about adding a ValidationError similar to CriticalValidationError but one that would stop further evaluation of _all_ validators in the manipulator instead of just the remaining validators for the current form field being processed? For example, I have a simple login form with username and password that authenticates to an LDAP server. If the user does not have cookies enabled, they fail the hasCookiesEnabled validator on username. However, even if I make hasCookiesEnabled raise a CriticalValidationError, the password validators will still get run and my LDAP server will still get hit. A more desirable outcome would be for me to be able to short circuit processing of all other validators if hasCookiesEnabled fails. A very similar situation can been seen in django.contrib.auth.forms.AuthenticationForm: class AuthenticationForm(forms.Manipulator): def __init__(self, request=None): self.request = request self.fields = [ forms.TextField(field_name="username", length=15, maxlength=30, is_required=True, validator_list=[self.isValidUser, self.hasCookiesEnabled]), forms.PasswordField(field_name="password", length=15, maxlength=30, is_required=True, validator_list=[self.isValidPasswordForUser]), ] Even if username's hasCookiesEnabled validator raised CriticalValidationError, the password's isValidPasswordForUser validator would still get run and hit the database. One issue would be what to name this more-critical-than-CriticalValidationError validation error. --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: File uploads
Fixed, is now ticket http://code.djangoproject.com/ticket/2070 --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
We're being had
Ilias Lazaridis is a known Internet troll. http://www.encyclopediadramatica.com/index.php/Ilias Let's stop feeding him/her/it, it's just a waste of time. -- Nicola Larosa - http://www.tekNico.net/ Users know the business better than you do, whoever you are. If you are willing to learn, you can change the world. -- Dratz, February 2006 --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: File uploads
On 6/2/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Streaming is storing the output directly without loading the entire > file into memory. Just small parts of it are in memory at any given > time before it is appended to a file on disk. Ah right. Should've thought of that. I guess this will also bring us closer to do what Google does with the Gmail file attachments. For those that do not know, it starts uploading the moment you completed the file selection. Thus allowing you to continue to edit while in the background the file gets transferred. Thanks for the clarification Oyvind, -- Jeroen Ruigrok van der Werven --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: File uploads
Jeroen Ruigrok van der Werven wrote: > Hei Oyvind, > > On 6/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Been working on a patch for streaming/ large file uploads. > > Can you briefly explain how I should interpret the concept streaming > file uploads? > > -- > Jeroen Ruigrok van der Werven Hi, Jeroen Streaming is storing the output directly without loading the entire file into memory. Just small parts of it are in memory at any given time before it is appended to a file on disk. Øyvind Saltvik --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: File uploads
Hei Oyvind, On 6/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Been working on a patch for streaming/ large file uploads. Can you briefly explain how I should interpret the concept streaming file uploads? -- Jeroen Ruigrok van der Werven --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
