Re: High Level Discussion about the Future of Django
One of the main advantages of Django over other web frameworks is twofold: 1. Almost anything can be overridden with a custom backend (auth, e- mail, context processors, middleware, etc.) 2. Custom backends can be plugged in side-by-side with "stock" backends What functionality do you feel is holding Django back in particular? NoSQL support? Cloud architecture? In my opinion, the best course of action is to write a backend for a desired piece of functionality and then release it as open source. Just because something doesn't make it into trunk doesn't mean that it can't be a popular modular extension to Django in real-world deployments. As for Python 3.x support, I think the #python welcome message sums it up: "It's too early to use Python 3.x" :-) -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Default ordering on User model
Is there a reason that the default ordering on the User model is by pk? Would it be a reasonable request to ask that the default ordering for this model be username? I have several models that have a m2m to the User model, and it's very hard to find someone to add using the admin when the users are in pk order. I wanted to test the waters before opening a ticket. -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Django, The Web Framework for perfectionists and innovative with rechargeable batteries.
So anyways... Google App Engine is a special case. It is not nearly as robust a database solution as something like CouchDB or MongoDB - but then again it was never meant to be. The direction from the beginning was on scaling, even if it meant dropping features. The BigTable ORM lacks many of the functions necessary for implementing the Django ORM on that database. Python-only solutions to these gaps would not scale as well as low-level database APIs, and as such would probably not scale well enough to be useful. The situation has not improved because Google doesn't see a need. App Engine fits in an even more specialized niche than most NoSQL solutions. That said, a lot of work has been done to make Django useful on that platform. My own web site runs Django 1.2.1 on App Engine. Things like auth, caching, and sessions have been implemented without porting the ORM. So really, the only barrier to "pure" Django on App Engine is the model, which needs to be rewritten for each application used on GAE. Now django-nonrel is doing some excellent work to try to implement a workable ORM on App Engine. However, I'm sure they are facing an uphill battle because of the constraints of the platform. I have no doubt that they will indeed produce a workable solution in time, though. I've been doing lots of research with Django on GAE, and am actually using it in production. If you're interesting in this particular stack, please contact me off-list and I can attempt to answer any questions that you have. -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Django, The Web Framework for perfectionists and innovative with rechargeable batteries.
Jacob, My work is very much in progress, and will be documented (with code samples) fairly regularly over the coming weeks and months. The blog itself is the guinea pig - running Django 1.2.1 on GAE. Please visit http://www.tiemonster.info/ for more information. After reading Waldemar's comments below, my next step will be to revisit django- nonrel and see the progress made since the last time I visited. Waldemar, I had no idea a working ORM had already been produced. I'll be looking at and reviewing your work as soon as possible. I'll provide as much feedback as I can which I hope can aid you in your work. As far as gaps in the ORM are concerned, the first issue I ran into is the lack of textual searching. I've found nothing similar to the __contains modifiers in the Django ORM. This makes it especially difficult to do full-site searching - something which I am implementing at the moment by iterating through the entire set of posts and doing the textual searching in python. This is obviously not an ideal solution. This is what I meant by "python-only solution". I've also run into issues with aggregation (SUM, MIN, MAX, etc), which I don't see a solution for in the GAE ORM. I am very excited that the code has been released, and that you've had luck with several third-party applications. Like I said, I'll definitely be checking that out as soon as possible. Last I checked, you were just looking into it (perhaps a while ago now). Cheers! -Mark On Jul 31, 11:27 am, Jacob Kaplan-Moss wrote: > On Sat, Jul 31, 2010 at 9:04 AM, tiemonster wrote: > > I've been doing lots of research with Django on GAE, and am actually > > using it in production. If you're interesting in this particular > > stack, please contact me off-list and I can attempt to answer any > > questions that you have. > > I'd love to see a public write-up of your project, techniques you > used, and how you're liking the results. Maybe blog about it, or post > it here? > > Jacob -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Django 1.3 and Python 2.4
Yeah - we're stuck with CentOS into the foreseeable future. Manually compiling Python to a different prefix, and then recompiling mod_wsgi and other modules against this version is really not an option at this point. If Django 1.3 deprecated support for Python 2.4, then we would be forced to remain on 1.2 until CentOS/RHEL received an update to python. I work at a university, and have colleagues at lots of other universities, and everyone I know that runs Linux is running some variant of RHEL. This is, in my opinion, unfortunate. However, it's a cultural shift that's going to take a while. If it were up to me, we would have been running Ubuntu Server a long time ago... -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: contributing to django as a part of master thersis
I'll be spending the next two years working on a event-driven python application server. As part of this work, I'll be investigating asynchronous database calls. I'll definitely report as I make progress in that arena. I'm envisioning a patch to the ORM that allows writes to be processed in the background. Obviously any reads in the same request wouldn't have access to that data, though, as in the current design. If anyone has a way around that, or if it generally accepted that that's ok, let me know. I'm all ears. :-) -Mark Cahill -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
