http://permalink.gmane.org/gmane.comp.python.django.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.python.django.devel/36047 <pre> On Thursday, May 24, 2012 3:57:26 PM UTC+2, Andre Terra wrote: There is a clear consensus about the Pony not fitting here. Almost every project use something from the nature as a logo (a whale, an apple, a leaf, an elephant etc). This is way too boring ! I suggest a good and rock-solid anvil. </pre> Stan 2012-05-25T11:42:57 http://permalink.gmane.org/gmane.comp.python.django.devel/36046 <pre>The single codebase port of Django to Python 3 is now available on GitHub [1]. Recent core changes have been merged, and the test results are available at [2]. Summary: 2.7.2: Ran 4734 tests in 540.793s - OK (skipped=112, expected failures=3) 3.2.2: Ran 4688 tests in 524.807s - OK (skipped=120, expected failures=2, unexpected successes=1) Recent tests only cover the SQLite backend and were run on Linux. Help with testing other DB backends (and the GIS functionality) would be much appreciated! Regards, Vinay Sajip [1] https://github.com/vsajip/django/tree/django3 [2] https://gist.github.com/1373553 </pre> Vinay Sajip 2012-05-25T09:51:54 http://permalink.gmane.org/gmane.comp.python.django.devel/36045 <pre>It's definitely possible for users to support commit=False. If you call form.save(commit=False), you can then store form.save_m2m in a temporary variable, define a new save_m2m function, and then call the old function from the new. Here's sort of an example: https://github.com/pculture/mirocommunity/blob/31688f2/localtv/user_profile/forms.py#L76. Does it a little differently, but the same result. --Stephen On Tuesday, May 22, 2012 2:53:00 AM UTC-7, is_null wrote: On Tuesday, May 22, 2012 2:53:00 AM UTC-7, is_null wrote: </pre> Stephen Burrows 2012-05-25T08:14:27 http://permalink.gmane.org/gmane.comp.python.django.devel/36044 <pre>I already said cbvs are the better option however as you said some solutions require custom views, it seems to me persistent login and registration widgets while an anonymous user instance is present are common practice (ie coming from à context processor) it felt repetitive to keep bending views for such à common thing :-) Thanks for raising the bigger picture tho :-) Op 25 mei 2012 om 08:36 heeft Florian Apolloner &lt;f.apolloner-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; het volgende geschreven: </pre> Hedde van der Heide 2012-05-25T07:55:06 http://permalink.gmane.org/gmane.comp.python.django.devel/36043 <pre>Hi Hedde, On Thursday, May 24, 2012 3:08:22 PM UTC+2, Hedde van der Heide wrote: No they shouldn't be made dynamic at all (none of them!) -- As Andy suggested CBV are a way better option. But those two forms never end up in the same template, so there is no possibility of a clash etc, login goes to /registration/login.html, registration iteself to /registration/somethingelse.html. And if you really send them to the same template you can't use the builtin views and have to write a new view yourself either way... Cheers, Florian </pre> Florian Apolloner 2012-05-25T06:36:04 http://permalink.gmane.org/gmane.comp.python.django.devel/36042 <pre>Hi folks -- Thanks so much to everyone who's participated in this thread; I feel like there's a lot of useful discussion and brainstorming going on. The DSF board met yesterday and discussed the effort -- we're determined to get this done soon. Unfortunately, we ultimately think that this collaborative effort isn't working: there's a lot of great ideas, but some of the discussion is veering closer to "design by committee", and nobody's really empowered to move things forward. Ultimately and sadly, though, great design is at odds to a community process: the only way we know to get something we *love* is to find someone awesome and let them do their thing. So here's the plan: in the next month we're do exactly that: find someone awesome, and give them carte blance on the redesign. We'll of course give feedback, and touch base with the community a few times, but ultimately we're going to put this thing into one person's hands. If you'd like to become the Benevolent Dictator For This Redesign, then please </pre> Jacob Kaplan-Moss 2012-05-24T17:14:36 http://permalink.gmane.org/gmane.comp.python.django.devel/36041 <pre>Here is an updated version of the design. http://i.imgur.com/PKUHM.jpg Let me know what you guys think. The icons and content are simply placeholders and can be changed later on. My experience is in web and UX design and am not a good illustrator or icon designer, so someone more experienced in those areas should ideally be creating the icons and the top illustration. In the design, I still kept the primary call-to-action geared towards new users, because I feel that they would be the ones needing most guidance. People who are existing users or are experienced developers would be much more likely to be able to find what they are looking for by searching, going through the navigation or scrolling down the page, without needing a large button "above the fold". Looking forward to more feedback regarding the design. Thanks. On Thursday, May 24, 2012 7:57:26 PM UTC+6, Andre Terra wrote: </pre> Ashraful Sheikh 2012-05-24T16:28:20 http://permalink.gmane.org/gmane.comp.python.django.devel/36040 <pre>Hi Ashraful, First of all, thank you for contributing with your ideas for this project. Your mockup is one of the most aesthetically pleasing so far IMHO but there are some issues that need addressing before it could be replace the current design. Since the mockup to feedback ratio in this thread seems distant from 1 at the moment, I wanted to contribute to the discussion, so please bear with me. I really like your overall use of whitespace, especially right at the top. My first thought after seeing the design is that it doesn't feel cluttered, and this is my biggest issue with the current layout. But the more I looked into it, the more I noticed key areas are missing. Russel has mentioned several times that djangoproject.com is not only for developers. We need to "sell" the project to sponsors who provide publicity and financial support, and managers who can foment adoption of our most loved framework in design shops around the globe and corporate environments seeking modern solutions to everyday challe</pre> Andre Terra 2012-05-24T13:57:26 http://permalink.gmane.org/gmane.comp.python.django.devel/36039 <pre>&lt; at &gt;Andy, I agree, it's perfectly possible to create you own auth backend now, so theres no need to change it if new views are sceduled. It just felt as a repetitive exercise &lt; at &gt;Florian, The other context variables should be dynamic aswell. I don't agree with your template logic. Django always seems to pass this 'form' name in, which is a problem when you have a page with multiple forms coming form django itself (for example: registration and auth). Ofcourse there's logic workarounds, but still, I don't think those should be hardcoded. Hedde Op 24 mei 2012, om 14:57 heeft Andrew Ingram het volgende geschreven: Met vriendelijke groet, Hedde van der Heide Developer &amp; Sales intellimedia.nl [T] +31(0)6 - 11 717 441 [E] h.vanderheide-SjywH5DZ67IpWRYgfXLN7A&lt; at &gt;public.gmane.org --- TWITTER &lt; at &gt;intelli_media </pre> Hedde van der Heide 2012-05-24T13:08:22 http://permalink.gmane.org/gmane.comp.python.django.devel/36038 <pre>It seems to me there'd be more mileage in making new class-based versions of the auth views. - Andy On 24 May 2012 13:51, Florian Apolloner &lt;f.apolloner-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote: </pre> Andrew Ingram 2012-05-24T12:57:44 http://permalink.gmane.org/gmane.comp.python.django.devel/36037 <pre>Hi, -1 from me here. A) why don't you have site_name_name etc (those are still fixed). B) templates need to be able to rely on a name, if your template expects a different name user {% with form as my_form %} Cheers, Florian On Wednesday, May 23, 2012 1:02:53 PM UTC+2, Hedde van der Heide wrote: </pre> Florian Apolloner 2012-05-24T12:51:25 http://permalink.gmane.org/gmane.comp.python.django.devel/36036 <pre> You really might want to read this thread before posting any mockups - especially Russell's comments. Just to point out one problem: where is the "Code" or "File a bug" link ? If someone wants to contribute to Django in some way: code, doc fixes, translation, money for DSF, etc., the site should make it easy to find the necessary information for that to happen (like a link bug tracker, *link to github*, link to Transifex and a contact to DSF). "Download" is really not the most important link these days. Just my 2 cents. </pre> Łukasz Rekucki 2012-05-24T06:03:44 http://permalink.gmane.org/gmane.comp.python.django.devel/36035 <pre>I played around a bit with using this, and got something quite workable going on. https://bitbucket.org/schinckel/django-multi-schema It's really only an exploration, but does show that it can be done. The problems actually really only got hard once you factor south into the equation. There are a few little hacky things that needed to be done (like setting the search path), and it probably only works on postgres, but as a concept I still feel like it has legs. There are also a couple of other approaches out there, too. Matt. On Thursday, May 24, 2012 3:36:58 AM UTC+9:30, Anssi Kääriäinen wrote: </pre> schinckel 2012-05-24T04:47:20 http://permalink.gmane.org/gmane.comp.python.django.devel/36034 <pre>Hi everyone, I saw this on HackerNews(news.ycombinator.com) and wanted to contribute. Here is my mockup: http://i.imgur.com/dSMSJ.jpg With the design, I focused on keeping the look extremely clean, professional and minimalistic. The content is based on that of the current site. The mockup may seem a bit lacking in color, but adding eye-catching icons for the features, and the screens for the "built with Django" section will add sufficient color to liven up the design. On wider screens, the blog posts will appear in a siderbar to the left of the features list. If you guys like it, email me at inlith-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org, or reply here. You can check out my previous work at madebyargon.com. Some of you may have seen the redesign I did for VideoLAN (videolan.org) which receive a positive reaction from the open-source community surrounding VLC. Thanks. On Saturday, April 28, 2012 2:05:27 PM UTC+6, Russell Keith-Magee wrote: </pre> Ashraful Sheikh 2012-05-24T00:36:53 http://permalink.gmane.org/gmane.comp.python.django.devel/36033 <pre> One schema per tenant would also be pretty good. It makes it much easier to do cross-db queries, or use a public schema for common stuff. This should be doable if/when the support for database schemas is included. I got pretty far in that feature in ticket #6148, but it turns out to be pretty complex to support introspection and creation on all the databases for both production and testing. So, it remains to see if we want to add all that complexity. Still, multitenancy support seems to be one use case where the database schemas support could be very useful in Django. - Anssi </pre> Anssi Kääriäinen 2012-05-23T18:06:58 http://permalink.gmane.org/gmane.comp.python.django.devel/36032 <pre>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 &lt;brett.hay...-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote: </pre> Josh Cartmell 2012-05-23T16:32:21 http://permalink.gmane.org/gmane.comp.python.django.devel/36031 <pre>I couldn't find an existing ticket but I'd like to suggest a change to make the basic auth view more dynamic (I'm not fond of hardcoded context variables :-)) change: def login(request, template_name='registration/login.html', redirect_field_name=REDIRECT_FIELD_NAME, authentication_form=AuthenticationForm, current_app=None, extra_context=None): to: def login(request, template_name='registration/login.html', redirect_field_name=REDIRECT_FIELD_NAME, authentication_form=AuthenticationForm, current_app=None, extra_context=None, form_name='form'): and obviously: context = { form_name: form, redirect_field_name: redirect_to, 'site': current_site, 'site_name': current_site.name, } Kind Regards, Hedde van der Heide </pre> Hedde van der Heide 2012-05-23T11:02:53 http://permalink.gmane.org/gmane.comp.python.django.devel/36030 <pre> On May 23, 3:07 am, Anssi Kääriäinen &lt;anssi.kaariai...-k5wbR+HVKhg&lt; at &gt;public.gmane.org&gt; wrote: If there is need and interest for similar work for DB2 I am Anssi, thank you very much for the offer. We (IBM_DB_DJANGO team) will certainly reach out to you if we are in need of this regards Mario </pre> Mario Briggs 2012-05-23T05:05:57 http://permalink.gmane.org/gmane.comp.python.django.devel/36029 <pre>I did a similar thing for some of my projects - the problem is that you can't reuse any non-multitenant apps without hacking the multitenant stuff in first, ie. it's a bit of a hack, plus it makes things harder to maintain going forwards. One database per tenant should (in theory) make life much simpler. Anthony On 22 May 2012 23:50, Bernardo Pires &lt;carneiro.be-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote: </pre> Anthony Briggs 2012-05-23T00:16:13 http://permalink.gmane.org/gmane.comp.python.django.devel/36028 <pre>On Tue, May 22, 2012 at 4:07 PM, Anssi Kääriäinen &lt;anssi.kaariainen-k5wbR+HVKhg&lt; at &gt;public.gmane.org&gt; wrote: I try to make a point of running the Oracle backend through the test suite in the lead-up to each minor release and fixing whatever I find. Unfortunately, I rarely find the time to do much more than that these days. I wonder whether Oracle would even make it into core if the decision were revisited. </pre> Ian Kelly 2012-05-22T22:56:23 http://permalink.gmane.org/gmane.comp.python.django.devel/36027 <pre>On May 23, 12:35 am, "Daniel Sokolowski" &lt;daniel.sokolow...-rKNhcObLy9Pby3iVrkZq2A&lt; at &gt;public.gmane.org&gt; wrote: I don't know about licensing... I believe the issue is that we don't have enough manpower to keep more backends updated in core. Even now the Oracle backend is somewhat problematic - there aren't that many contributors (or committers for that matter) who have Oracle installed, and thus it is somewhat common that commits break that backend. Then we fix those errors afterwards when/if we spot the errors. Adding another not commonly available backend to the matrix would cause more similar problems. Having the backend in core is somewhat problematic for the above reasons. But not having the backends in core is problematic for the users... Still, at least for now it is better for the backends to live outside core. BTW I have just committed some patches with the aim of making the full Django test suite pass when using django-mssql (another 3rd party backend). If there is need and interest for similar wor</pre> Anssi Kääriäinen 2012-05-22T22:07:45 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.python.django.devel