Re: Allow disabling choices in a

@tony thanks this realy helped me! On Tuesday, 1 May 2018 at 01:33:19 UTC+2 tony...@gmail.com wrote: > This might be a late answer but this is a simplified version that can be > modified using the form instance. > > You can either pass a list of values to be disabled i.e > > def __init__(self,

Re: photobook designing

yes, you can. On Thu, Jan 24, 2019 at 2:50 PM Esra Başkurt wrote: > Hello > I want to do a website about photobook designer like : > https://www.adoramapix.com/books/ > > > How can I do it

Re: Messages without text in the messages framework

the django-users mailing list for that, or IRC #django on freenode, or a site like Stack Overflow. On Sat, 19 Jan 2019 at 16:00, Sebastian Lechner <mailto:m...@seble.info>> wrote: Dear Django developer community, often I would like to trigger a message to the user with the

Messages without text in the messages framework

discarded. Is there are another way to send a message without text (but a number of tags) with the messages framework? Best regards Sebastian -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from

Will asgi become a PEP like wsgi is ?

://channels.readthedocs.io/en/stable/asgi.html How do these two concepts compare in regards to their respect "importance" to the python community? Especially under the consideration that real-time web applications (i.e. HTML5 websockets) is getting more and more important. Regards, Sebastian -- Yo

Re: Migrations and Reusable Apps

Hey Aymeric, thanks a lot for your immediate feedback. I appreciate that a lot. I've added a few comments inline. On 30/06/14 23:55, Aymeric Augustin wrote: > 2014-06-30 14:32 GMT+02:00 Sebastian Vetter > <sebast...@roadside-developer.com > <mailto:sebast...@roadside-developer.co

Re: Migrations and Reusable Apps

Are there any implications this might have on the loading of the app registry? Thanks for any thoughts and advice on this. And thanks for the great new appregistry, it's a pleasure to work with. Cheers, Sebastian PS: @Florian, thanks for the PGP/Mime hint. I hope it looks better this time :) [1] https

Re: Migrations and Reusable Apps

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey Aymeric, > At this point, I think you're the only person who reached out for > help :-) well, not anymore ;) > So, if anyone else is maintaining a third-party app and could use > tips about how to deal with app-loading, let me know and I'll do

Django Project Proposal

My name is Kevin Sebastian and I have been working with django for quite some time and I would like to contribute to any of its projects.I will be grateful if someone can offer any suggestion for the same.I am also proficient in python and its various libraries and I have worked on python

Re: Not calling things twice in templates

s could have an expensive __init__()) whether > that thing should be re-evaluated more than once per request, or per context? As an alternative to the explicit way, how about making the context dictionary memoizable, i.e. let Django cache each value's object transparently the first time it is ret

Re: Non-default managers in related field lookups

__call__ notation. The patch in the ticket uses an explicit method named `manager`, however using __call__ seems more elegant (+ 1). Maybe the efforts from that patch can be revisited. Best wishes, Sebastian. [1] https://code.djangoproject.com/ticket/3871 [2] https://code.djangoproject.com/attachm

Re: Custom managers in reverse relations

, this could easily introduce name clashes between forward and reverse attributes. Any thoughts? Sebastian. On Sat, 14 Jan 2012 22:15:33 +0200 Kääriäinen Anssi <anssi.kaariai...@thl.fi> wrote: > Just a quick thought: you should check out the work done for allowing use of > man

Re: Custom managers in reverse relations

? Or, am I missing something and this is already possible in some other way? Since I'm looking forward to seeing this implementation in Django 1.4, I ask for your input on the matter. Thanks! Sebastian. [1] In fact, that's not entirely true: we get whatever is returned by the _default_ manager

Custom managers in reverse relations

f course feel free to raise any concerns you might have. Regards, Sebastian. PS: Merry X-Mas and whatnot! :D [1] https://code.djangoproject.com/ticket/3871 -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group

Hash collision in 'cache' templatetag

d increase both runtime and storage space requirements of the template fragment cache. Regards, Sebastian. [1] https://code.djangoproject.com/browser/django/trunk/django/templatetags/cache.py?rev=16539 [2] https://docs.djangoproject.com/en/dev/topics/cache/#template-fragment-caching

Re: Wrong JOIN with nested FKs

Hello, akaariai has proposed a patch that solves the bug described below. It is attached to ticket #16715. How do we proceed from here? Sebastian. On Thu, 29 Sep 2011 21:52:23 +0200 Sebastian Goll <sebastian.g...@gmx.de> wrote: > Hello, > > I'd like to draw your attention t

Re: How to do equivalent of LEFT JOIN ON in Django (returning all Left rows, when Right item may not exist)

e relations null-able is the more trivial part of the patch, and essentially a one-liner in django/db/models/sql/compiler.py. "new_nullable = f.null or None" in line 674 – as of r16928 – should be "new_nullable = True" since reverse relations should always be considered null-able. Se

Re: Wrong JOIN with nested FKs

Hello, I'm afraid I'll have to reply to my own message because nobody else did. ;) Please read on. Also, please note that the original report is now over five weeks old, with no real solution yet in sight. On Thu, 29 Sep 2011 21:52:23 +0200 Sebastian Goll <sebastian.g...@gmx.de> wrote:

Wrong JOIN with nested FKs

erator fails to correctly promote the join type for the nested relation. Sebastian. -- 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 t

Re: First time contribution, tests fails.

or this is something expected > (known bug?). How should I procede. Should I make my changes? or try to fix > tests? Are you sure that you are using the right version of Django to run the tests? Try setting PYTHONPATH to the path of your local copy of the SVN repository. Sebastia

Re: Small job for a Django Devel/User

On Sat, Jul 30, 2011 at 8:23 PM, Karen Tracey wrote: > Please do not crosspost to both django-users and django-developers: pick > the right list and post there. This post is off-topic for django-developers. > > Sorry, I thought a Django devel could be interested in a job

Problem with writing custom field to work with inherit models

Hi, could you explain to us why this isn't working? https://github.com/humanfromearth/django-stdimage/issues/11 Thanks s. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: #6375 -- Class Based Views: Opinions on commit plan

Maybe not important but makes bit harder to find in it trac :) Russ there is a typo in subject, ticket id is #6735, not 6375. On Fri, Oct 15, 2010 at 8:11 AM, Russell Keith-Magee wrote: > On Fri, Oct 15, 2010 at 1:59 PM, Yo-Yo Ma wrote: >> I

Re: 8040 SlugField format not enforced - fixed, closed an "ready for checkin" since two years

I am sorry - you are right, I just found the error in my code sorry, sorry, sorry and thanks for the fast feedback! Sebastian On 12 Okt., 16:49, Peter Baumgartner <sgt.hu...@gmail.com> wrote: > It just moved. See: > > http://code.djangoproject.com/browser/django/trunk/dja

Re: 8040 SlugField format not enforced - fixed, closed an "ready for checkin" since two years

/__init__.py#L1000 Sebastian On 12 Okt., 13:34, Luke Plant <l.plant...@cantab.net> wrote: > On Tue, 2010-10-12 at 04:21 -0700, Sebastian wrote: > > Hello, > > the ticket "SlugField format not enforced" is fixed, closed an "ready > > for checkin" si

8040 SlugField format not enforced - fixed, closed an "ready for checkin" since two years

Hello, the ticket "SlugField format not enforced" is fixed, closed an "ready for checkin" since two years. What can I do? Regards, Sebastian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to th

Re: Ticket #14007: Automatically discover models within a package without using the app_label Meta attribute

On Wed, Jul 28, 2010 at 10:45 PM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > On Wed, Jul 28, 2010 at 12:09 PM, Rajeev J Sebastian > <rajeev.sebast...@gmail.com> wrote: >> I think it might be useful for people refactoring their ever-growing >> models.py > &g

Re: Ticket #14007: Automatically discover models within a package without using the app_label Meta attribute

quot; is a package, and because of this, every model within submodules needs an app_label in the Meta. I think it might be useful for people refactoring their ever-growing models.py Regards Rajeev J Sebastian -- You received this message because you are subscribed to the Google Groups "Dj

Re: Admin patches

es, I know this. I am running single tests, when I have changed some tests or added a new one. But finally I want to know if any other test still pass when I have changed something. Regards Sebastian signature.asc Description: PGP signature

Re: Admin patches

failures and 37 errors [1]. Do I have configured my test environment wrong? Here is my settings.py [1]. [1] http://pastebin.org/321014 [2] http://pastebin.org/321027 Regards Sebastian NoacK signature.asc Description: PGP signature

Admin patches

Regards Sebastian Noack signature.asc Description: PGP signature

Re: Django 1.2 release candidate available

the django gods :D Regards Rajeev J Sebastian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to d

Re: Django 1.2 release candidate available

On Thu, May 6, 2010 at 10:37 AM, James Bennett <ubernost...@gmail.com> wrote: > On Wed, May 5, 2010 at 11:53 PM, Rajeev J Sebastian > <rajeev.sebast...@gmail.com> wrote: >> When can we start discussing potential small/micro fixes for the next >> version of django? >

Re: Django 1.2 release candidate available

oday. Congrats on yet another great Django release! When can we start discussing potential small/micro fixes for the next version of django? Regards Rajeev J Sebastian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post

Re: GSoC - Class based serializers

t; things like the "model" field, to collapse the fields dict into the > main obj dict, etc.).  Lastly, I think a more detailed timeline would > be helpful, it's important to get estimates of how long each smaller > change will take (and it helps you flesh out what pieces of work g

Re: Proposal - hook to modify links in object-tools

On Tue, Mar 23, 2010 at 12:20 PM, George Karpenkov <true.chesh...@gmail.com> wrote: > once again, I'm happy to write a patch if people think it's a good > idea Love it! :) Regards Rajeev J Sebastian -- You received this message because you are subscribed to the Google Gro

Re: Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

ite.get_current(), as you seem to have misunderstood. Regards Rajeev J Sebastian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this

Re: Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

"example.com". Anyway, nothing to get so worked up about as you have done. Regards Rajeev J Sebastian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com.

Re: Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

no, that doesn't solve the issue (the solution was outlined by the OP). Its just easier to have this in the settings (imo), because at the point of time (or phase of development) where this is useful, there are usually no fixtures. Regards Rajeev J Sebastian -- You received this message because you ar

Re: Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

ttings SITE_DOMAIN and SITE_NAME instead of blindly using 'example.com'. This prevents the need to go in an edit the domain within the admin (or run some python code in shell) everytime one does a syncdb. It is, quite simply, a suggestion to allow overriding the django default when creating the *d

Re: [Proposal] Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

def_name = settings.SITE_NAME >        except: def_name = "example.com" > > and then create the new site using: >        s = Site(domain=def_domain, name=def_name) > > > I hope this is the correct place to post this! I wanted to hear what > other people though

Re: admin javacripts

about it. It is merely my helpless reaction towards this unfortunate direction in Django and Django ecosystem in general. As someone wrote earlier, *some* choice has to made, and it might as well be jquery. So be it. Amen. Regards Rajeev J Sebastian [1]: http://jqueryvsmootools.com/ -- You received

Re: admin javacripts

at an old checkout: > >  http://code.djangoproject.com/browser/django/trunk/django/contrib/admin/options.py#L273 ... just when I was relieved :P Regards Rajeev J Sebastian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, se

Re: admin javacripts

On Fri, Feb 19, 2010 at 8:01 PM, Javier Guerra <jav...@guerrag.com> wrote: > On Fri, Feb 19, 2010 at 6:32 AM, Rajeev J Sebastian > <rajeev.sebast...@gmail.com> wrote: >> On Thu, Feb 18, 2010 at 8:09 PM, Rob Hudson <r...@cogit8.org> wrote: >>> While certain pa

Re: admin javacripts

On Thu, Feb 18, 2010 at 8:09 PM, Rob Hudson <r...@cogit8.org> wrote: > While certain parts of the admin are (or will be) using jQuery > (widgets, etc.) This really sucks. Kindly don't do this. Regards Rajeev J Sebastian -- You received this message because you are subscribed t

Re: Proposal: Tutorial Refresh

l > seems completely unnecessary. +1 I've trained 8 apprentices over the past 1-1/2 years. The existing django tutorial is invaluable since it can be done in about a day. Regards Rajeev J Sebastian --~--~-~--~~~---~--~~ You received this message becaus

Re: Model.objects.raw() (#11863)

by the DB. For e.g. "SELECT a.*, db_specific_function(a.id) as my_annotation FROM raw_query_author a ORDER BY a.id" Regards Rajeev J Sebastian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Djang

Re: How safe to use #6646 : included template overrides parent

, Sebastian On Mar 30, 3:10 pm, Rory Campbell-Lange <r...@campbell-lange.net> wrote: > On 30/03/09, Russell Keith-Magee (freakboy3...@gmail.com) wrote: > > > > > On Mon, Mar 30, 2009 at 7:44 PM, Rory Campbell-Lange > > <r...@campbell-lange.net> wrote: > &g

Re: Model-validation: call for discussions

xcept the problem of too many levels of indirection" - Kevlin Henney http://en.wikipedia.org/wiki/Abstraction_layer http://en.wikipedia.org/wiki/Butler_Lampson Regards Rajeev J Sebastian --~--~-~--~~~---~--~~ You received this message because you are

Re: Problem with ORM

W dniu 16.01.2009 16:34, varikin pisze: > > On Jan 15, 5:38 pm, Sebastian Bauer<ad...@ugame.net.pl> wrote: > >> I think ORM supposed to have save insert and update: >> >> save(force_insert=False,force_update=False) >> update() == save(force_update=True

Re: Problem with ORM

I think ORM supposed to have save insert and update: save(force_insert=False,force_update=False) update() == save(force_update=True) insert() == save(force_insert=True) in that situation we could have clean code and we know that update is realy update on DB i now we can have

Problem with ORM

Hi I think it's a bug, but maybe im wrong: print Categories.objects.count() >>0 new_obj = Categories.objects.create(name="test") instance_1 = Categories.objects.get(pk=new_obj.pk) instance_2 = Categories.objects.get(pk=new_obj.pk) instance_1.delete() print Kategorie.objects.count() >>0

Re: RequestContext rarely used (branched from Feature reviews for 1.1)

mplate everwhere! I always try to "delegate" to the generic views. Regards Rajeev J Sebastian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: login_required

but we can do this "little" modification in v1.1 i think this change will allow site administrator to ban users through change is_active flag Waylan Limberg pisze: > On Mon, Nov 10, 2008 at 2:49 PM, Sebastian Bauer <[EMAIL PROTECTED]> wrote: > >> Hello, i think

login_required

Hello, i think login_required should check that user is not only authenticated, but also if is active. What do you think about this change? Sebastian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "D

Re: Implementing a pure RDF backend for Django

d faceted browser going using mootools in the frontend and a custom metadata layer. This allowed me to plugin in any ontology (with little modification) and browse the triple store with the faceted browser. Creating triples was also done as a framework with some mootools code in the frontend, and i

Re: GET requests should not alter data?

On Fri, Oct 17, 2008 at 12:54 AM, James Bennett <[EMAIL PROTECTED]> wrote: > > On Thu, Oct 16, 2008 at 7:11 AM, Rajeev J Sebastian > <[EMAIL PROTECTED]> wrote: >> Without trying to read deeply between the lines, the thread seemed to >> come to a point where th

Re: GET requests should not alter data?

request could cause a db write. I *think* thats where Amit is now. (He also mentioned this as the second option) Hope I'm right ... Regards Rajeev J Sebastian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Dj

Re: About FireSymfony and Django

Umm ... Sorry to post that email to the public django-devel list :) I realise it is not for django usage, but core django development. It happened by mistake. Regards Rajeev J Sebastian. --~--~-~--~~~---~--~~ You received this message because you are subscribed

Re: About FireSymfony and Django

to take a look at what you have, and try to port it to Django. Regards Rajeev J Sebastian On Thu, Oct 16, 2008 at 6:27 AM, Alvaro Videla <[EMAIL PROTECTED]> wrote: > > Hi, > > As you may guess, I'm a symfony develper and the creator of > FireSymfony. I read here: http://oebfare.

Re: GET requests should not alter data?

agmatic reasons > that have already been elucidated. I think Amit was just suggesting that these exceptions be documented, and not in the pursuit of a purist goal :) Regards Rajeev J Sebastian --~--~-~--~~~---~--~~ You received this message because you are subscribed to

Re: I want a pony: Django Cheeseshop

e going to be reusable, might as well distribute them as eggs. Or you could just have people drop packages into a specific directory in your project. (Pinax for e.g., has apps/) Regards Rajeev J Sebastian [1] http://peak.telecommunity.com/DevCenter

Re: Proposal: installmedia command - A story for distributing media with apps

? Anyway, I've attached our media app (with the command, etc). If you want any changes to be included, please do tell me. Regards Rajeev J Sebastian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Djan

Re: Proposal: installmedia command - A story for distributing media with apps

e things very simple. Regards Rajeev J Sebastian --~--~-~--~~~---~--~~ 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

Re: djangoproject.com/documentation/ redirected

he new docs...I've been making some > improvements to the new index, which I agree could use some work. Great! Looking forward to it. Regards Rajeev J Sebastian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups &quo

Re: djangoproject.com/documentation/ redirected

d docs frontpage/ToC available at some URL ? That one seemed nicer: more info/links was available without having to scroll down. (Perhaps, its also that I havent gotten used to the new docs yet ...) Regards Rajeev J Sebastian --~--~-~--~~~---~--~~ You rec

Re: Proposal: Widget Templates

te (because 90% of the time, the styling for a given widget on a given site is the same), ... *and* this should be modifiable, i.e. we should be able to set the template for any widget, in each form (maybe using some widget API in the form __init__ method).

Re: ANNOUNCE: Django 1.0 released

Hi James, The release notes has a string that seems wrong ... "Django 1.0 represents revision 88XX of our public repository". Did you forget the XX bit ? Regards Rajeev J Sebastian On Thu, Sep 4, 2008 at 5:37 AM, James Bennett <[EMAIL PROTECTED]> wrote: > > The

Re: Make clickable area of object links larger

ow do you make the whole area clickable with just > style rules? I believe you can set the display of the anchor to block. That should fill the outer block. Regards Rajeev J Sebastian --~--~-~--~~~---~--~~ You received this message because you are subscribed to

Re: GSOC: More backends for djangosearch

The latest PG has its own text indexing/search system ... is this what you are referring to by "tsearch2" ? Regards Rajeev J Sebastian On Mon, Jul 7, 2008 at 11:55 PM, Ben Firshman <[EMAIL PROTECTED]> wrote: > > A quick update! > > School things are well and truly

Re: Community representation, or, #django user "Magus-" needs to go far away

+1 to Tom, though magus On Tue, Jul 1, 2008 at 7:34 PM, Tom Tobin <[EMAIL PROTECTED]> wrote: > On Tue, Jul 1, 2008 at 4:25 AM, Kenneth Gonsalves > <[EMAIL PROTECTED]> wrote: >> >> why should he be more polite? He follows the policy of 'teaching to >> fish' rather than spoonfeeding. I have several

Re: RFC: Django 1.0 roadmap and timeline

Rajeev J Sebastian --~--~-~--~~~---~--~~ 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

Re: Response to "Shortcutting render_to_response"

lling a generic view in a function is quite common and in fact an elegant use of the language. The fact that generic views all use RequestContext is also widely known. So your patch is not strictly necessary. it simply adds burden for people learning to use django. Regards Raj

Re: Want to have unit tests in multiple files

On Fri, 23 May 2008 13:32:45 -0500 "Gary Wilson Jr." <[EMAIL PROTECTED]> wrote: > In case you haven't figured this out already, it can be done by > importing your unit test classes from the test/*.py modules in > tests/__init__.py That is exactly what I have done at my work, just a few days

Re: Add optional FOR UPDATE clause to QuerySets

On Sat, 17 May 2008 13:04:36 +0200 Sebastian Bauer <[EMAIL PROTECTED]> wrote: > Thank you for answer, but for update, i think, is really important > for commercial projects and places where you need to be sure that no > one changed row in parallel I don't think that commercia

Re: Manager-model reassignment on abstract subclassing

, you should update now. I think the patch is ready to get merged into trunk now, but I can not decide this. What does the maintainers think? Regards Sebastian Noack signature.asc Description: PGP signature

Re: QuerySet.update improvement.

e aren't already tickets), and > split the parts of the #7210 patch that fix those issues (and the > relevant tests) into separate patches. I think you are right about (3). But (2) is not a fatal bug, but rather a corner case and handled deep into the new code. Regards Sebastian signature.asc Description: PGP signature

Re: QuerySet.update improvement.

ich might become rounded up- or downwards depending on the db engine. The result of the division test is 2.8 now. This should actually work. Furthermore I am using the operator module instead of eval, now. Thanks for this advice. I just forgot that I can use it for this test. Regards Sebastian Noack signature.asc Description: PGP signature

Re: QuerySet.update improvement.

fortunately, I'm not sure what caused it. I am pretty sure that this is not related to my patch. I get the same failure, and as far as I know I got it even before I wrote the patch. Thanks for testing. Regards Sebastian Noack signature.asc Description: PGP signature

Re: QuerySet.update improvement.

updating sliced query sets, because of calling update() on a sliced query set will update all objects. Do not think about implemeting this feature. Although some DBMS might supports UPDATE with LIMIT and OFFSET, many don't or support only LIMIT (as MySQL for example). Note that (2) and (3) are b

Re: Manager-model reassignment on abstract subclassing

ther that patch should be applied? Thanks. Although I wrote this patch, I have a disagreement. ;-P Tests are still missing. But I think I can wrote some test cases at the weekend or during next week. Regards Sebastian Noack signature.asc Description: PGP signature

Re: Add optional FOR UPDATE clause to QuerySets

Russell Keith-Magee pisze: > On Sat, May 17, 2008 at 3:56 AM, Sebastian Bauer <[EMAIL PROTECTED]> wrote: > >> could someone tell me when this ticket will be add to trunk: >> >> http://code.djangoproject.com/ticket/2705 >> >> its very importan

Add optional FOR UPDATE clause to QuerySets

could someone tell me when this ticket will be add to trunk: http://code.djangoproject.com/ticket/2705 its very important to me because im writing game and i need this to finish Thanks for answer PS. sorry for my really bad english --~--~-~--~~~---~--~~ You

Re: QuerySet.update improvement.

and ~, for completeness. I still have to write tests and documentation, but I would like to hear from Russel or the other maintainers, what they think about the code. Regards Sebastian Noack signature.asc Description: PGP signature

Re: QuerySet.update improvement.

and I have to write test cases. I can't do this now, but I think I will do it in the next days. But it would be cool if somebody can already look on my latest patch, if it is ok. Thanks. Regards Sebastian Noack signature.asc Description: PGP signature

Re: QuerySet.update improvement.

ive test suite to back it up. I know this. But there is no sense do this at the moment. As you already noted there are still a few points to discuss and probably things to change on this code. So I will write documentation and tests when this is finished, because of otherwise I have to do this work twice. Regards Sebastian Noack signature.asc Description: PGP signature

QuerySet.update improvement.

this patch? Or ideas ti even improve this patch? Thanks. Regards Sebastian Noack signature.asc Description: PGP signature

Re: Dev attitude towards Windows and IIS

plore (considering windows in general, maybe you should think again about IIS support expecially given the good alternatives). Regards Rajeev J Sebastian > Thanks. > > Randy > > > --~--~-~--~~~---~--~~ You received this message because you

Re: Model Inheritance in qsrf and User?

kind of purpose anyway). In fact, I would so far as to say "never use inheritance, unless you really know what you are doing". of course, Inheritance being the first thing people teach about OO doesnt help at all. regards Rajeev J Sebastian --~--~-~--~~~---~--

Re: Model Inheritance in qsrf and User?

gt; Could you elaborate or point to elaboration on why non-abstract > inheritance is a bad fit for extending user? Because every app has its own concept/method of how to link info to a User object, hence that information is best held in other models each with a FK to t

Re: [GSoC] Aggregate Support to the ORM

just as the builtin sum, avg, etc ? Regards Rajeev J Sebastian On Wed, Apr 23, 2008 at 1:54 AM, Nicolas E. Lara G. <[EMAIL PROTECTED]> wrote: > > Hello, > I have been selected to implement Aggregate support in the Django ORM > as a project for Google Summer of Code

Re: Template.render() should accept a dictionary, not just a Context object

eturn self.nodelist.render(context) > > This is backwards compatible and would make the template system that > tiny bit nicer to use. The problem with this is that we have to pass an instance of a subclass of Context, rather than something that has the interface of a Context. Is it

Re: Easier URL patterns

t read? Django is the web framework for perfectionists with deadlines! Regards Rajeev J Sebastian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send e

Re: Easier URL patterns

anging on stuff, copying the pattern into Kodos and typing in > the URL I wanted to match it has usually pointed out my mistake in about 90 > seconds. Eric3/Eric4 also has a very good regexp tool which is integrated with it, but also executable standalone from the shel

Re: GSoC proposal: Resource-based Models

>class Meta: >source = sources.FOAFSource() > Btw, RDFAlchemy provides a kind of ORMish layer. I am using it currently in one of my semweb projects though it hasnt yet reached the power of ActiveRDF. Regards Rajeev J Sebastian --~--~-~--~~~---~-

GSoC proposal: Resource-based Models

Introduction of resource-based Models = My name is Sebastian Hillig and I currently study IT Systems Engineering in Potsdam/Germany at the Hasso Plattner Institute. I came to Django when exploring the "world" of web frameworks about 1.5 years ago

Re: ModelAdmin and AlreadyRegistered

Hello Micheal, I guess my very terse response caused some misunderstanding. I meant, we (i.e., dinamis.com in our inhouse projects) put all our admin related stuff for each app in an /admin.py and load it at startup. Sorry for the misunderstanding I caused. Regards Rajeev J Sebastian On Sun

Re: ModelAdmin and AlreadyRegistered

in.py in installed apps sounds good to me. We already do this. Regards Rajeev J Sebastian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: Django ORM performance patch. Fixes #5420, #5768

art in the design > (Database table name + model field attribute name... it's mixing > apples and oranges). In queryset-refactor, we've changed that > (order-by) use double-underscores and only field names, just as in > filters. One of the reasons for this was consistency. > > I thi

Re: Django ORM performance patch. Fixes #5420, #5768

ave many sense as quoted string (even > current QuerySet.order_by() uses '.' instead of '__' as separator). So > from design and usability point of view my form of selecting related > fields is better, I think. Ok, I agree. I would like to getting this feature merged in trunk, too. R

  1   2   >