Any Windows users who could help setting up Jenkins slaves?

It would be nice to add Windows support to our continuous integration. Do we have anyone with experience setting up Windows slaves for Jenkins who could help with this? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django its

Re: Redirect loop detection in test client is incorrect

Is there any disadvantage to making it some "large" number like 10? In that case it probably wouldn't need to be configurable. The additional time to do 10 loops instead of 2 is probably trivial (and it's an unexpected condition anyway). On Friday, May 1, 2015 at 1:36:32 PM UTC-4, Mounir Messel

Re: Redirect loop detection in test client is incorrect

age, Page2 to Page3 and Page3 to the Page1: N=2 redirects >> to the Page1. >> Do you think 10 times make senses? In my opinion it's too much and the >> need to raise an error to make developers know about something wrong in >> their redirects else they can override it f

[ANNOUNCE] Django bugfix releases issued: 1.8.1 and 1.7.8

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2015/may/01/bugfix-releases-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 a

Re: Idea/request for help: Django Developers Community Survey

n the answer about such an important question shouldnt be reduced to 3 >> little options a handfull people decided on, that wouldnt reflect what >> people really want if they cant choose an real answer. >> >> Am 27.04.2015 02:46, schrieb Tim Graham: >> >> Th

Fellow Report - May 1, 2015

In addition to these tasks, rolled the 1.8.1 and 1.7.8 bug fix releases yesterday. Report for week ending May 1, 2015: Triaged --- https://code.djangoproject.com/ticket/24708 - forms.GenericIPAddressField.to_python behaves differently to other CharField subclasses. (accepted) https:/

Re: Idea/request for help: Django Developers Community Survey

s. On Saturday, May 2, 2015 at 8:27:34 PM UTC-4, Tim Graham wrote: > > I made a few edits based on recent feedback. I'll publicize it via the > djangoproject.com some time next week. > > On Wednesday, April 29, 2015 at 1:59:20 AM UTC-4, Markus Holtermann wrote: >> >>

Re: An easier path to upgrade from one LTS release to another

I think there is some merit to reconsidering the deprecation schedule as Anssi suggests. What I have seen is that most third-party apps didn't consider dropping support for the previous LTS (1.4) until the next LTS (1.8) was released. This meant that all these projects had to implement their ow

Need help running Django's test suite on Oracle 12

We have some instructions to help contributors run the Django test suite on Oracle, however, these instructions are for Oracle 11 and the virtual machine image provided by Oracle now uses Oracle 12c. I've tried to update the instructions, but it seems there are some changes in Oracle 12 related

Re: An easier path to upgrade from one LTS release to another

d in 1.5, could it finally be > removed in 1.9? > > > On Friday, May 8, 2015 at 1:53:59 AM UTC+10, Carl Meyer wrote: >> >> On 05/07/2015 08:53 AM, Tim Graham wrote: >> > I think there is some merit to reconsidering the deprecation schedule >> as >> &

Fellow Report - May 9, 2015

Report for week ending May 9, 2015: Triaged --- https://code.djangoproject.com/ticket/24741 - UnicodeDecodeError in gettext via migrations autodetector (needsinfo) https://code.djangoproject.com/ticket/24740 - AdminSite site title (worksforme) https://code.djangoproject.com/ticket/2474

Re: SSL support for Django-admin runserver‏

Hi Steven, I'm in favor of trying to switch runserver to use gunicorn instead of expanding the functionality of our own homegrown webserver (https://code.djangoproject.com/ticket/21978). Windows support still remains an unsolved issue (https://github.com/benoitc/gunicorn/issues/524), but I don

Re: Migrations in Django 1.7 make unit testing models harder

orward, even having an option to skip migrations is a problem because we'd > need that data to be populated. Is there something planned for this for > Django 1.9? > > On Saturday, December 27, 2014 at 8:10:10 PM UTC+5:30, Tim Graham wrote: >> >> In pull request 3

Re: form validation in contrib.auth

1. I don't see much benefit to adding a max length for one form (AuthenticationForm) to give some sense of security as opposed to properly addressing the issue at the webserver level. As Paul said, "As documented in the deployment docs, it is your responsibility as the deployer to limit post bo

Re: Capturing faked migrations in django_migrations table

I'm curious to know the reason why it would be helpful to know whether or not a migration was faked. When you fake a migration, you are promising that your schema matches the migration, so it seems to me that it would only matter if you made a mistake there. On Wednesday, May 13, 2015 at 12:38:

Can Django assume connect privileges to the 'postgres' database?

Django 1.8 requires a connection to the 'postgres' database in order to resolve ticket #16969 [1]. We've had several reports of cases where connecting to the 'postgres' database isn't permitted (e.g. Heroku and other shared hosting providers) which causes problems when running tests and in some

Fellow Report - May 16, 2015

Report for week ending May 16, 2015: I also tested Django with Python 2.7.10rc1 and found a backwards incompatible change which has been reverted. https://bugs.python.org/issue24134 Triaged --- https://code.djangoproject.com/ticket/24779 - django-1.8.1 fails test with pypy - FAIL: test

[ANNOUNCE] Django security release issued (1.8.2)

Today the Django team issued Django 1.8.2 as part of our security process. This releases address a security issue, and we encourage all users to upgrade as soon as possible. More details can be found on our blog: https://www.djangoproject.com/weblog/2015/may/20/security-release/ As a reminder,

Re: Proposal: Manually login without authenticate

Could you elaborate on what use case you are trying to solve? On Friday, May 22, 2015 at 11:36:21 AM UTC-4, poiati wrote: > > Hello guys, > > I want to discuss the current login workflow in django. As it is we need > to call `authenticate` before `login` because we need to set the > authenticati

Fellow Report - May 23, 2015

Report for week ending May 23, 2015: I also coordinated the 1.8.2 security release which went out this week. Triaged --- https://code.djangoproject.com/ticket/24787 - Cannot assign a ForeignKey field with blank=True and null=False in Model.clean() (accepted) https://code.djangoproject.c

Re: Adding a function to to Django to programmatically delete stale content types

My suggestion wasn't that update_contenttypes() couldn't be modified, but rather that it might be better to expose the desired functionality as a separate utility method to avoid having to explain in the documentation how the interactive and force_remove keywords interact (probably the utility

Re: Why can't templates access properties

Accessing properties in templates should work as far as I know. Maybe there is an error in your application. On Tuesday, May 26, 2015 at 2:27:40 PM UTC-4, Ram Rachum wrote: > > Hi, > > I noticed that when I use variables in Django templates that access object > properties, it doesn't work. (e.g.

Re: URL namespaces

Point 1 sounds like https://code.djangoproject.com/ticket/11642 -- and that ticket says it may be superseded by https://code.djangoproject.com/ticket/21927. Could you review those tickets as well as the others in the "Core (URLs)" component of Trac? It would be good if you could assign yourself

Re: URL namespaces

g app names, and there are easy workarounds that I feel > shouldn't be part of the API itself. The namespace would be specified in > include(), and default to the app_name. > > Op donderdag 28 mei 2015 15:37:20 UTC+2 schreef Tim Graham: >> >> Point 1 sounds like ht

Re: Fellow Report - April 24, 2015

it won't stop the server"(commit > <https://github.com/django/django/commit/0f2e82b9ec9797147945a6f9a402b5ae0fb1d9f4>) > > from the docs. Is this development server change intentional in 1.8? > > On Saturday, April 25, 2015 at 7:09:27 PM UTC-5, Tim Graham wrote: >

Re: Fate of sql* management commands

There's a ticket waiting someone to implement what has been discussed: https://code.djangoproject.com/ticket/24481 On Friday, May 29, 2015 at 12:05:48 PM UTC-4, Marcin Nowak wrote: > > > > On Monday, March 30, 2015 at 1:58:02 AM UTC+2, Russell Keith-Magee wrote: >> >> >>> >>> *What is the new way

Re: Fate of sql* management commands

t; pass >> >> sql.check_for_migrations = check_for_migration_bypassed >> >> (Tested with v1.8) >> >> /BR >> Marcin >> >> On Friday, May 29, 2015 at 6:38:11 PM UTC+2, Tim Graham wrote: >>> >>> There's a ticket waiting someon

Fellow Report - May 30, 2015

Report for week ending May 30, 2015: Triaged --- https://code.djangoproject.com/ticket/24850 - Squashed migration not recognized as an initial migration (duplicate) https://code.djangoproject.com/ticket/24851 - Regression in reverse one-to-one field in list_display (accepted) https://c

Re: Fate of sql* management commands

models. We welcome your contribution if you can form a consensus on a proposal. On Monday, June 1, 2015 at 4:00:14 AM UTC-4, Marcin Nowak wrote: > > > On Sunday, May 31, 2015 at 1:47:32 AM UTC+2, Tim Graham wrote: >> >> They were dropped as part of the removal of the old code that

Re: Django banking packages

You'll get answers to questions like this on the django-users email list, < django-developers@googlegroups.com> - the web interface is < https://groups.google.com/forum/#!forum/django-users>. The list you've posted to is django-developers, which is for the discussion of the development of Django

Re: 1.9 release planning

I put together a draft proposal in the form of a potential djangoproject.com blog post. I've enabled commenting in case you have minor cosmetic comments, but please keep discussion about the content of the proposal itself on this mailing list. Also, please let me know of any additional question

Re: 1.9 release planning

/feature is available in 1.8, the 3rd party app should > be able to use the new feature to stay compatible, right? If anything I'd > like to see us hold off on dropping features deprecated in 1.9 until after > the LTS to help people migrate between LTSs. > > Thanks, > Coll

Re: Introducing django-compat - arteria's solution for for- and backwards compatibility from Django 1.4.x to 1.8.x/1.9.x

When do you drop support for old versions of Django? The main concern I have is that it somewhat encourages running on unsupported and insecure versions of Django (currently 1.5, 1.6; and 1.4 will be end of life in October). Therefore I don't thinking giving it an official blessing is a good id

Re: Read-only overridden field appears twice in the admin

Yes, it looks like a legitimate bug. Please file a Trac ticket. On Wednesday, June 3, 2015 at 8:55:47 AM UTC-4, is_null wrote: > > Hi all, > > I've had this issue reported for the second time in > django-autocomplete-light's tracker. > > For the first time on Jan 16th 2014 by a user whom I thou

Re: More components in Trac for non-technical aspects

I think we should keep Trac focused on tracking bugs. The dsf-members mailing list seems like a natural place to raise these ideas, although that's a more limited audience, so I'd feel free to raise them here unless someone else can suggest a better place. On Thursday, June 4, 2015 at 11:10:25

Re: Provide free, simple, small-scale hosting for new users

PythonAnyware provides free hosting and that's what the Django Girls tutorial uses: http://tutorial.djangogirls.org/en/deploy/README.html I don't think the Django Software Foundation needs to build a service like that. On Thursday, June 4, 2015 at 11:08:01 AM UTC-4, Markus Amalthea Magnuson wr

Re: Provide free, simple, small-scale hosting for new users

financial muscle or human resources to provide such a service. There could >>> be an argument to document possible free hosting platforms, but the django >>> project generally avoids advertising any particular company (or third party >>> package for that matter).

Fellow Report - June 6, 2015

It was a busy week, especially with the DjangoCon Europe sprints. Thanks to all participants! Look forward to reviewing the new backlog of pull requests. Report for week ending June 6, 2015: Triaged --- https://code.djangoproject.com/ticket/24885 - Writing your first Django app, part

Re: 1.9 release planning

t; next > LTS (e.g. upgrade 1.8->1.9->2.0), then upgrade your dependencies to the > newer version that supports both 2.0 and 2.1, and then finally upgrade > to 2.1." part. > > Thanks, > Collin > > On Monday, June 1, 2015 at 11:02:01 AM UTC-4, Tim Graham wrote: &g

Re: Introducing django-compat - arteria's solution for for- and backwards compatibility from Django 1.4.x to 1.8.x/1.9.x

, we are > interested in work from LTS to LTS. For our open source apps we want to > support what's supported officially to not exclude others. That's why we > started this thing. > > I'd really welcome the bi-yearly LTS release cycle with one year of LTS > su

Re: Django Admin - ModelAdmin exclude

I agree with Marc that so many ways to do things isn't ideal, but I don't see a different simple way to accommodate Peter's use case, so +0 to adding get_exclude(). On Saturday, June 6, 2015 at 11:44:53 AM UTC-4, Peter J. Farrell wrote: > > In our case, we need to dynamically include additional

Re: Form assets and static file storage

The problem has come up before: https://code.djangoproject.com/ticket/18455 but there is some question about whether the design of the Media class is something we should try to continue building on: https://code.djangoproject.com/ticket/22298 The suggestion to have the built-in static tag work l

Re: Minor Feature Request: Unconfigured Allowed_Hosts Setting Should Raise ImproperlyConfigured Error

We added such a check in runserver [1]. For other servers it seems less clear to me where that check would go -- in the WSGI handler? In django.setup()? (obviously, there is no need for ALLOWED_HOSTS if you are using Django outside a webserver context, so the check could be annoying if it's the

Re: 1.9 release planning

Collin, I'm not following your reasoning about why dropping features deprecated in one LTS (e.g. 1.8) in the next LTS (e.g. 2.1; I think you made a typo in your timeline putting it next to 2.0?) will make it possible to easily support both LTS releases? That's the purpose of Loic's proposal I b

how to deal with inspect.getargspec() deprecation?

inspect.getargspec() was deprecated in Python 3.0 and will be removed in 3.6 (ETA late 2016). It started throwing a deprecation warning in Python 3.5 which causes some test failures when we check the number of deprecation warnings so I'd like to deal with it now and avoid introducing more usages

Re: Minor Feature Request: Unconfigured Allowed_Hosts Setting Should Raise ImproperlyConfigured Error

I forgot about the existing settings checks in django.conf__init__.py. That seems like a reasonable place. Robert do you want to try to write a patch and/or open a ticket? On Wednesday, June 10, 2015 at 2:38:31 PM UTC-4, Carl Meyer wrote: > > On 06/10/2015 11:55 AM, Tim Graham wrote:

Re: 1.9 release planning

uot; I am not worried about supported deprecated APIs > in old releases, only how long they stay around in master as that could be > a barrier to innovation. > Right, so the cost would be an extra 8 months before removing features > deprecated in 1.9 from master. > > Thanks, > C

Re: how to deal with inspect.getargspec() deprecation?

M, Berker Peksağ wrote: > > On Wed, Jun 10, 2015 at 9:49 PM, Tim Graham > wrote: > >> inspect.getargspec() was deprecated in Python 3.0 and will be removed > in 3.6 > >> (ETA late 2016). It started throwing a deprecation warning in Python > 3.5 > >> w

Re: URL namespaces

About #24127, I'd like if you could investigate if making the backwards incompatible change breaks any tests in Django's test suite. That would offer a starting point to think about the ramifications. Wouldn't the fix for broken user code be to set "request.current_app = None" where necessary?

Re: App config on the default template for app creation

Aymeric, did you consider it? It seems reasonable to me. On Friday, June 5, 2015 at 9:35:37 AM UTC-4, Mounir Messelmeni wrote: > > Will it be better to add apps.py and app_config on the __init__.py file > when we run ./manage.py startapp? > I think this way users will know more about this feature

Re: Feature: URL template tag, optional parameters

I think you'll have to try implementing it to see if it's feasible. On Thursday, June 4, 2015 at 5:44:54 AM UTC-4, erez@gmail.com wrote: > > Hi, > > AFAIK, the recommended way in Django to handle multiple urls with the same > view, is to have optional parameters. ( > https://docs.djangoproje

Re: Introducing django-compat - arteria's solution for for- and backwards compatibility from Django 1.4.x to 1.8.x/1.9.x

ber, 25% in this case, that > matters. It depends who starts with the latest greatest version and who use > the LTS. I think agencies with a lot of customer and big, complex projects > will/tend to build on a LTS version. These numbers depends totally who > answers the survey. >

Re: App config on the default template for app creation

Thanks, I added a ticket: https://code.djangoproject.com/ticket/24971 On Thursday, June 11, 2015 at 4:52:46 PM UTC-4, Aymeric Augustin wrote: > > > On 11 juin 2015, at 21:04, Tim Graham > > wrote: > > > > Aymeric, did you consider it? > > No, I didn’t.

Re: MigrationTestCase

Sure... what do you think of the API that Tom proposed? Did you have something different in mind? On Friday, June 12, 2015 at 10:23:57 AM UTC-4, Sean Briceland wrote: > > I believe Tom is referring to testing their migration files in order to > ensure DB is migrated accordingly. > > For example,

Re: 1.9 release planning

I'm still in favor of "Collin's proposal." You'll need to convince me that keeping deprecations around longer is worth having somewhat meaningful version numbers, but I'm not sure I really consider dropping deprecation shims as "incompatible API changes" that justify a major version bump. For e

Re: 1.9 release planning

gt; Features deprecated in a LTS leak onto x.1 releases but that's fine (1 > release deprecations are a no-go IMO), we can document it as "deprecations > from a major branch will be either loud or gone in the following major > branch". > > -- > Loïc >

Re: how to deal with inspect.getargspec() deprecation?

ering that dropping Python 2 in master is < 2 years out. https://github.com/django/django/pull/4846 On Wednesday, June 10, 2015 at 5:45:30 PM UTC-4, Tim Graham wrote: > > The APIs are rather different. I will keep working on the conversions > (we'll need them no matter which op

Re: 1.9 release planning

ore visibility to our efforts to ease straddle two > LTS versions (supporting shims from LTS+1 for 1 additional release). I > think it's enough to justify adopting it even if we aren't "pure" in its > implementation. > > -- > Loïc > > > On Jun 13, 2

how long to support Python 3.3?

Django 1.8 was the last version to support Python 3.2, which has its security updates end February 2016. That means Python 3.2 users can continue getting Django security updates for about 2 years after Python security updates end. I am wondering if we should instead try to better align the end

Re: 1.9 release planning

Of course RemovedInDjango19Warning is also in 1.7 and a lot of docs reference Django 1.9. I'm not enthusiastic about updating all that. On Sunday, June 14, 2015 at 1:43:50 AM UTC+2, Loïc Bistuer wrote: > > > > On Jun 13, 2015, at 20:43, Tim Graham > > wrote: > &g

Re: Tips on adding a Couchbase backend

There's nothing in the way of official documentation about writing third-party database backends. I guess the best approach would be to look through the source code of database engines in Django as well as the projects you mentioned and learn from that. If we can add any hooks to Django to help

Fellow Report - June 13, 2015

In non-code work, the discussions about the future release schedule continue in the "1.9 release planning" thread. I hope we can finalize that within the next week or so. Report for week ending June 13, 2015: Triaged --- https://code.djangoproject.com/ticket/24948 - BMP Image File trea

Re: how long to support Python 3.3?

o looks like 3.x usage has more than doubled over the last year. :) > > On Saturday, June 13, 2015 at 7:00:55 PM UTC-4, Tim Graham wrote: >> >> Django 1.8 was the last version to support Python 3.2, which has its >> security updates end February 2016. That means Python

Re: 1.9 release planning

The Google doc has been evolving: https://docs.google.com/document/d/1bC6A8qc4skCmlagOnp8U7ddgyC-1XxXCBTlgrW690i0/edit?usp=sharing On Monday, June 15, 2015 at 3:37:16 PM UTC-4, Aymeric Augustin wrote: > > Le 15 juin 2015 à 15:54, Loïc Bistuer > > a écrit : > > > > I'm -0 (borderline -1) on tha

Re: Minor feature request: log adding a custom permission to the database when migrating

It already exists, you just need to specify a higher verbosity level like so: manage.py migrate -v 2 On Tuesday, June 16, 2015 at 8:27:14 AM UTC-4, Mikael H wrote: > > Hi > > I am new to this group so I hope I use the right channels for this request. > > When I add a custom permission to a model

Re: Custom Model field, to_python() / from_db_value() and unittests...

The doc about how to ignore warnings in tests is here: https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/submitting-patches/#deprecating-a-feature Alternatively, you can temporarily remove these lines in runtests.py: warnings.simplefilter("error", RemovedInDjango20Warning

Re: does django-admin need a man page?

r of built in commands (e.g. > http://south.readthedocs.org/en/latest/commands.html#syncdb ). > > So, the man page is doomed to be both incomplete and possibly incorrect. > Surely it makes more sense for a man page to just point to the "--help" tag > and official docs onli

Re: Misleading Documentation on Model Field Reference

Feel free to propose a ticket and pull request. I don't think this needs much discussion on the mailing list. Thanks! On Saturday, June 20, 2015 at 9:19:47 AM UTC-4, Christian Schmitt wrote: > > Hello, I read carefully through out the Django Docs and found one comment > really misleading ( > htt

Fellow Report - June 20, 2015

Report for week ending June 20, 2015: Triaged --- https://code.djangoproject.com/ticket/24985 - Provide a way to sanitize invalid characters from Rss201rev2Feed (accepted) https://github.com/django/djangoproject.com/issues/492 - SelectDateWidget(empty_label) is not working (invalid) ht

Re: 1.9 release planning

It's okay with me. I don't think RemovedInDjango18Warning is much of a public API, but we can mention it's renaming in the minor release notes just in case. On Monday, June 22, 2015 at 10:33:47 AM UTC-4, Loïc Bistuer wrote: > > Just when we thought we had a winner... I'd like to make a final pro

Re: 1.9 release planning

Done that in https://github.com/django/django/pull/4908 On Monday, June 22, 2015 at 1:35:19 PM UTC-4, Loïc Bistuer wrote: > > We can just leave RemovedInDjango20Warning as an alias (not a subclass) to > PendingDeprecationWarning in 1.8. As long as we don't refer to it in the > rest of the codeba

Re: can't receive IPN in the production with Django-paypal

You'll get answers to questions like this on the django-users email list, < django-us...@googlegroups.com> - the web interface is < https://groups.google.com/forum/#!forum/django-users>. The list you've posted to is django-developers, which is for the discussion of the development of Django itsel

Re: CommonMiddleware DISALLOWED_USER_AGENTS logic

I don't think there's an "architecture rule" that would prevent that design. It looks like DISALLOWED_USER_AGENTS has been around since 2005, but handler403 wasn't added until 1.4. Since the docs for the setting say "Use this for bad robots/crawlers." I guess it's implied that customizing the r

Re: Mongo related issue in Django

It's difficult to tell what the issue is without seeing all you code, but "is this is a bug?" questions are more suited for the django-users mailing list. A good first step in testing your "fix" is to see if Django's test suite passes afterwards. I suspect you'll see some test failures with the

Re: Mongo related issue in Django

Sorry, but that doesn't help as I have no experience with mongoengine. As I said, if you want further help, you might find it on the django-users mailing list but I would check mongoengine support for Django. It's not so clear they are working on it now. https://github.com/MongoEngine/mongoeng

Re: 1.9 release planning

Thanks to everyone for feedback! The technical board has signed off on these changes. Here are the results: https://www.djangoproject.com/weblog/2015/jun/25/roadmap/ - Django’s Roadmap https://github.com/django/django/pull/4897 - Updated release process for new release schedule. https://github

Re: Developer Community survey - results?

Yes, we can share the results now. I just scrubbed the email addresses first. Some nice charts automatically generated by Google forms: https://docs.google.com/forms/d/1Owv-Y_beohyCm9o2xPamdBnvjreNYoWai3rDloKZxWw/viewanalytics The raw results: https://docs.google.com/spreadsheets/d/1dhrdfLDGGk

Fellow Report - June 27, 2015

Report for week ending June 27, 2015: It was good to finish up the release schedule planning this week. The results of that are listed in the “Authored” section below. Thanks again to everyone who helped craft the plan. One notable merge this week was JavaScript linting from Trey Hunner (see

Re: Adding new model. ContentType error with field "name"

Hi, Please don't cross post to django-users and django-developers. This mailing list is for the development of Django itself. I'll answer your question on django-users. Thanks! On Monday, June 29, 2015 at 5:05:41 AM UTC-4, ClosiusBeg wrote: > > Hi All! > > I caught a error when I move from Dajng

[ANNOUNCE] Django Security advisory: simple_tag does not do auto-escaping

The Django team has just published a short security advisory about usage of the simple_tag template tag helper. You should audit your own code. https://www.djangoproject.com/weblog/2015/jun/29/simple_tag-security-advisory/ -- You received this message because you are subscribed to the Google Gr

naming of a new test client method for logging in

There's a proposal [1] to add a new method to the test client that works like login(), but skips the authentication (no credentials need to be provided) and verification (is_active=False can login) steps. The signature is (user, backend=None). What would you name this method? Proposals so far:

Re: naming of a new test client method for logging in

Okay, it seems I'm in the minority with my preference for login_user(). I've committed the patch with force_login(). Thanks for the feedback. On Tuesday, June 30, 2015 at 4:34:11 PM UTC-4, Berker Peksag wrote: > > On Tue, Jun 30, 2015 at 4:38 PM, Tim Graham > wrote: > &

Re: Inheritance in admin classes

Could it be https://code.djangoproject.com/ticket/22828 ? On Wednesday, July 1, 2015 at 5:32:48 PM UTC-4, kny...@knyg.ht wrote: > > Hello all, > > So, I was talking to kezabelle on IRC some months back about a problem I > was having, and finally remembered to post something. > > If I inherit from

should we close in-memory file-like objects (StringIO, BytesIO, etc.)?

Andriy proposed a patch to close objects like StringIO and BytesIO in our test suite [1]. I am not sure how much benefit this gives (frees "a few bytes of RAM" according to [2]) and it seems to add a lot of verbosity. Looking at Python's own test suite, it doesn't appear these objects are close

Fellow Report - July 4, 2015

Report for week ending July 4, 2015: Highlight of this week was merging the rest of DEP 3, the JavaScript unit tests. The integration with Jenkins is also completed. Thanks Trey Hunner and everyone else who contributed to the effort. Triaged --- https://code.djangoproject.com/ticket/250

Re: should we close in-memory file-like objects (StringIO, BytesIO, etc.)?

Thanks for the info and feedback. We'll omit these changes for StringIO and Bytes IO then. On Saturday, July 4, 2015 at 8:52:52 AM UTC-4, Ned Batchelder wrote: > > On 7/3/15 1:55 PM, Aymeric Augustin wrote: > > 2015-07-03 17:10 GMT+02:00 Berker Peksağ >: > >> I agree with you on the StringIO

Re: And again about permission to view

admin. > > I wrote the ticket <https://code.djangoproject.com/ticket/25057>, and Tim > Graham forwarded me to this mailing list. > > I want to say only that unavailability this permission not only brings > inconvenience in the development of complex projects. But it is > disappointing whe

[ANNOUNCE] Django security releases issued (1.4.21, 1.7.9, and 1.8.3)

Today the Django team issued multiple releases -- Django 1.4.21, 1.7.9, and 1.8.3 -- as part of our security process. These releases address a couple security issues, and we encourage all users to upgrade as soon as possible. More details can be found on our blog: https://www.djangoproject.com/

Re: And again about permission to view

Historically there's been pushback against adding new settings. That said, I don't see an alternative here besides perhaps an AppConfig attribute (last discussed in https://groups.google.com/d/topic/django-developers/qnnCLppwA3o/discussion). Perhaps we should try to move the existing auth setti

metaclass expertise needed on migrations bug

To someone with experience with metaclasses, A high-level overview of this ticket/pull request would be appreciated: https://code.djangoproject.com/ticket/25068 https://github.com/django/django/pull/4968 -- You received this message because you are subscribed to the Google Groups "Django devel

Re: URL dispatcher API

Marten, did you consider putting the new API in `django.urls` instead of `django.core.urls`? I don't need there's a need to namespace it under "core", but others might be able to confirm the philosophy behind this. On Thursday, July 9, 2015 at 7:19:11 AM UTC-4, James Addison wrote: > > Marten, >

Fellow Report - July 11, 2015

Report for week ending July 11, 2015: Triaged --- https://code.djangoproject.com/ticket/25065 - Should EmailField empty_strings_allowed be False (invalid) https://code.djangoproject.com/ticket/25067 - Allowing all characters when parsing inclusion templatetags (duplicate) https://code.

Re: A method for overriding default raw_id_fields behavior

Yes, there's an open ticket for that: https://code.djangoproject.com/ticket/17881 On Sunday, July 12, 2015 at 2:18:24 PM UTC-4, damon c wrote: > > The default behavior for the modelAdmin is to render a element > containing *every* instance of the model referred to by the FK. > > When this fie

Re: Proposal: deprecate and remove egg template loader

Created ticket: https://code.djangoproject.com/ticket/25120#ticket On Monday, July 13, 2015 at 11:01:08 AM UTC-4, Donald Stufft wrote: > > I’m fine with this, but just be warned that it does mean anything > that ships a Django app will need a zip_unsafe=True or else they > no longer support bein

Re: Support for UNLOGGED tables in PostgreSQL

I see a thirty second increase in the test suite (from 7.5 minutes to 8 minutes) on my local machine with: sql_create_table = "CREATE UNLOGGED TABLE %(table)s (%(definition)s)" On Tuesday, July 14, 2015 at 4:20:45 AM UTC-4, Federico Capoano wrote: > > That's also a viable alternative, although i

ForeignObject defaults to virtual_only=False?

ForeignObject defaults to virtual_only=False [1]. This seems counterintuitive as my understanding is that ForeignObject fields are virtual (i.e. they don't directly map to a database column). I am testing Andrew's patch to allow disabling migrations in tests [2] and ran into a problem in Django

Re: Why Django is making migrations for external apps?

Andrew, do you think having the autodetector not "resolve" settings to their values and instead include that as references in auto-generated migrations is something we should try to implement? If so, let's suggest that solution on https://code.djangoproject.com/ticket/24648 On Wednesday, July

Major features for 1.9

Currently we have two items on the roadmap: https://code.djangoproject.com/wiki/Version1.9Roadmap PostgreSQL Full Text Search (Marc Tamlyn) Custom indexes (Marc Tamlyn) Hopefully we can add Marten's URLs GSoC p

Fellow Report - July 18, 2015

Report for week ending July 18, 2015: Triaged --- https://code.djangoproject.com/ticket/25090 - Output of password_validators_help_text_html() is not marked safe (won’t fix) https://code.djangoproject.com/ticket/25118 - add template filter doesn't work with mixed types (accepted) https

Simplifying MANIFEST.in

Lately we've had some packaging problems due to mistakes in MANIFEST.in, mostly due to missing files in the source distribution because we forgot to update MANIFEST.in for new or moved files. Currently it looks like this: include README.rst include AUTHORS include INSTALL include LICENSE include

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