Re: AbstractUser hierarchy and email-based-users

Russ tried to complete the "EmailUser" solution for 1.7, but if I remember correctly, there was some issue with testing that couldn't be easily resolved. https://github.com/django/django/compare/master...freakboy3742:emailauth Anyway, if that issue is still blocked, it looks like the `SimpleIde

Re: Improving MSSQL and Azure SQL support on Django

Thursday and Friday >> are coding sprints, where there will be many people (including a good >> chunk of the core team) looking for projects to hack on. >> >> Microsoft is already a sponsor of DjangoCon itself; if we can get some >> engineers from the Azure team (

Re: Ability to migrate other applications

e something on your wishlist? DSF Fellow >> Tim Graham has an offer for you: groups.google.com/d/msgid/django… > > > Well, actually, I'd really like this for 1.9 ;-) > > Has anyone +1's for this or is it more like -1's ? > > >> Sample project is a

Re: WIKI_VIEW privileges are required to perform this operation. You don't have the required permissions.

This issue turned out to be a bug in Trac, fixed by upgrading to the latest version. Details in https://github.com/django/code.djangoproject.com/issues/58. On Monday, August 31, 2015 at 8:35:30 AM UTC-4, Tim Graham wrote: > > Hi, as far as I know, we haven't banned anyone in T

Re: Ability to migrate other applications

My main concern is not with the complexity of your proposed patch but with committing to supporting a new API that solves a problem that can already be solved a different way (albeit maybe less elegantly). Anyway, I don't want to speak definitely about the issue, but it seems like if we keep th

Validate domains against IDNA2008 instead of IDNA2003?

Quoting this ticket: https://code.djangoproject.com/ticket/25337 """ IDNA domains validation is a mess, anyway, it's going forward, and IDNA2008 refines IDNA2003 proposal to better define what is a valid IDN domain and what is not. ICANN/IANA [ https://www.icann.org/resources/pages/idn-guidelin

Re: Django Admin - ModelAdmin exclude

A pull request has been offered: https://github.com/django/django/pull/5214 It seems simple enough to me. Marc or Luke, would you withdraw your objection after seeing the implementation? On Wednesday, September 2, 2015 at 7:09:18 AM UTC-4, Ramez Ashraf wrote: > > I agree that there are a lot of

Re: Django with Pycharm

Hi, This is off-topic for the django-developers mailing-list, which is dedicated to the development of Django itself. Please send questions like this to django-users. Thanks! On Friday, September 4, 2015 at 11:07:11 AM UTC-4, Nick Sarbicki wrote: > > Hi Prabhu, > > Are you using the community or

Re: status of 1.9 release blockers

15 at 3:40:22 PM UTC-4, Tim Graham wrote: > > Time to kickoff the progress tracker for the next major release! > > Here's the status with 4 weeks to go until alpha (September 21). > > Release blockers: > > - Add Oracle support for new-style GIS functions > https://c

Fellow Report - September 5, 2015

Report for week ending September 5, 2015: Triaged --- https://code.djangoproject.com/ticket/25330 - RuntimeError: Error creating new content types." when upgrading to 1.8: due to contenttype.name (duplicate) https://code.djangoproject.com/ticket/25338 - IOError exception information ge

Re: Password validation in Django revisited

I think the simplest solution could be to remove the default list of AUTH_PASSWORD_VALIDATORS that have been added to the project template settings file and let the user add it to their own production settings instead. Do you think this reduces the usefulness of the feature? We could add a depl

Re: Password validation in Django revisited

don't want these validators >> in development either. Personally, I have no issue with adding a SETTING=[] >> to my local_settings. It would be nicer to drive a solution based on DEBUG >> though. >> >> Cheers >> >> >> On Tuesday, 8 September 201

Re: draft blog post for Oracle help

l) apps with Django framework and oracle > backend for 8 years now. I am familiar with the problems associated with it > because few times I have been forced to find ways to solve them:) > > FeliXX > > W dniu czwartek, 13 sierpnia 2015 18:12:17 UTC+2 użytkownik Tim Graham > napi

Re: Proposal to document the error on trying to import django in python 3.4.

I think a better use of time could be to update the docs to more strongly recommend virtualenv and discourage the use of `sudo pip install`. On Wednesday, September 9, 2015 at 10:17:48 AM UTC-4, Anjul Tyagi(geety) wrote: > > Thanks for all that information Nick, it helped me a lot. > > Yes, it w

Enforcing a max size for form field values read into memory (review/determination of next steps needed)

Hi, I think I will be able to make good on my promise to give all the tickets that were in the review queue on last Friday a review for 1.9, except for this one... https://code.djangoproject.com/ticket/21231 https://github.com/django/django/pull/3852 Mostly I am wondering if there any other fra

Re: Proposal to document the error on trying to import django in python 3.4.

I created a ticket: https://code.djangoproject.com/ticket/25376#ticket You can read about how to get started contributing to Django in our docs: https://docs.djangoproject.com/en/dev/internals/contributing/ If you have any trouble, #django-dev is a good place to ask questions. Thanks! On Thurs

Re: Proposal to document the error on trying to import django in python 3.4.

Could you please submit a pull request? It's much easier to review and leave comments that way. Thanks! On Friday, September 11, 2015 at 10:22:45 AM UTC-4, Anjul Tyagi(geety) wrote: > > I drafted the changes in the current documentation regarding emphasizing > the use of virtualenv. Have a look

Fellow Report - September 12, 2015

Report for week ending September 12, 2015: Triaged --- https://code.djangoproject.com/ticket/25366 - Changing the type of a primary_key field in a migration does not update FK columns pointing to it (duplicate) https://code.djangoproject.com/ticket/25354 - related_query_name doesn't su

Re: Making the test suite run faster

Aymeric merged this on Thursday. Big thanks to him! Now it's time to have a competition to build the machine that will run the Django test suite in the fastest time. :-) On Wednesday, September 9, 2015 at 3:06:30 AM UTC-4, Aymeric Augustin wrote: > > Le 8 sept. 2015 à 18:42, Michael Manfre > >

Re: status of 1.9 release blockers

riday, September 4, 2015 at 3:55:22 PM UTC-4, Tim Graham wrote: > > Status with 2 weeks and a weekend to go until alpha (Monday, September 21). > > Planned major features for 1.9: > > PostgreSQL Full Text Search (Marc Tamlyn) > > I haven't seen any recent activity on

Re: status of 1.9 release blockers

turday, September 12, 2015 at 7:50:31 PM UTC-4, Tim Graham wrote: > > With 1 week to go until alpha: > > I haven't heard anything from Marc or Preston on the major features from > the last mail. > > Jani continues to give updates in #django-dev about his progress on > ge

Re: Capturing faked migrations in django_migrations table

Maybe we could have BaseCommand remove the 'console' handler from the 'django' logger during the command's execution (at least under normal verbosity conditions)? As mentioned on the pull request, there is also an idea to update management commands to use logging [1]. I think the two ideas coul

Re: Django help

Hi Ketan, You might like to read the archives of the django-core-mentorship mailing list as similar inquiries have been made there. https://groups.google.com/forum/?fromgroups#!forum/django-core-mentorship Feel free to ping me (timograham) in #django-dev on IRC if you want to chat. Tim On Fri

Re: Ticket #23242 -- Approximate date_hierarchy

values at all, or are you required to use the enum? >> >> I don't think setting date_hierarchy to a tuple is any cleaner. >> >> On Monday, August 31, 2015 at 12:54:21 PM UTC-6, Tim Graham wrote: >>> >>> This seems okay at first glance, though

Fellow Report - September 19, 2015

On the infrastructure side, I added Python 3.5 support to Jenkins (Django 1.9 will support it) and removed our own “wheelhouse” of cached wheels since Pip 7+ now provides that functionality. I also completed the “new stable branch tasks” for bootstrapping Django 1.10 which can be merged after

Methodology for increasing the number of PBKDF2 iterations

The latest guidance on increasing the number of PBKDF2 iterations for each release of Django was written by Alex in July 2014: For each release... "Increase the default PBKDF2 iterations in django.contrib.auth.hashers.PBKDF2PasswordHasher by about 20% (pick a round number)." He noted in that c

Re: Methodology for increasing the number of PBKDF2 iterations

Django 1.8 is the last version to support Python 3.2 and 3.3, so I believe we could assume Python 2.7.8+ and 3.4+ as of Django 1.9. While we only *officially* support the latest release of each Python series, explicitly dropping support for < Python 2.7.8 might not be acceptable, however, it se

Re: Why leave explicit null=True when blank is True in IntegerField, DateField etc?

As Yo-Yo mentioned, there are valid use cases for blank=True, null=False, and I believe having one field option implicitly change another actually adds complexity instead of simplifying things. On Monday, September 21, 2015 at 6:52:08 PM UTC-4, Paulo Maciel wrote: > > Why confused? It's optional

Re: status of 1.9 release blockers

me doc enhancements now, I will review in the morning. On Friday, September 18, 2015 at 10:03:45 AM UTC-4, Marc Tamlyn wrote: > > Sorry everyone :( > > On 18 September 2015 at 15:01, Tim Graham > wrote: > >> The major features are officially deferred. Let's try for th

Re: ANNOTATIONS WORKING

What's the ticket number? On Tuesday, September 22, 2015 at 7:56:04 AM UTC-4, varun naganathan wrote: > > The bug is already reported and the triage stage is accepted.I'm in the > path of trying to fix the bug so kind if needed guidance on how to pursue > solving it . > Thanks -- You receive

Re: Proposal to document the error on trying to import django in python 3.4.

See if https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/working-with-git/ helps. If you have further questions, it's probably easier if ask can ask in #django-dev on IRC rather the on this mailing list (which reaches hundreds of people). Thanks! On Tuesday, September

moving the class-based View base class out of django.views.generic?

Class-based view users, does this proposal from https://code.djangoproject.com/ticket/25385 seem like a good one? --- Whenever I talk about class-based views and how their concept is separate from generic views (typically in a class setting), the question I am asked is invariably: if they ar

Re: status of 1.9 release blockers

pha then (whether or not the patch is completed). 3) Create the 1.9 branch today to allow normal development to proceed on master and release the alpha by the end of the week with the option to backport the patch if it's completed. Opinions? On Monday, September 21, 2015 at 9:08:22 P

Re: Methodology for increasing the number of PBKDF2 iterations

As I understand it, the problem with increasing the number of iterations on the slower hasher is that upgrading Django could effectively result in a DDoS attack after you upgrade Django as users passwords are upgraded. Some benchmarking suggests that the new algorithm results in a 3x speed up (

Re: Methodology for increasing the number of PBKDF2 iterations

We have access to the plain text password when the user logs in. On Tuesday, September 22, 2015 at 1:23:01 PM UTC-4, Xof wrote: > > > On Sep 22, 2015, at 10:18 AM, Tim Graham > > wrote: > > > As I understand it, the problem with increasing the number of iterations &

Re: Methodology for increasing the number of PBKDF2 iterations

to store the upgraded password. If pbkdf2 is slow, isn't it reasonable that this could cause a CPU spike on a high traffic site? On Tuesday, September 22, 2015 at 1:39:12 PM UTC-4, Xof wrote: > > > On Sep 22, 2015, at 10:27 AM, Tim Graham > > wrote: > > > We

Re: Methodology for increasing the number of PBKDF2 iterations

aynor wrote: > > Sure, but such a problem has nothing to do with password upgrades, it can > already be triggered by registration, or even just logging in without a > password upgrade. > > Alex > > On Tue, Sep 22, 2015 at 2:43 PM, Tim Graham > wrote: > >>

Re: status of 1.9 release blockers

his being > part of a core component and it has to be done right. > > /Markus > > On Wednesday, September 23, 2015 at 2:54:50 AM UTC+10, Tim Graham wrote: >> >> The second patch has been committed, and the first one is still under >> review. >> >> F

Re: status of 1.9 release blockers

All known issues are resolved. I plan to create the branch and make the release in about 4 hours if nothing else pops up. On Wednesday, September 23, 2015 at 9:46:40 AM UTC-4, Tim Graham wrote: > > I'm okay with deferring it. I'll see if we can release the alpha later > toda

[ANNOUNCE] Django 1.9 alpha 1 released

We've made the first release on the way to Django's next major release, Django 1.9! With two and a half months until the scheduled final release, we'll need timely testing from the community to ensure an on-time and stable release. Check out the blog post: https://www.djangoproject.com/weblog/2

Re: draft blog post for Oracle help

PM UTC-4, Mariusz Felisiak wrote: > > https://code.djangoproject.com/wiki/OracleTestSetup instruction is ready, > enjoy > > W dniu wtorek, 8 września 2015 14:14:44 UTC+2 użytkownik Tim Graham > napisał: >> >> Another place to help is to update the instructions on how to

Re: Skip IN clause on prefetch queries?

Regarding the "missing message", it's there now. If you are a first-time poster, your mail is held in a moderation queue. On Friday, September 25, 2015 at 6:35:34 AM UTC-4, Erik Cederstrand wrote: > > Hi devs, > > My lengthy email to this list about improving performance of > prefetch_related()

simplifying the install page

The install page mentions several different ways to install Django, from pip install (recommended), to `setup.py install`, to symlinking the Django checkout in your site-packages. Do you see any reason to keep the latter methods instead of recommending pip all the time? https://docs.djangoproj

Re: Some love for admindocs

It might be interesting to fork it and develop your vision as a separate project so you can iterate more quickly. At some point we could evaluate whether the existence of an actively maintained external package would allow us to deprecate the version in Django itself (as has been previously pro

Re: simplifying the install page

.html > > It's worth noting too, that although newer versions of python include > pip and venv, some distros have decided not to install pip and venv by > default. > > On Fri, Sep 25, 2015 at 1:07 PM, Daniele Procida > wrote: > > On Fri, Sep 25, 2015, Tim Gr

Fellow Report - September 26, 2015

Report for week ending September 26, 2015: Triaged --- https://code.djangoproject.com/ticket/25441 - Add support for negative filesize to filesizeformat template filter (accepted) https://code.djangoproject.com/ticket/25434 - Missing documentation for request.site attribute (accepted)

Re: draft blog post for Oracle help

tember 2015 00:34:21 Tim Graham wrote: > > Thanks again for updating those instructions. Just a couple things: > > > > I second that. > > > 1. The DATABASES setting should have an 'other' database as they did > > before. > > > > 2. I t

Re: Improving MSSQL and Azure SQL support on Django

Hi Meet, I was wondering 1. If you have any progress updates since your last message? 2. If you have any further details on the schedule for the time in Seattle in a week and a half? (including video conference details for those unable to attend in person) 3. If myself or the other attendee

Re: status of 1.9 release blockers

8 PM UTC-4, Tim Graham wrote: > > All known issues are resolved. I plan to create the branch and make the > release in about 4 hours if nothing else pops up. > > On Wednesday, September 23, 2015 at 9:46:40 AM UTC-4, Tim Graham wrote: >> >> I'm okay with deferring it.

Fellow Report - October 3, 2015

Report for week ending October 3, 2015: Triaged --- https://code.djangoproject.com/ticket/25473 - Consistently use dashes instead of underscores in URL names (accepted) https://code.djangoproject.com/ticket/25478 - 1.8 migrating doc code sample needs parens (worksforme) https://code.dj

[ANNOUNCE] Django bugfix release issued: 1.8.5

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2015/oct/03/bugfix-release-issued/ -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group an

Re: forcing a name for a sqlite in memory shared cache test db

I guess this is probably a use case that wasn't considered when writing that patch. Feel free to submit a pull request. On Monday, October 5, 2015 at 9:55:14 AM UTC-4, riccardo.magliocchetti wrote: > > Hello Andriy, all, > > i need to being able to reference a sqlite3 shared in memory test data

Re: Reverse manager assignments doing an implicit save

The deprecation seems reasonable to me as it would clear up confusion about why most model attribute assignments require a model save but not this one. Implemented here: https://github.com/django/django/pull/5413 On Friday, April 20, 2012 at 10:00:01 AM UTC-4, Anssi Kääriäinen wrote: > > I was g

Fellow Report - October 10, 2015

Report for week ending October 10, 2015: Besides the usual, I spent some time this week combing the ticket tracker for issues that have been fixed, are obsolete, or are duplicates -- hence the large number of “triaged” tickets below (also some of the “authored” items are regression tests for

Re: Improving MSSQL and Azure SQL support on Django

12:32:25 PM UTC-7, Tim Graham wrote: >> >> Hi Meet, >> >> I was wondering >> >> 1. If you have any progress updates since your last message? >> > > > * Yes, engineers on my team I are currently ramping up on the t

Re: Django pass User instance to Forms when form is created

Please write to django-users, this mailing list is for the development of Django itself. On Wednesday, October 14, 2015 at 2:50:56 AM UTC-7, Ernest Appiah wrote: > > > > > I have a Django form and l would like to pass a user instance when the > form is created > > *First Approach* > > This is wh

Re: Duplicate window for upload image

Please write to django-users, this mailing list is for the development of Django itself. On Wednesday, October 14, 2015 at 10:32:55 AM UTC-7, Rosangela Oliveira wrote: > > Hi,I need some help > > I have a problem when I try to upload the image in a django project, it's > open the windows t

Re: status of 1.9 release blockers

We're on schedule for Monday's beta release. Most of the backported fixes have been issues affecting 1.8 too. On Saturday, October 3, 2015 at 10:31:13 AM UTC-4, Tim Graham wrote: > > We've resolved a couple of release blockers on the stable/1.9.x branch > since th

Re: Django 1.9 AppRegistryNotReady

This seems to be expected behavior, "In other words, your applications’ root packages and the modules that define your application configuration classes shouldn’t import any models, even indirectly." from https://docs.djangoproject.com/en/1.8/ref/applications/#how-applications-are-loaded You sa

Fellow Report - October 17, 2015

Report for week ending October 17, 2015: This week I spent three days at Microsoft HQ in Seattle at the first "open source data camp". As I understand it, the "data camps" are normally held to inform Microsoft partners about current and upcoming offerings in Microsoft cloud services and to ge

should manage.py test run system checks?

A ticket [1] and pull request [2] note that `manage.py test` ran the system checks in Django 1.7 (as a side effect of call_command('migrate')), but this is no longer the case in Django 1.8 since call_command() doesn't trigger the system checks anymore. me: I'm of the opinion that running the sy

[ANNOUNCE] Django 1.9 beta 1 released

We've made the second release on the way to Django's next major release, Django 1.9! With a month and a half until the scheduled final release, we'll need timely testing from the community to ensure an on-time and stable release. Check out the blog post: https://www.djangoproject.com/weblog/201

Re: #25582: Add a way to build URLs with query strings

Can you make an API proposal? On Friday, October 23, 2015 at 3:41:42 AM UTC-4, guettli wrote: > > From https://code.djangoproject.com/ticket/25582 > > {{{ > > It is a common question on stackoverflow and other places: > > How to reverse() to url including GET parameters? Example: > .../myview?f

Re: Why passing request, *args, **kwargs in dispatch method for generic views

It looks like setting the request/args/kwargs attributes came after the original CBGV implementation. https://github.com/django/django/commit/ea6b95db https://code.djangoproject.com/ticket/19316 https://groups.google.com/d/topic/django-developers/7c7aI-slGNc/discussion I haven't looked closely

Re: Python 3.5 Support in Django 1.8.x?

Officially Django 1.8 doesn't support Python 3.5. In practice, I think it probably works. See details in https://code.djangoproject.com/ticket/25502 about why the 1.8 test suite doesn't pass with Python 3.5. We could probably change that if there is sufficient interest, however, I'm not aware o

Re: #25582: Add a way to build URLs with query strings

On the ticket, Luke pointed out these libraries: 1) For Python code: urlobject ​​https://github.com/zacharyvoase/urlobject/ and furl ​​https://github.com/gruns/furl 2) For template code: django-spurl - ​​https://github.com/j4mie/django-spurl He doesn't see a need to include a subset of the funct

Re: Django 1.9: default='' no longer permitted on model field (with blank=False)

Maybe it would be enough to ignore ValidationErrors with code='blank' and/or code='null' in the check? That's been the only "false positive" with this check as far as I can tell. On Friday, October 23, 2015 at 8:08:57 PM UTC-4, Russell Keith-Magee wrote: > > On Sat, Oct 24, 2015 at 5:42 AM, Marc

Re: Python 3.5 Support in Django 1.8.x?

), it makes > sense that our LTS will be officially supported. > > Russ %-) > > On Sat, Oct 24, 2015 at 5:57 AM, Marc Tamlyn > wrote: > >> FWIW, I think we should add 3.5 support to 1.8. >> >> On 23 October 2015 at 17:08, Tim Graham >> > wrote:

Re: Django 1.9: default='' no longer permitted on model field (with blank=False)

bout using the checks framework to try to prevent invalid tickets from newbies making mistakes. It's difficult to anticipate the universe of valid use cases, so thanks for testing the prerelease and offering your feedback. On Friday, October 23, 2015 at 8:16:58 PM UTC-4, Tim Graham wrote

Re: Python 3.5 Support in Django 1.8.x?

Here's the PR to remove 50K lines of deprecation warnings when running the Django 1.8 tests on Python 3.5 as well as to fix the two test failures caused by those warnings: https://github.com/django/django/pull/5472 In case you look and wonder about the build failures, Jenkins broke today after

a standard descriptor signature?

Curtis, or should I say FunkyBob, raised the issue here: https://github.com/django/django/pull/5226 Currently we have several different signatures: def __get__(self, instance, instance_type=None) def __get__(self, obj, type=None): def __get__(self, instance, type=None) def __get__(self, obj, obj

Fellow Report - October 24, 2015

On the infrastructure front, I've been working with Shai and Mariusz Felisiak to update the Oracle continuous integration server to Oracle 12. It’s mostly completed and we have some new GIS tests between Oracle 11 and 12 to fix for anyone interested. We’ll likely retire the Oracle 11 machine on

Re: 1.9 Changes to BoundField

The release notes don't mention it because it's a private API until now. Feel free to do nothing as we're unlikely to remove the backwards compatibility alias for a while, at least until versions < 1.9 are unsupported at which point you could update the import to the new location without needin

Should contrib.auth include support for 2fa out of the box?

On Trac [1], Alex says, "Django did a tremendous service to its users by making strong password hashing be the default. The world is pushing forward, and now 2fa is the next standard that many sites fail to meet. Django should include support for 2fa out of the box, ideally with support for b

Re: [Feature] On CommandError, sys.exit(1)

The place you linked to is ignoring CommandError when parsing arguments. I'm not sure under what conditions this happens (if at all) -- the Django tests don't cover it. As far as I know, BaseCommand already does sys.exit(1) when there's an unhandled exception: https://github.com/django/django/

Re: a standard descriptor signature?

; > Now that Curtis did all the investigation work I think it wouldn't hurt >> being consistent here. >> > >> > __get__(self, instance, cls=None) and __set__(self, instance, value) >> look like sane defaults to me. >> > >> > Le samedi 24 octobre

improving our Contributor License Agreement process

In 2014 I started to research if we could offer a Google Summer of Code project aimed at improving Django's process for collecting and organizing CLAs. I didn't complete that proposal when I found some existing solutions, in particular https://cla.puppetlabs.com/ which Puppet labs said they were

Re: Ticket 2273: django.contrib.auth.models.User: username is case-sensitive

I created https://code.djangoproject.com/ticket/25617 - Disallow usernames that differ only in case in UserCreationForm. Please voice any concerns on that ticket. On Monday, October 26, 2015 at 2:24:27 PM UTC-4, Collin Anderson wrote: > > I also agree. And to be clear, we're talking about UserCr

Re: improving our Contributor License Agreement process

Avoiding unnecessary work appeals to me, so I think it would be great to check with the lawyers before proceeding. On Tuesday, October 27, 2015 at 8:33:21 PM UTC-4, Russell Keith-Magee wrote: > > Hi Tim, > > On Wed, Oct 28, 2015 at 12:50 AM, Tim Graham > wrote: > >&

Re: ValueError: Available apps isn't a subset

What command are you using to run the tests? It is possible you have stale pyc files that needed to be deleted? (git clean -fdx). On Thursday, October 29, 2015 at 6:47:09 AM UTC-4, Jose Paul wrote: > > > I am getting following error when I tried to run DJango 1,8 test cases > Please help to unde

Re: language error -- fixed -- please update django source code

Please don't duplicate a Trac ticket on the mailing list. Thanks. On Friday, October 30, 2015 at 5:56:47 AM UTC-4, Edwin Siu wrote: > > #UPDATE: October 30, 2015 Django 1.8, Ubuntu Server 14.04, literati.nyc > #1 note that by the time automatic notifications were immplemented, > #I used crontab to

Re: ValueError: Available apps isn't a subset

__call__ > self._pre_setup() > File "C:\Python27\lib\site-packages\django\test\testcases.py", line 779, > in _pre_setup > apps.set_available_apps(self.available_apps) > File "C:\Python27\lib\site-packages\django\apps\registry.py", line 285, > in set_

Fellow Report - October 31, 2015

On the infrastructure front, I completed pull request integration for the Windows build, so that’s a new status check that runs on all pull requests that also run the tests on Linux. Sorry about the djangoproject.com outage on Monday -- that was due to some unexpected problems during Rackspac

[ANNOUNCE] Django bugfix release issued: 1.8.6

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2015/nov/04/bugfix-release-issued/ -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group an

Fellow Report - November 7, 2015

I didn’t do too much triaging and reviewing this week due to traveling and Django Under the Hood. I started releasing 1.8.6 on a train from Brussels to Amsterdam and uploaded it upon arrival. We had a nice day of sprints today and now I have a plethora of pull requests to review. :-) Triaged

Re: Proposal: add new template tag "age"

For questions of whether or not to include something like this in core, my own rule of thumb is, "Is this difficult to implement as a third-party package? If not, do more than ~80% of sites need this feature?" If the answer to both questions is "no" (which is the case here, in my opinion), then

Support `manage.py shell -c 'run_code_as_django()'`?

Similar to "python -c", there's been a request for: python manage.py shell -c 'run_code_as_django()' to avoid writing simple management commands. What do you think about this idea? https://code.djangoproject.com/ticket/25680 -- You received this message because you are subscribed to the Googl

Re: Oracle GIS update

The changes to get it running were merged in September. Absent a proper solution for those 6 failures, I agree it would be a good idea to mark them expectedFailure so we can get the build running on CI before 1.9 final. On Tuesday, November 10, 2015 at 1:54:42 PM UTC-5, Marc Tamlyn wrote: > > Th

Odd behavior change in 1.8 with {% if %}, RelatedObjectDoesNotExist, and TEMPLATE_STRING_IF_INVALID

I'd appreciate some opinions on whether or not we should treat this issue as a regression: https://code.djangoproject.com/ticket/25600 -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from th

Re: Form field labels change proposal

How do you envision putting this through a deprecation cycle? On Wednesday, November 11, 2015 at 10:59:46 AM UTC-5, Sergei Maertens wrote: > > This is a proposal to change how Django generates form field labels from > model fields. Currently, `capfirst` is called on `field.verbose_name` (see > h

Re: why django 1.9 migrations are essential?

Hi, have you read the 1.9 release notes? Specifically, "When supplying None as a value in MIGRATION_MODULES , Django will consider the app an app without migrations." If so, maybe we need a better description of

Re: Odd behavior change in 1.8 with {% if %}, RelatedObjectDoesNotExist, and TEMPLATE_STRING_IF_INVALID

n how the if tag silences exceptions. On Wednesday, November 11, 2015 at 4:56:03 PM UTC-5, Shai Berger wrote: > > On Tuesday 10 November 2015 21:32:36 Tim Graham wrote: > > I'd appreciate some opinions on whether or not we should treat this > issue > > as a regression: htt

Re: status of 1.9 release blockers

Sorry for the lack of updates, but no news is good news. We're on track for a release candidate on Monday. On Saturday, October 17, 2015 at 7:41:55 PM UTC-4, Tim Graham wrote: > > We're on schedule for Monday's beta release. Most of the backported fixes > have been

Fellow Report - November 14, 2015

Triaged --- https://code.djangoproject.com/ticket/25701 - Add warning to an admin list_view if too many queries are being used (accepted) https://code.djangoproject.com/ticket/25710 - Clarify the docs about what INTERNAL_IPS does (accepted) https://code.djangoproject.com/ticket/25712 -

Re: [Feature Request] Performant values_list query

I don't think there is much database backend specific logic as far as values_list() goes, but if you get something working on SQLite and send a pull request, we can easily run it on all database backends. For performance testing, you might find https://github.com/django/djangobench/ useful. On

[ANNOUNCE] Django 1.9 release candidate 1 released

We're closing in on the final Django 1.9 release, so it's release candidate time! Details are up on the Django project blog: https://www.djangoproject.com/weblog/2015/nov/16/django-19rc1-released/ -- You received this message because you are subscribed to the Google Groups "Django developers

Re: [Feature Request] Performant values_list query

We don't patch the docs for versions of Django older than the latest stable release except in critical cases. For one, this causes problems for the translated versions of the docs because there's no process for updating those older versions. Also, Django 1.7 will be unsupported in a couple week

removing redirect URLs for some really old Django releases

I wonder if anyone objects to removing some non-trivial logic to support old download redirect URLs: https://github.com/django/djangoproject.com/pull/548 This only affects the redirect URLs like /download/%(version)s/tarball/. The files are still accessible at their actual URLs like https://ww

django.utils.version.get_version() discrepancy for Python 2 vs. Python 3

There was a small hiccup with the 1.9 release candidate yesterday. Unless there is some other conflating factor that I missed, generating release packages using Python 2 will yield a name like "Django-1.9c1.tar.gz" while Python 3 yields "Django-1.9rc1.tar.gz" ('rc' instead of 'c'). Yesterday's

Re: django.utils.version.get_version() discrepancy for Python 2 vs. Python 3

Thanks Donald, updating setuptools was the factor I missed, not Python 2 vs. 3. On Tuesday, November 17, 2015 at 5:06:59 PM UTC-5, Donald Stufft wrote: > > > On Nov 17, 2015, at 12:00 PM, Tim Graham > > wrote: > > There was a small hiccup with the 1.9 release candid

<    1   2   3   4   5   6   7   8   9   10   >