Re: Merging Schema Alteration branch

On Saturday, August 10, 2013 4:41:28 AM UTC+2, Russell Keith-Magee wrote: > > Say… Andrew… there's this guy on a black horse at my front door… says his > name is "Famine"… he wants to talk about the coming apocalypse… :-) > Indeed, I already got migrations which magically unapply themself

Re: Avoid unbounded memory consumption when running `manage.py test`

Hi Matt, On Thursday, August 1, 2013 12:08:23 AM UTC+2, Matt McClure wrote: > > Is the ultimate upstream the CPython repository now? Or a separate > unittest2 repository? For Python >= 2.7 it should be CPython; for everything below the separate unittest2 repository. -- You received this

Re: Support Negative Indexing on QuerySets

Hi Wim, On Wednesday, July 31, 2013 12:04:42 AM UTC+2, Wim Lewis wrote: > > On 30 Jul 2013, at 2:06 PM, Florian Apolloner wrote: > > How do you think such support would look like? For negative indices > you'd have to know the size of the resultset to be able to do "limi

Re: Support Negative Indexing on QuerySets

On Wednesday, July 31, 2013 1:03:31 AM UTC+2, Andre Terra wrote: > > On Tue, Jul 30, 2013 at 6:55 PM, Florian Apolloner > <f.apo...@gmail.com > > wrote: > >> Right, it depends on your usecase; I was just trying to point out other >> alternatives aside from

Re: Support Negative Indexing on QuerySets

On Tuesday, July 30, 2013 11:34:18 PM UTC+2, Andre Terra wrote: > > On Tue, Jul 30, 2013 at 6:06 PM, Florian Apolloner > <f.apo...@gmail.com > > wrote: > >> You can always do list(qs)]:-1] though… > > > Although you really shouldn't [1]. Right, it depend

Re: Support Negative Indexing on QuerySets

Hi Mark, How do you think such support would look like? For negative indices you'd have to know the size of the resultset to be able to do "limit somthing offset length-your_negative_index" -- this doesn't seem to make any sense for an ORM. You can always do list(qs)]:-1] though… Cheers,

Re: docs.djangoproject.com very slow

Hi, should be back to normal by now. On Monday, July 29, 2013 7:46:20 PM UTC+2, Kevin Veroneau wrote: > > Not sure where to report this, but the docs.djangoproject.com is going > very slow today, and I received a "504 Gateway Time-out" from the nginx > server. Any ideas? > -- You received

Re: Deprecate FCGI support in Django 1.7

On Monday, July 15, 2013 9:55:51 PM UTC+2, Aymeric Augustin wrote: > > - Django's core developers don't use FCGI — at least, I don't know any > active core dev who does. > I do, but with a patched flup and a patched suexec and what else, so I am hardly a typical usecase; and I am in the

Re: Deprecate FCGI support in Django 1.7

On Monday, July 15, 2013 6:20:45 PM UTC+2, Some Developer wrote: > > What about SCGI and AJP support? Is that going? > Yes, it's either all or nothing. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and

Re: Deprecate FCGI support in Django 1.7

On Monday, July 15, 2013 4:14:43 PM UTC+2, Jannis Leidel wrote: > > If you're suggesting to move the FastCGI code into a separate app: +1 > I'd have just dropped it, but yes we can move it out; although someone else will have to step up to continue maintaining it (if there is a need to

Re: Deprecate FCGI support in Django 1.7

On Monday, July 15, 2013 7:07:08 AM UTC+2, Russell Keith-Magee wrote: > > I'm not arguing that FastCGI is a good option, just that it's prevalent. > And if we're going to stop supporting it, we need to be aware of who we're > cutting off. > We won't cut anything off (maybe aside from the

Re: Spam on ticket #542

On Monday, July 15, 2013 3:20:16 AM UTC+2, Ramiro Morales wrote: > > Would it be worth look at the web server log to see if these comments > were effectively created by HTTP POST requests at all? > That's what I did to figure out the ip (which I blocked via iptables before Aymeric played

Deprecate FCGI support in Django 1.7

Hi, I'd like to get rid of everything FCGI-specific in Django sooner or later (rather sooner). Flup isn't maintained since a long time and there is no ticket tracker to report stuff. Graham pointed out that if someone wants to use FCGI they can use

Re: Supported Python versions for Django 1.7

Hi, On Friday, June 28, 2013 4:17:22 PM UTC+2, Aymeric Augustin wrote: > > As far as I can tell, there's a consensus on dropping support for Python > 2.6. That will allow us to remove the vendored copy of unittest2 and to > take advantage of datastructures introduced in Python 2.7 like

Re: SQL from Models

Hi, this list is about the development of Django itself, please take your question to django-users. Thanks, 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

Re: Proposal: add request decompression to gzip middleware

Hi, On Sunday, May 26, 2013 3:49:48 PM UTC+2, Sébastien Béal wrote: > > - limit resources available with the resource module. Is there any other > parts of Django using this technique? Using rlimits are imo not an option; as (to my knowledge) it affects the whole process and not just the

Re: Reopening/Refixing #20246

Hi, On Sunday, May 19, 2013 8:18:48 PM UTC+2, Claude Paroz wrote: > > I'm not completely sure. The narrow space should certainly be used between > a number and its unit symbol (kg, cm, Mb, etc.). So your proposal is at > least valid for a part of the patch. However, for "5 hours, 4 minutes",

Re: Proposal: add request decompression to gzip middleware

Hi, given that I already think that the GzipMiddleware is a bad idea (it should be left up to the webserver), I don't like the idea of adding this to the current middleware. Any reason why you couldn't do this in the webserver? Regards, Florian -- You received this message because you are

Re: ORA-01882 [was Re: looking up date as str (fails under Oracle, Ticket #20015)]

Hi Shai On Sunday, May 19, 2013 7:12:12 AM UTC+2, Shai Berger wrote: > > Florian, Aymeric, or any Django/Oracle user in Kenya: How did you overcome > this? > I have no idea, I just bang my head against the CI till it works or falls completely apart (well not really, but you get the gist ;)).

Reopening/Refixing #20246

Hi, I don't think that the fix of #20246 [0] is correct. You started using \xa0 while Wikipedia clearly suggests that we should use a narrow space instead of a full-space (probably U+202F). This is something we learned during our physics courses too, so it's in line with what science

Re: test discovery

On Saturday, May 11, 2013 2:38:23 PM UTC+2, Carl Meyer wrote: > > No good reason, just an oversight I think. If that's all that's needed to > make the CI happy, feel free to change it, should be a simple fix. > Perfect, pushed a fix, let's see what jenkins says. -- You received this message

Re: test discovery

Hi Carl, before I read all the tickets etc; why does runtests.py not use the TEST_RUNNER from settings.py (see https://github.com/django/django/commit/9012833af857e081b515ce760685b157638efcef#L60L149)? We'd need that for jenkins to produce xml files as output. Thanks, Florian -- You

Re: test discovery

Not good, at least our Jenkins runner which should generate xml output doesn't like it :/ On Saturday, May 11, 2013 5:36:55 AM UTC+2, Carl Meyer wrote: > > I merged this patch tonight. Thanks to everyone who contributed! Now let's > see how the CI servers feel about it... > > Carl > > On

Re: Data concurrency, consistency and serializabe

Hi, this question seems to be more suited for django-users. django-developers is for the development of Django itself. 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

Re: Test failures under Oracle

Hi, now that the 1.6 release plan is out, I'd like to push this topic again. If you are using Oracle, now is the time to fix those bugs. Personally I am toying with the idea of dropping Oracle support from core if we can't ensure it's quality. Regards, Florian -- You received this message

Re: Changing deferred model attribute behavior

On Thursday, April 25, 2013 7:06:06 PM UTC+2, Adrian Holovaty wrote: > > Also, I should mention that this should be *optional* behavior, as the > current behavior is reasonable for the common case. The API for specifying > this "load everything" behavior is a separate discussion. Perhaps a

Re: [GSoC 2013] contribute to django-deployer for deploying django to PaaS easily

Hi, aside from what Russell already pointed out, I would like to add a few points: * You list "Refactor for Expandability" as last on your schedule. I think it should be at the start, eg compare different solutions like GAE, heroku, Gondor, find a common subset and then write the backends

Re: [GSoC 2013] contribute to django-deployer for deploying django to PaaS easily

Hi, On Saturday, April 20, 2013 8:03:43 PM UTC+2, LittleQ@NCCU, Taiwan wrote: > > cuz seems like there's no #django-dev, so feel free to add my XMPP > directly: littl...@gmail.com There is #django-dev (sic) on irc.freenode.net. Regards, Florian -- You received this message because you are

Re: Problem with creating a one-to-one instance

Hi Carsten, first of all, django-dev is not a second level support list, so for the future please refrain from posting here just because you get no answer on the user list. As for the issue on hand, try accessing ma.vbp_id after you assign the instance, this should give you some clues.

Re: ALLOWED_HOSTS : Cannot allow hosts with single label

Hi, it's hard to say anything without knowing your real alias, the tests work for me as soon as I remove the underscore which is indeed not allowed in hostnames! Regards, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To

Re: Kickstarter for Django Admin?

Hi, I already wanted to look at hyperadmin, but got caught up reading what HATEOAS is and how it works first ;) I do have one question if you don't mind: With a REST/HATEOS backend you'd export links with appropriate rel attributes to tell the client what we can do. So far so good, but let's

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

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

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: 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

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: 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: 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: 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 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: 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: 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: 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

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 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: 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

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: 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

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: 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: 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 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, 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

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: [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

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: 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

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: [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 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: 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: 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: 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: 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: 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: 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: 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 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: ``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: 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: 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: 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: 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: 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: 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: 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: 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: 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

<    2   3   4   5   6   7   8   9   >