Re: Caching back-refernces on one-to-one fields

Hi, On Wednesday, January 18, 2012 8:07:26 PM UTC+1, Shai Berger wrote: > > Do you see a reason why I should not post a ticket? > No, please go ahead. Funny you mention that problem now, I ran over the same thing yesterday :) Cheers, Florian -- You received this message because you are

Re: Tutorial for dev version not working (Polls app): admin

Hi, Please post questions to django-users; once we determined it's not an error by you django-developers is the correct mailinglist for discussing bugs. Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this

Re: Fieldsets in forms - ready to check-in

Hi, since it's a new feature and the beta release is already out, there is no chance of getting that into 1.4 -- I think it's best if you push this thread again after 1.4 has been released. Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django

Re: MySQL connection pooling - preferred method??

On Friday, February 17, 2012 10:11:57 PM UTC+1, Cal Leeming [Simplicity Media Ltd] wrote: > > # Apparently this will stop many connections to MySQL > from django.core import signals > from django.db import close_connection > signals.request_finished.disconnect(close_connection) > This approach

Re: MySQL connection pooling - preferred method??

Hi, On Friday, February 17, 2012 11:08:40 PM UTC+1, Cal Leeming [Simplicity Media Ltd] wrote: > > Could you elaborate on this a bit more? And would this affect MySQL? Well there isn't much more to it than a "ABORT; DISCARD ALL" at the end of the session to discard changes and clean (abort)

Re: django-admin.py startproject creating duplicate settings.py files

Cause ``reset --hard`` only resets managed files, not unmanaged files. ``git clean -fdx`` would have done the job (make sure to read the help before issuing that command). Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group.

Re: integration of sphinx documentation in a website a la https://www.djangoproject.com/

Hey, did you know that the webpage is opensource? You can take a look yourself: https://github.com/django/djangoproject.com Cheers, Florian On Friday, February 24, 2012 10:33:54 PM UTC+1, d b wrote: > > Hi, > > I just got started using Sphinx to generate documentation, and am loving > it..

Re: Newline stripping in templates: the dnl way

Hi, On Friday, February 24, 2012 7:48:29 PM UTC+1, ojno wrote: > > Jinja implements whitespace control by putting a minus sign after/before > the % in a tag - http://jinja.pocoo.org/docs/templates/#whitespace-control - > I haven't tried it myself, but it looks like {% tag -%} is equivalent to

Re: Newline stripping in templates: the dnl way

s/why/way/ sry :( On Friday, February 24, 2012 11:47:21 PM UTC+1, Florian Apolloner wrote: > > Hi, > > On Friday, February 24, 2012 7:48:29 PM UTC+1, ojno wrote: >> >> Jinja implements whitespace control by putting a minus sign after/before >> the % in a tag -

Re: Newline stripping in templates: the dnl way

Hi, On Saturday, February 25, 2012 5:27:43 AM UTC+1, Tai Lee wrote: > > Adding more symbols to existing tags (e.g. {^ for x in y ^} or {% for > x in y -%}), multi-line comment tags that don't actually include a > comment, and half baked comment tags (where the closing tag is > assumed) are all

Re: Newline stripping in templates: the dnl way

Hi, On Saturday, February 25, 2012 10:04:21 AM UTC+1, Anssi Kääriäinen wrote: > > In most situations white space matters: > {{ user.lastname }} {{ user.firstname }} > Right, but """ {{ user.lastname }} {{ user.firstname }} """ would have produced exactly the same output in HTML, hence my

Re: override_settings with dynamic model creation

Hi, On Monday, February 27, 2012 2:53:37 PM UTC+1, Alisue wrote: > > But I found that ``override_settings`` is available in dev version of > django. So I just wonder that if official django's > ``override_settings`` support dynamic model creation. ``override_settings`` does exactly what the

Re: New feature: Support for MessagePack Serializer

Hi, since this Serializer can be easily maintained outside of core there is no need to include it. -1 from me. Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit

Re: Django participation in Google Summer of Code 2012

Hi, Am Donnerstag, 8. März 2012 15:51:58 UTC+1 schrieb Vladimir Perić: > > I was also considering applying for as a GSoC student to Django this > summer, but I see that the "Python 3 porting" project has been removed > from the new list. Is there a reason for this? > Django already has a

Re: authentication by email

Hi, On Friday, March 9, 2012 6:54:16 AM UTC+1, Clay McClure wrote: > > if settings.AUTH_EMAIL_AUTHENTICATION: > Hell, not another ugly setting like this. Should these things really take five years? What happened to pragmatic? > Yes, since no one needs it. Okay no one isn't true, but no one

Re: Language Translation

Hi, please post usage questions to django-users. Thx. On Friday, March 9, 2012 4:23:37 PM UTC+1, Vishnu vg wrote: > > Hi Friends, > > I have a cms based existing django site. I want to translate it to german > or other language, Please suggest which is the best method? > > > -- > Regards > >

Re: auth.User refactor: reboot

Hi lepture, aside from the fact, that it's not really a security bug we do ask people not to report security issues public but mail to security at djangoproject.com. Reporting them in the open does help neither you nor us. And please don't hijack threads like this -- this thread is about a

[GSoC 2012] Questions regarding the contrib.auth project

Hi, I would like to participate in this years Google Summer of Code. As a project I would like to tackle Django's beloved auth.User model. The topic has been discussed quite extensively the last days so I won't repeat everything here again. My prefered solution would be "Solution 3" from the

Re: Tagging 1.4 django release in Subversion

Hi, it's not tagged yet on purpose. Cheers, Florian On Sunday, March 25, 2012 8:26:17 AM UTC+2, jdetaeye wrote: > > > Can a developer please tag the 1.4 release in the SVN repository please? > Ie create >

Re: Tagging 1.4 django release in Subversion

Hi, good news: tag is there (https://code.djangoproject.com/changeset/17810) On Monday, March 26, 2012 6:05:47 AM UTC+2, Tai Lee wrote: > > How come? The release that can be downloaded from the site already must > correspond to an SVN revision number, right? Why not tag it as such so that >

Re: Tagging 1.4 django release in Subversion

Hi Tom, On Monday, March 26, 2012 5:59:45 PM UTC+2, Tom Evans wrote: > > Out of interest, is there any documentation of the release process? > Not sure if the process is documented in public somewhere, a quick search suggests no -- might be wrong. > I'm also intrigued how you have a release

Re: Tagging 1.4 django release in Subversion

Hi, On Tuesday, March 27, 2012 7:09:44 AM UTC+2, Łukasz Rekucki wrote: > > For a moment, I thought we could have some more of that magic and > amend the commits in git, so that "author" would be the patch > contributor and commit author would be the "committer". This should be > possible in most

Re: Http404 and process_exception

Hi, this mailing list is for the development of django itself. Please direct user question to django-users. Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit

Re: Dropping django.utils.simplejson

Hi, I am for number 2 too, but don't forget that's deprecation in 1.5 and 1.6 and removal in 1.7 Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit

Re: auth.user refactor: the profile aproach

Hi Adrian, On Tuesday, April 3, 2012 10:34:18 PM UTC+2, Adrian Holovaty wrote: > > I chatted about this with Jacob on IRC, and we reached consensus on > this approach. I'd like to get moving on this and would be happy to > take it on myself, starting next week. > I'd like to help out there, could

Re: extra files in startproject

On Friday, April 13, 2012 6:49:32 AM UTC+2, Alex Ogier wrote: > > I have seen setup.py's that use remove_tree as part of a "clean" command > to allow someone to run "setup.py clean && setup.py install" to obtain > a pristine distribution idempotently, which I think is a good idea. > No, they

Re: GitHub migration planning

Hi, On Tuesday, April 24, 2012 7:30:05 AM UTC+2, Tai Lee wrote: > I just remember Adrian basically saying (and I'm paraphrasing here): "I've > been away too long, but I'm back now and I've decided that we're moving to > GitHub!" > I had that feeling a bit myself, but I think there have been

Re: GitHub migration done!

On Tuesday, May 1, 2012 6:40:53 PM UTC+2, dstufft wrote: > > Pretty sure this isn't going to make a compatible with the existing > mirror > mirror but http://hg-git.github.com/ should make it easy to go from git > -> hg. > Far from easy, last time (or actually times) I tried to use it it

Re: GitHub migration done!

On Wednesday, May 2, 2012 3:37:07 PM UTC+2, Florian Apolloner wrote: > > Far from easy, last time (or actually times) I tried to use it it broke in > many horrible ways :( [And either the link isn't listing an up2date project > or it's really dead since 3 years] > Ignore the

Re: Djangopeople.net status

On Friday, May 11, 2012 1:40:45 AM UTC+2, dstufft wrote: > > djangopeople.me ? > I for one hate the fact that it's twitter login only :( -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit

Re: #18277 : Passing additional context to startproject command

On Tuesday, May 15, 2012 3:53:56 PM UTC+2, Dominique Guardiola Falco wrote: > > Example use case : in order to make a valid wsgi.py file, pass the > virtualenv site-packages folder path > Why would your wsgi file need to know the site-packages folder? Shouldn't the external hosting mechanism

Re: Suggestion: make auth login view more dynamic

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

Re: Suggestion: make auth login view more dynamic

Hi Hedde, On Thursday, May 24, 2012 3:08:22 PM UTC+2, Hedde van der Heide wrote: > > @Florian, The other context variables should be dynamic aswell. > No they shouldn't be made dynamic at all (none of them!) -- As Andy suggested CBV are a way better option. > I don't agree with your

Re: Draft branch: Swappable User models in contrib.auth

Hi, On Wednesday, June 6, 2012 4:32:02 PM UTC+2, Anssi Kääriäinen wrote: > > Still, yet another API idea: [snip] > > Then, Model.__new__ will replace the SwappableUser class with the > swapped in class. The 'swappable' in model.Meta tells which concrete > model implementation to use. > I'd

Re: auth_permission column lengths

Hi Greg, Django itself can't change that currently since there is no support for schema alteration in Core. Once we get that we can tackle issues like that and increase to a sensible limit. (both name and codename might cause problems…). Cheers, Florian -- You received this message because

Re: Skip session save on 500 responses

On Friday, July 6, 2012 12:02:56 AM UTC+2, Luke Plant wrote: > > I agree it should be changed, and I would regard it as a bug fix, but > make a note of it in the 1.5 release notes nonetheless. > +1 Cheers, Florian -- You received this message because you are subscribed to the Google Groups

Re: propagating unnamed groups to included URL patterns

Hi, there is no need to write to django-developers to notify us about ticket changes, we do follow trac and there is an extra ML for ticket updates. Cheers, Florian On Wednesday, July 11, 2012 5:18:44 PM UTC+2, Stefan Talpalaru wrote: > > https://code.djangoproject.com/ticket/18494 > > I've

Re: When to close pull requests

Hi, On Sunday, July 15, 2012 11:07:41 AM UTC+2, Anssi Kääriäinen wrote: > > I think we should categorically close pull requests which are non- > trivial and do not contain ticket reference, and also those pull > requests which are more than "last polish" away from merge. Even in > the case of

Re: new syntax for management commands

Hi, On Sunday, August 12, 2012 2:22:58 AM UTC+2, Russell Keith-Magee wrote: > > I'll agree that it looks appealing. However, as always, my question is > about backwards compatibility. > Seriously? In my eyes it's ugly, especially if you have more than one options. Eg imagine you have

Re: django.core.urlresolvers swallowing AttributeErrors

Fixed in https://github.com/django/django/commit/367bfaa5226eaae3278989e63f16063d5cc46cd8 On Tuesday, August 14, 2012 6:01:56 PM UTC+2, Dan Passaro wrote: > > Hello, > > I was working on a project and noticed that urlresolvers.py would swallow > attribute errors in user code. > > The way the

Re: ``models.BooleanField`` fields default to ``False`` when missing from fixtures

On Monday, September 24, 2012 3:07:37 PM UTC+2, Yo-Yo Ma wrote: > > Yep, that looks like it. IMHO, this is a bug that should be fixed without > delay, as it breaks a cardinal rule for Pythonistas, and could even lead to > a "data corruption" situation, if a dev was to add a boolean field and >

Re: Http handler may assign urlresolver-related data to request

Hi Benoit, as a matter of fact I want to add that to 1.5, and I started playing with a small testapp to see what's needed: https://github.com/apollo13/django-locale-switcher -- My conclusion is also that stuffing the resolver_match on the request would be the best option. We have another five

Re: Http handler may assign urlresolver-related data to request

I added a patch to https://github.com/django/django/pull/399 -- Let me know what you think, if I don't get any negative feedback I'll commit it before the feature freeze. Cheers, Florian On Tuesday, September 25, 2012 4:00:48 PM UTC+2, Florian Apolloner wrote: > > Hi Benoit, > >

Re: Feature request: collectstatic shouldn't recopy files that already exist in destination

Hi Jeremy, On Tuesday, October 9, 2012 5:15:04 AM UTC+2, jdunck wrote: > > Would it be reasonable to have a backend-specific hook to determine a > fingerprint, where that could be mtime or md5 or whathaveyou as long as > equality (or maybe ordering) works? > Given our discussion in IRC

Re: Feature request: collectstatic shouldn't recopy files that already exist in destination

Hi Stephen, On Tuesday, October 9, 2012 7:28:43 AM UTC+2, Stephen Burrows wrote: > > I'm a little confused by the track the discussion took recently... my > impression was that the solution would *not* be to change from > last_modified to a checksum, or to add an additional checksum method. >

Re: URL dispatcher slow?

Oh cmon, please stop playing a socket puppet for the wheezy.web author. A web framework consists of more than just a win in speed (an the author of wheezy.web can argue whatever he wants that "basic" stuff stuff should be fast) -- if we were looking for speed we wouldn't use python at all

Re: URL dispatcher slow?

Hi, I won't answer your rheotircal questions ;) On Thursday, October 11, 2012 8:02:19 AM UTC+2, Yo-Yo Ma wrote: > > BUT... Django is NOT that fast. > We do know that (you know that and probably everyone else too) and I already said in my post that Django isn't the fastest framework out there.

Re: How to test patch

Hi, On Monday, October 29, 2012 1:29:14 PM UTC+1, Aymeric Augustin wrote: > > We tried moving Django's CI to Travis about 6 months ago. Unfortunately, > Travis' time limit is too low for Django's test suite. We contacted them, > but as of August 6th, we were still waiting for them to increase

Re: Unicode SlugField

Hi, it surely won't change in 1.5 since we already released an alpha. Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit

Re: Github tags

Hi, They are (now) all there and signed with the release key: https://github.com/django/django/tags -- Please tell us if we missed something! Thx, Florian On Friday, November 2, 2012 5:17:25 AM UTC+1, Samus_ wrote: > > hi, I think that's great :) in the meantime could you please indicate the

Re: Status of bug #11580 ?

Hi Michał, The bug got accepted by a core dev, so the next thing to do for you if you want to get this bug fixed is probably to work on a patch. With 1.5 coming this year it would be the perfect time to fix it ;) Our plans are obviously to fix all existing bugs, but as you can imagine our time

Re: Custom user models in 1.5, not flexible/dry enough?

Hi Alex, On Tuesday, November 6, 2012 11:55:39 PM UTC+1, Alex Ogier wrote: > > So, I went ahead and implemented the most useful mixin of the three that I > defined previously, the PermissionsMixin. > I am not really sold on the idea of having this PermissionMixin, for one reason: If I need a

Re: Django and South

Please search this group for discussions on this topic. Regards, Florian On Tuesday, November 20, 2012 5:29:28 AM UTC+1, Илья Лебедев wrote: > > I've realized that django has no migration tool in development and that > looks weird for me. Everybody use South, but django neither includes it in

Re: ticket #19324: empty records in django_session table caused by invalid session keys

Hi Robert, there is no need to notify us about tickets here, we do see those in Trac ;) Best Regards, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit

Re: Improved ajax support idea

Hi, On Thursday, November 22, 2012 11:39:54 AM UTC+1, is_null wrote: > > More projects use AJAX nowadays. Django could help them more. Django somehow does that already: It doesn't stand in your way :) > All generic views could do something like this. The point is to provide a > consistent

Re: Admin Javascript Roadmap/Brainstorming

Hi Tyler, On Wednesday, November 28, 2012 6:24:57 PM UTC+1, Tyler Ball wrote: > > - jQuery: Inlines are written as a jQuery plugin, DateTime and i18n are > written without jQuery. The version of jQuery included is 1.4.2, which is > ~3 years old. Do we want to have jQuery in this project? I

Re: Yet another __ne not equal discussion

On Friday, November 30, 2012 6:12:43 PM UTC+1, Shai Berger wrote: > > live_articles = Article.objects.exclude(status="archived") > live_cats = Category.objects.filter(article__in=live_articles) > That works and it has the positive side-effect to kill any mysql server in a matter of seconds

Re: Proposal: Django URL Admin (django-urls)

Hi Zach, On Friday, December 7, 2012 9:07:32 PM UTC+1, Zach Borboa wrote: > > Does something like this exist already? If not, it should. I am wondering what you are trying to achieve with this post. If you only want to know if something like this exists you should ask in django-users, this

Re: Oracle backend bug makes testing on oracle slower?

On Tuesday, December 11, 2012 8:53:55 PM UTC+1, Shai Berger wrote: > > Should I open a ticket for it? It is a one-line patch... > Please try to test this on master first, we most likely won't patch 1.3. Cheers, Florian -- You received this message because you are subscribed to the Google

Re: Django 1.1 is not installable

On Friday, December 14, 2012 9:01:27 PM UTC+1, Michael Elsdörfer wrote: > > I'm only using Django 1.1 as part of CI tests, and they have started > failing recently because of this, so I'd be happy to see it fixed. > I am strongly against showing non-supported versions on PYPI, I also don't see

Re: First request - Modify django.core.management.color with settings option

I dislike a setting for this, an optional environment variable would make more sense imo (since you usually don't want to set this for one project but all…). Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this

Re: Weird error on bad form class

Hi, On Thursday, December 20, 2012 9:29:06 PM UTC+1, Francisco Vieira wrote: > > Oh, and by the way, I'm using Django version 1.4.3. If this has already > been fixed in 1.5 forget this... > I think I indeed fixed that for Django 1.5:

Re: Relative path support for TEMPLATE_DIRS and others in settings.py (django ticket 694)

Hi, On Saturday, December 22, 2012 10:35:59 PM UTC+1, Ben Porter wrote: > > I would like to see support for relative paths. It seems the solution is > simple, but I wonder if there is some compelling reason to require absolute > paths? It would seem so but it is everything but simple: First

Re: Relative path support for TEMPLATE_DIRS and others in settings.py (django ticket 694)

Hi, On Tuesday, January 1, 2013 7:48:59 PM UTC+1, Cal Leeming [Simplicity Media Ltd] wrote: > > Rather than saying "spend 30 seconds thinking about it", could you perhaps > spend 30 seconds explaining why using relative paths for TEMPLATE_DIRS > would be considered a bad thing to do? I

Re: Using condition on signal.post_save()

This mailing list is about the development of Django itself, please direct user questions to django-users. Regards, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit

Re: Relative path support for TEMPLATE_DIRS and others in settings.py (django ticket 694)

Hi, On Wednesday, January 2, 2013 8:19:36 PM UTC+1, ted wrote: > > FWIW, this is a working draft of a default settings file I like that > addresses most of these issues: > https://github.com/tedtieken/django-project-skel/blob/master/project_name/settings.py > (would appreciate constructive

Re: Relative path support for TEMPLATE_DIRS and others in settings.py (django ticket 694)

Hi Ted, On Wednesday, January 2, 2013 10:26:10 PM UTC+1, ted wrote: > Florian, the method you use for environment specific settings is one of > the two most common I saw in my survey: local_settings.py being the most > common. Again, best practice vs common practice I don't know. > In my

Re: BUG:can't createsuperuser??

Hi zhfisher, On Wednesday, January 16, 2013 10:51:17 AM UTC+1, zhfisher wrote: > > Django version=1.5 rc1 > Database:mySQL > > E:\Work\Code\Django\SaleTools>manage.py createsuperuser > D:\Python27\lib\site-packages\django\utils\hashcompat.py:9: > DeprecationWarning: > django.utils.hashcompat is

Re: BUG:can't createsuperuser??

Hi Mugisha Moses, On Wednesday, January 16, 2013 3:09:46 PM UTC+1, Mugisha Moses wrote: > > http://www.joelonsoftware.com/articles/Unicode.html > While you surely wanted to be helpful, a link like this isn't really helping to solve the problem. Given the fact that the user is on windows and we

Re: postgresql range types v2

Hi, On Thursday, January 17, 2013 11:08:01 PM UTC+1, Russell Keith-Magee wrote: > > So - while I'm not sure there's a place for this in core (unless you can > demonstrate how to implement range types on other backends), it should be > *possible* to use this library as a third party extension.

Re: Is there a buildbot? Is there a waterfall? Do the tests pass against all backends?

Hi, you can see the tests at http://ci.djangoproject.com/ -- currently Oracle is untested cause it's a major pita to setup on ubuntu. Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and

Re: Is there a buildbot? Is there a waterfall? Do the tests pass against all backends?

Hi, On Friday, February 22, 2013 10:01:44 PM UTC+1, Shai Berger wrote: > > but other than that, it > was quite easy to get going. I use it on my laptop (which is easily strong > enough) for development. > Yeah, I know about it and set it up on the CI during the sprints, it's still

Re: [SPAM] Re: Is there a buildbot? Is there a waterfall? Do the tests pass against all backends?

The problem is that it segfaults, when something like a segfault happens you usually don't get more information than that... I tried to debug the segfault but cx_Oracle or rather the instantclient stuff is installed without debug information :/ -- You received this message because you are

Re: Is there a buildbot? Is there a waterfall? Do the tests pass against all backends?

Hi, On Monday, February 25, 2013 6:31:19 PM UTC+1, Jacob Kaplan-Moss wrote: > > Would a dedicated Oracle build slave machine (VM, probably) help? So, the current status is: We have Oracle itself running in Virtualbox on the Jenkins, this does work. The issue is that cx_Oracle (or the oracle

Re: Is there a buildbot? Is there a waterfall? Do the tests pass against all backends?

Hi Shai, On Monday, February 25, 2013 5:27:06 PM UTC+1, Shai Berger wrote: > > Without knowing anything, my first guess would be a mismatch between the > python > version used to run the test and the one used to build cx_Oracle. But if > you > install cx_Oracle from source, that's probably

Travis support (again)

Hi, so during the sprints a few people (thanks to everyone involved, sadly enough I can't remember all the names, so I refrain from mentioning an incomplete list) worked on adding and testing travis support to Django which resulted in this ticket: https://code.djangoproject.com/ticket/19891

Re: [SPAM] Re: Is there a buildbot? Is there a waterfall? Do the tests pass against all backends?

Hi Shai, On Tuesday, February 26, 2013 2:18:14 AM UTC+1, Shai Berger wrote: > > > No, since the Oracle tests are somewhat slow we decided to just test one > > Python for now. I will try to see if Python 2 makes a difference, didn't > > yet think of it. > > > > Cool. > They do work on

Re: Switch to database-level autocommit

Yay (+1) and preferably ASAP to get it tested by users right now. -- 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

Re: deprecation of AUTH_PROFILE_MODULE

Hi, On Friday, March 1, 2013 9:00:28 PM UTC+1, Luke Sneeringer wrote: > > I'd be interested in actually doing this if folks on the list think it's a > good idea. > Doing it outside of Django core if fine, inside core is -0 to -1 from me. Cheers, Florian -- You received this message because

Re: Switch to database-level autocommit

Hi Shai, On Sunday, March 3, 2013 12:27:47 AM UTC+1, Shai Berger wrote: > > > I also believe that it beats the alternative — namely, live with the > > > current behavior forever. > > > I sincerely hope that is not the only alternative; that there's a way to > implement the new behavior

Re: deprecation of AUTH_PROFILE_MODULE

Hi Jacob, On Sunday, March 3, 2013 5:08:24 PM UTC+1, Jacob Kaplan-Moss wrote: > > I actually strongly disagree: I think Django *should* ship an > "authenticate-using-email" system. > Out of curiosity, since I barely have this need by myself: Is it "authenticate-using-email" or

Re: Switch to database-level autocommit

Hi, On Monday, March 4, 2013 2:00:03 PM UTC+1, Aymeric Augustin wrote: > > PostgreSQL and Oracle use the "repeatable read" isolation level by > default. According to http://www.postgresql.org/docs/9.1/static/transaction-iso.html PG uses "read commited" as default. > MySQL uses "read

Re: Moving database backends out of the core

Hi, On Tuesday, March 5, 2013 8:35:07 PM UTC+1, Michael Manfre wrote: > > The current discussion about "Switch to database-level autocommit" ( > http://bit.ly/ZlVERI) reminded me of a past discussion regarding moving > the database backends out of the core. I don't remember exactly where I >

Re: Moving database backends out of the core

Hi Shai, On Tuesday, March 5, 2013 10:32:29 PM UTC+1, Shai Berger wrote: > > In recent years, I have been the main contributor to South's MSSQL and > Oracle > backends. I am biased towards having MSSQL treated as an equal to the > database > systems supported in core, but also towards support

Re: Moving database backends out of the core

On Tuesday, March 5, 2013 11:01:01 PM UTC+1, Florian Apolloner wrote: > > I am obviously biased against postgres as my previous post indicated, but > regardless of that I think that MSSQL should stay outside of core. No > core-developer I know actually uses Windows as base

Re: Switch to database-level autocommit

On Wednesday, March 6, 2013 8:49:37 AM UTC+1, Ian wrote: > > On Tue, Mar 5, 2013 at 3:13 PM, Aymeric Augustin > wrote: > > In the mean time, I discovered that it's impossible to implement > > TransactionMiddleware reliably as a middleware, because there's no >

Re: Moving database backends out of the core

Hi Andre, On Tuesday, March 5, 2013 11:39:29 PM UTC+1, Andre Terra wrote: > > but at work I'm restricted to corporate rules, MS SQL or Oracle, and > Windows. Right, that's probably one of the reasons why Oracle is in core (aside from the fact that we were completely monolithic at that

Re: Moving database backends out of the core

Hi, On Wednesday, March 6, 2013 3:32:45 PM UTC+1, Michael Manfre wrote: > > The lack of data validation is definitely a nogo for production sites, but > imo sqlite in production is also a nogo. > Right, but shipping Django with a non production db might send interesting signals to endusers ;)

Re: Moving database backends out of the core

Hi, On Friday, March 8, 2013 4:24:00 AM UTC+1, Michael Manfre wrote: > > django-mssql is actively maintained and will be for at least the next few > years because it's used for my employer's production site that is critical > to business operations. The backend also supports stored procedures

Re: Moving database backends out of the core

On Friday, March 8, 2013 3:35:53 PM UTC+1, Michael Manfre wrote: > > If we have MSSQL in core I'd really like to be able to talk with it from a > Linux machine too, it would also make testing easier since we'd just need a > VBox with MSSQL ;) Supporting a commercially available product but >

Re: Request for review: database-level autocommit

Hi Aymeric, On Friday, March 8, 2013 11:32:52 PM UTC+1, Aymeric Augustin wrote: > > Carl was kind enough to review the branch in detail. (Thank you!) > > I'll take his feedback into account, clean up the history, and push a new > version tomorrow. I hope to merge it during the week-end. > If you

Re: Test failures under Oracle

Hi, On Sunday, March 10, 2013 6:33:08 PM UTC+1, Petite Abeille wrote: > > > I'm only dealing with Oracle to fix failures in Django's test suite or > ensure that new features are supported under Oracle. Clearly I'm not smart > or knowledgeable enough to take advantage of its docs. > If you can

Re: Test failures under Oracle

Hi, On Sunday, March 10, 2013 7:48:02 PM UTC+1, Petite Abeille wrote: > > (1) Whereabout way to get table metadata (i.e. query the table to figure > out its data to figure out its meta data). Instead, using the data > dictionary directly would be more reliable and to the point, e.g. select >

Re: Test failures under Oracle

Hi, On Sunday, March 10, 2013 9:00:57 PM UTC+1, Petite Abeille wrote: > > > Patches welcome… > Yes, I wish I knew Python. Sadly I don't. :) > Interesting. Out of curiosity may I ask what brought you to this ML then? (Don't get me wrong, it's just not that often that people write to this

Re: Documenting lazy() and memoize()

Hi Tom, On Friday, March 15, 2013 12:11:04 PM UTC+1, Tom Evans wrote: > > Any thoughts on this please? > What's wrong with the solution provided by Donald, which is already in core? Regards, Florian -- You received this message because you are subscribed to the Google Groups "Django

Re: Appomatic: A django app packaging system based on pip

Hi Egil, this mailinglist is for the development of Django itself, you might wanna write to django-users. Regards, Florian -- 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,

Re: Is there a buildbot? Is there a waterfall? Do the tests pass against all backends?

Hi, On Tuesday, March 19, 2013 8:21:05 AM UTC+1, Shai Berger wrote: > > Is there any interest in fixing this, specifically? > Sure, I just don't have to knowledge to debug cx_Oracle, so if you are up to please. Although I think the endresult would most likely be a patch to cx_Oracle and not

Jenkins missing all Django jobs

Hi, I updated jenkins today and ran into a major issue (https://issues.jenkins-ci.org/browse/JENKINS-17337). This will be fixed in a few hours and I'll update jenkins tomorrow. Sorry for the inconvenience. Regards, Florian -- You received this message because you are subscribed to the

Re: Jenkins missing all Django jobs

And fixed On Monday, March 25, 2013 10:06:21 PM UTC+1, Florian Apolloner wrote: > > Hi, > > I updated jenkins today and ran into a major issue ( > https://issues.jenkins-ci.org/browse/JENKINS-17337). This will be fixed > in a few hours and I'll update jenkins t

Re: loaddata --ignorenonexistent not working for XML based fixtures

Hi, this got committed a while back. Thx, Florian -- 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

  1   2   3   4   5   6   7   8   9   >