Re: Djangopeople.net status
> > https://convore.com/djangopeoplenet-development/ - gives http404 > Djangopeople.net is dead? If to be honest I don't understand you, guys! What's the profit of rewriting views to class-based if djangopeople.net is down for a year ? I would like to help, but don't know how. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/9i-ZliqzD6oJ. 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.
Proposal: Signal connection via "my_app.MyModel"
I'd like to suggest adding the ability to connect signals with models by app label and model name. Example API: post_save.connect( my_signal_handler, sender='my_app.MyModel' ) This would allow for better decoupling of code, as well as a far cleaner dependency graph. I'm not certain how this would affect custom signals. I'm primarily speaking of the provided signals in ``db.models.signals``, but this might be something that applies to custom signals as well. -- 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.
Re: Djangopeople.net status
On Wed, May 9, 2012 at 1:37 PM, Alex Sosnovskiy wrote: >> https://convore.com/djangopeoplenet-development/ - gives http404 > > Djangopeople.net is dead? > > If to be honest I don't understand you, guys! What's the profit of rewriting > views to class-based if djangopeople.net is down for a year ? Look at the whois record for djangoproject.com verses djangopeople.net. I don't think djangopeople.net is officially part of Django. Regardless, would you have development on the framework stop so a site that isn't 'core' to the project is tweaked? -A -- 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.
Re: Multi-tenant Django
Alec, Mezzanine is using standard django.contrib.sites. Nothing special there. The main issue with the sites framework is that each site runs using a separate process and settings, so the resources can add up depending on how you setup the stack, and managing the tenants becomes the issue as they grow in number. Apache with modwsgi using self destructing daemons is the best solution here. Until https://code.djangoproject.com/ticket/15089 is resolved IMHO django-hosts is currently the best lightweight solution for multi- tenancy requirements in django, but not useful with a project like Mezzanine I'm afraid. https://github.com/ennio/django-hosts cheers, Brett On May 9, 1:02 pm, Alec Taylor wrote: > Dear Django-developers, > > I've been using Django for a few months now, and recently—for > different projects—started using the web-framework: web2py[1], and the > Django project: mezzanine[2]. > > Both advertise as being multi-tenant solutions[3][4]. > > Would it be possible to extend Django to meet this use-case? — Or have > I overlooked something and is this possible already? > > Thanks for all information, > > Alec Taylor > > [1]http://www.web2py.com/ > [2]http://mezzanine.jupo.org/ > [3]https://groups.google.com/forum/#!topic/mezzanine-users/4XPe5MaD4Fw > [4] PyCon 2012 > talk:http://youtu.be/M5IPlMe83yI?t=5m32shttp://dl.dropbox.com/u/18065445/Slides/PySFTalkSlides.pdf(slide42, > see yt for more info) -- 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.
Re: Djangopeople.net status
On Thu, May 10, 2012 at 9:19 AM, Aaron C. de Bruyn wrote: > On Wed, May 9, 2012 at 1:37 PM, Alex Sosnovskiy wrote: >>> https://convore.com/djangopeoplenet-development/ - gives http404 >> >> Djangopeople.net is dead? >> >> If to be honest I don't understand you, guys! What's the profit of rewriting >> views to class-based if djangopeople.net is down for a year ? > > Look at the whois record for djangoproject.com verses > djangopeople.net. I don't think djangopeople.net is officially part > of Django. I can confirm for you -- djangopeople.net has never been an "official" part of the Django project. It was always an effort run outside of the official (although Simon, the original developer, is a Django core developer). That said, I'm still interested in making djangopeople.net an official resource of the Django project. It was a very useful resource in it's time, which I for one miss. If anyone is interested (including Bruno, if he's still interested) in managing the project for the long term, let me know. Yours, Russ Magee %-) -- 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.
