Django 1.6 GenericRelation regression

[Josh Cartmell]

I am a developer that helps out with Mezzanine and 
ever since 1.6 came out we have been struggling to get Mezzanine to 
work under it.

The trouble that we have run into in 1.6 is getting a GenericRelation to 
show up in admin fieldsets, this worked previously.

Here is a link to the Mezzanine issue where we have been discussing/working 
on this on Github:
https://github.com/stephenmcd/mezzanine/issues/745

Here is a very simple Django project and app, sans Mezzanine, with a 
unittest that fails under 1.6 but works under 1.5 and illustrates the 
problem:
https://bitbucket.org/joshcartme/16genericissue

I think this might be a Django bug, should I open an issue on trac?

Regards,
Josh

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/fbfcc2af-3a39-4e73-9a9e-c141becdf59c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Django 1.5.1 released

[Josh Cartmell]

Thanks for the extra details Jacob.  I had a bit of time and thought
it was an interesting challenge so I created a Google Script based
twitter bot that tweets the title and links of everything posted to
the Django Announce Google group.

There may be bugs but so far it's working, you can check it out here:
https://twitter.com/djangoannounce

On Apr 3, 9:17 am, Jacob Kaplan-Moss  wrote:
> On Tue, Apr 2, 2013 at 11:02 PM, Russell Keith-Magee
>
>  wrote:
> > In short, no - Twitter isn't a particularly reliable source for updates.
> > Someone in the core team will usually tweet about the release, but since
> > it's hard to share logins to a single Twitter account, and the person who
> > owns Django's twitter account won't always be involved in formally cutting
> > the release, we sometimes drop the ball.
>
> Actually, in theory we've got hootsuite set up to automatically tweet
> stuff posted to the blog. However, in practice it seems to break, and
> it hasn't updated in about two weeks. I'm looking into fixing it, and
> we'll try to keep a better eye on it ferm here on out.
>
> But yeah, as Russ says -- the announce list is going to be the most
> reliable. The number of things that could break about the blog ->
> hootsuite -> twitter flow make it rather unreliable.
>
> Jacob

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Django 1.5.1 released

[Josh Cartmell]

That makes sense, thanks for the explanation and the pointers to the
best sources of information.  I never realized the Django announce
mailing list existed, it will serve my purposes perfectly as I'm sure
it's intended to!

Regards,
Josh

On Apr 2, 9:02 pm, Russell Keith-Magee <russ...@keith-magee.com>
wrote:
> Hi Josh,
>
> In short, no - Twitter isn't a particularly reliable source for updates.
> Someone in the core team will usually tweet about the release, but since
> it's hard to share logins to a single Twitter account, and the person who
> owns Django's twitter account won't always be involved in formally cutting
> the release, we sometimes drop the ball.
>
> Our official channels are the django-announce mailing list, and Django's
> blog. If you're looking for guaranteed notification, those two channels are
> guaranteed to receive notification.
>
> Yours
> Russ Magee %-)
>
>
>
>
>
>
>
> On Wed, Apr 3, 2013 at 12:10 AM, Josh Cartmell <joshcar...@gmail.com> wrote:
> > Thanks for the release!
>
> > Kind of random question, but this seems like the best place to ask
> > it.  I used to use Twitter mobile notifications to keep up with Django
> > releases, but I've noticed that the last three releases (since 1.4.4)
> > have not been announced on Django's Twitter.  Is this just an over-
> > site, or is Twitter no longer a good place to keep up with Django
> > releases.
>
> > Thanks,
> > Josh
>
> > On Mar 28, 2:02 pm, Jacob Kaplan-Moss <ja...@jacobian.org> wrote:
> > > Hi folks --
>
> > > We've just released Django 1.5.1, a bug fix release that cleans up a
> > > couple issues with last month's 1.5 release.
>
> > > The biggest fix is for a memory leak introduced in Django 1.5. Under
> > > certain circumstances, repeated iteration over querysets could leak
> > > memory - sometimes quite a bit of it.
>
> > > For more details, see our announcement:
>
> > >    https://www.djangoproject.com/weblog/2013/mar/28/django-151/
>
> > > Thanks for using Django!
>
> > > Jacob
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Django developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to django-developers+unsubscr...@googlegroups.com.
> > To post to this group, send email to django-developers@googlegroups.com.
> > Visit this group athttp://groups.google.com/group/django-developers?hl=en
> > .
> > For more options, visithttps://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Simplify the default project template

[Josh Cartmell]

Long time lurker here.  Anyways, one thing that I think might trip up
beginners is this line:
# Quick-start development settings - unsuitable for production

For a beginner that could be a very daunting statement that could
leave them wondering:
Why is this unsuitable for production and what is suitable for
production?  Is it inefficient or insecure or both?

I think a little more explanation regarding it's unsuitability would
make it a lot less scary.  In line with what you have done here it
might make sense to add a new section to the docs describing how to
make the default settings production ready and then link to it after
that statement.

On Jan 29, 1:01 pm, Aymeric Augustin
 wrote:
> Hello,
>
> I took into account the feedback received here and on IRC (thanks everyone!) 
> and I now have a branch ready for review:
>
> https://github.com/aaugustin/django/compare/simplify-project-template
>
> The commit messages give some hints about the reasoning behind each change. 
> I'll be glad to provide more detailed explanations if necessary.
>
> Like Jacob said, everyone here would certainly do this a bit differently. 
> Let's avoid bikeshedding — if you can't resist, tell me in private — and look 
> for problems such as:
>         - I got the priorities wrong: forgot something important / included 
> something useless,
>         - I missed some best practices,
>         - I did something that's likely to trip up beginners,
>         - etc.
>
> I plan to commit this next week. Let me know if you'd like more time to 
> review.
>
> Thank you,
>
> --
> Aymeric.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Multi-tenant Django

[Josh Cartmell]

I wanted to point out that Mezzanine doesn't actually just use
django.contrib.sites.  Mezzanine uses django.contrib.sites and thread
locals.  The way it is set up example1.com and example2.com can both
be driven by the exact same django instance but have different
content.  The third paragraph in the first post of this thread
explains a bit more about how it works:
http://groups.google.com/group/mezzanine-users/browse_thread/thread/e173dee4c683e05c

On May 9, 8:15 pm, Brett H  wrote:
> 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.
>
> Untilhttps://code.djangoproject.com/ticket/15089is 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/S...,
> > 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.