Re: revisiting the Python version support policy

Can you explain more about what they struggled with? Maybe there's other ways to solve those problems. On Friday, January 25, 2019 at 9:43:37 AM UTC-5, Tom Forbes wrote: > > This message really resonated with me, especially after helping a few > beginners get started with Python and watching the

Re: Fellow Reports - January 2019

Week ending January 26, 2019 Triaged --- https://code.djangoproject.com/ticket/30127 - Deprecate cached_property's name argument (created) Authored -- https://github.com/django/django-formtools/pull/136 - Add testing for Django 2.2 https://github.com/brutasse/django-push/pull

Re: Plot cordinate on google map as like as snap road

This mailing list is for the development of Django itself, not for support using Django. Please use the django-users mailing list for that, or IRC #django on freenode, or a site like Stack Overflow. However, given your question doesn't seem Django related, you probably don't want to ask in a Dj

Re: Google Summer of Code 2019

we can add > functionality for heroku ,docker etc > > On Wednesday, January 16, 2019 at 8:03:55 PM UTC+5:30, Tim Graham wrote: >> >> Org applications for Google's Summer of Code are now open (deadline >> February 6). Do you think the Django Software Foundation should

Re: Fellow Reports - January 2019

Week ending February 2, 2019 Triaged --- https://code.djangoproject.com/ticket/30146 - Move change form fieldset toggle to the right side (wontfix) https://code.djangoproject.com/ticket/30150 - Django 1.11 with MySQL 8: "Unknown system variable 'TX_ISOLATION'" (wontfix) https://code.dj

Re: Google Summer of Code 2019

All answers are at https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info On Monday, February 4, 2019 at 4:19:06 AM UTC-5, Carlton Gibson wrote: > > Hey Tim. > > > For each year your organization has participated, provide the counts of > successful and total stud

Re: Google Summer of Code 2019

o/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info > > Il giorno lun 4 feb 2019 alle ore 13:05 Tim Graham > ha scritto: > >> All answers are at >> https://github.com/django/django-team-wiki/wiki/Google-Summer-of-Code-Application-Info >> > -- You receiv

Re: django logging - `ServerFormatter.uses_server_time()` forces users to use `{` logging style

I'm not opposed to a patch to address your use case. On Thursday, February 7, 2019 at 6:34:23 AM UTC-5, Łukasz Skarżyński wrote: > > Hello, > > I encountered some troubles with django logging configuration during the > update from Django 1.11 to 2.1. This issue was related to this commit >

Fellow Reports - February 2019

Week ending February 9, 2019 Triaged --- https://code.djangoproject.com/ticket/30167 - Allow Child Templates To Inherit Loaded Tags From Parent (duplicate) https://code.djangoproject.com/ticket/30168 - Change date, time and datetime inputs from text type (duplicate) Authored -

Re: Fellow Reports - February 2019

Week ending February 16, 2019 Reviewed/committed -- https://github.com/django/django/pull/10875 - Refs #15902 -- Deprecated storing current language in the session. https://github.com/django/django/pull/10877 - Fixed #22423 - Added support for MySQL operators on real geometr

Re: Fellow Reports - February 2019

Week ending February 23, 2019 I took a break for most of this week. Reviewed/committed -- https://github.com/django/django/pull/10995 - Refs #19544 -- Ignored auto-created through additions conflicts if supported. https://github.com/django/django/pull/10999 - Fixed #30141 --

Re: Fellow Reports - February 2019

Week ending March 2, 2019 Triaged --- https://code.djangoproject.com/ticket/30214 - Indexes defined on abstract base classes are not propagated to subclasses (invalid) https://code.djangoproject.com/ticket/30228 - DeleteModel migration's name argument is supposed to be lowercase (needsi

Re: GSoC 2019 Update

I agree that a cross-database JSONField probably wouldn't take 3 months to implement -- but it would be up to the student to write a proposal and timeline that demonstrates there's 12 weeks of work. Students are supposed to be working full time. GSoC requires writing code so an acceptable proje

Fellow Reports - March 2019

Week ending March 9, 2019 Triaged --- https://code.djangoproject.com/ticket/30232 - Correct expected format in invalid DurationField error message (fixed) https://code.djangoproject.com/ticket/30231 - Field's verbose_name is ignored in FilteredSelectMultiple widget for inlines created w

Re: Support for unittest -k option

-kdb could be a suitable short option. On Monday, March 11, 2019 at 9:20:37 AM UTC-4, Tobias McNulty wrote: > > Agreed it's probably better to make the switch now, and I'd be fine > without a replacement shorthand alternative for --keepdb. > > Cheers, > > > *Tobias McNulty*Chief Executive Officer

Re: Proposal to re-open #27017 (updating only dirty fields in save())

t;> >> Hi! >> >> This is my first post on this list. I recently left a comment on #27017 >> <https://code.djangoproject.com/ticket/27017#comment:3> requesting to >> re-open the topic of only saving dirty fields in save(). Tim Graham >> helpfully

Re: Fellow Reports - March 2019

Week ending March 16, 2019 Triaged --- https://code.djangoproject.com/ticket/30255 - docutils reports an error rendering view docstring when the first line is not empty (accepted) Reviewed/committed -- https://github.com/django/django/pull/11075 - Fixed #30161 -- Added

Re: Newcomer's questions

On Sunday, March 17, 2019 at 9:43:29 PM UTC-4, Alexey Tsivunin wrote: > > I'm working on issue #29471. This issue have version 2.0. Do I need to add > version indicator in that case? > > No, the "Version" flag on the ticket merely indicates when the ticket was reported. > if you're fixing a T

Re: GSoC Proposal

Your proposal should be quite a bit more detailed. See https://gist.github.com/chrismedrela/82cbda8d2a78a280a129 for a past example. I'm not sure if it'll be feasible to write a successful application without having some experience contributing to Django -- I think most if not all past students

Re: Fellow Reports - March 2019

Week ending March 23, 2019 Triaged --- https://code.djangoproject.com/ticket/30270 - .all() for related manager always returns empty list (invalid) https://code.djangoproject.com/ticket/30277 - Django Advanced Tutorial Link doesn't lead to the intended page (fixed) https://code.djangop

Re: Fellow Reports - March 2019

Week ending March 30, 2019 Triaged --- https://code.djangoproject.com/ticket/30288 - PostgreSQL connections forced into UTC if setting.USE_TZ is True (duplicate) Authored -- https://github.com/django/django/pull/11147 - Fixed #30301 -- Removed OutputWrapper.__init__()'s style_

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

MariaDB is supported (see https://code.djangoproject.com/ticket/29548). The test failures are (as the error message says) because you haven't installed the timezone definitions. On Sunday, April 7, 2019 at 3:03:14 AM UTC-4, Asif Saif Uddin wrote: > > You can open a work in progress pr to fix the

Re: Proposal to format Django using black

I'm sorry for establishing some (foolish?) guidelines that discouraged some people from contributing. I didn't establish those guidelines merely to be pedantic, but perhaps I'm too much of a perfectionist at times. After GitHub allowed mergers to amend pull requests, I often made cosmetic adjus

Re: Ideas for a new DEP on long-term Django API compatibility

Pascal, you can read about the reason for the action actions change on the ticket https://code.djangoproject.com/ticket/29917 ...and on this mailing list... https://groups.google.com/d/topic/django-developers/-OWoYL_zryM/discussion. I hesitate to link to things like that in the release notes be

Re: Make Development More Accessible

uot; > trope, when that's not meant as a compliment. > > I think it couldn't be further from the truth. > > Yes, these ain't the wild west days of yore. (Granted) > > But Django has successfully transitioned (with large thanks to the effort > Tim Graham

Re: Removing old branches from the Django Git repository.

Same proposal from 2016: https://groups.google.com/d/topic/django-developers/sf2adeIAkQA/discussion On Thursday, October 10, 2019 at 4:09:24 PM UTC-4, Tom Forbes wrote: > > I second this, there are a few other branches in that list (successful or > not) that have historic value to Django. Is the

Re: URL dispatching framework: feedback requested

It looks to me like the rationale for the existing organization is that everything in that module is designed to be used in a URLconf. Do you propose to make everything importable from "django.urls" or from "django.urls.conf" or some other organization? If we remove urls from django.conf, then

Re: Docs and search : Split the results by category

A similar thing was proposed in another thread: https://groups.google.com/d/msg/django-developers/QW06ctKbFKA/Yg-zE3RSEQAJ I don't disagree that the search could be better, so feel free to prototype something to get feedback. On Monday, January 4, 2016 at 10:25:54 AM UTC-5, Joachim Jablon wrote

Re: Extending JSONField serialization

This came up in a ticket a couple days ago: https://code.djangoproject.com/ticket/25995 On Tuesday, January 5, 2016 at 11:18:01 AM UTC-5, Aymeric Augustin wrote: > > Hello, > > I’m using the JSONField provided by django.contrib.postgres for logging > arbitrary data to PostgreSQL. > > For this

Re: got glossarium?

I agree the glossary is abandoned and I propose removing it. I don't know that there's much value in expanding it. The idea is that you can use :term:`model` and have "model" linked to the glossary definition. In my opinion, the Django docs are comprehensible without this. A better solution in

Re: 1.8 shipping invalid .py files in the startapp template

The current pull request proposes to make a backwards-incompatible change by chopping off any ".tpl" suffix in app or project template files. i.e. "If you are using custom templates and these templates already use a ``.tpl`` suffix, you will need to append an additional ``.tpl`` (ie. ``filenam

Re: Vote on Jira as bugtracker

To search Trac, use "site:code.djangoproject.com your query" in a Google search box. Works great in my experience. On Wednesday, January 6, 2016 at 6:42:44 PM UTC-5, Josh Smeaton wrote: > > FWIW I actually like Jira (much more than Trac) and find it a lot easier > to use. I think the trick is co

Re: slow migrations

As far as I know, no one is actively working on this area at the moment. There is at least one open issue: https://code.djangoproject.com/ticket/22608 You can look through all open migrations tickets too: https://code.djangoproject.com/query?status=assigned&status=new&component=Migrations&stage=A

Fellow Report - January 9, 2016

Triaged --- https://code.djangoproject.com/ticket/26024 - ConditionalGetMiddleware's ETag is broken (accepted) https://code.djangoproject.com/ticket/26028 - Improve instructions for overloading Django templates (accepted) https://code.djangoproject.com/ticket/26030 - Password change, no

Re: re-thinking middleware

That warning sounds like a good idea. We have a similar warning if both the old and new style template settings are defined: https://github.com/django/django/commit/24620d71f2116da31abe6c9391f7bc807ac23c0b On Sunday, January 10, 2016 at 6:57:09 PM UTC-5, Raphaël Barrois wrote: > > On Fri, 8 Jan 2

Re: 1.8 shipping invalid .py files in the startapp template

Seems reasonable to me. On Monday, January 11, 2016 at 10:24:18 AM UTC-5, Carl Johnson wrote: > > I think the template files should be shipped out as .py-tpl, since that's > their type (a Python template), and the resulting final files should just > have the extension renamed. Having two extensi

Fellow Report - January 16, 2015

Triaged --- https://code.djangoproject.com/ticket/26069 - Docs for MyModel._meta.get_fields_with_model() missing info about 'is_relation' (accepted) https://code.djangoproject.com/ticket/26066 - Admin changelist could handle a table wider than the screen more elegantly (accepted) https

deprecate CommaSeparatedIntegerField?

A proposal has been raised to change the validation for CommaSeparatedIntegerField to allow negative numbers [1]. This is obviously backwards-incompatible, so I don't think it'll fly without some option to control the behavior, however, I wanted to ask if there's any reason not to deprecate the

does anyone use contrib.auth's "test models"? (CustomUser and ExtensionUser)

As Simon noted in a ticket [1], "Since the introduction of contrib application migrations in 1.8 (#22170 ) the ​documented custom user test models ta

Re: Team of 7 students will be contributing to Django for a school project. What's the best way to work on features without stepping on toes?

Hi Jason, That sounds exciting. Feel free to ping me (timograham) in #django-dev IRC to discuss. I'd highly advise to send pull requests as you work so you can learn our contribution process, coding guidelines, etc. Also, I won't feel so overwhelmed with a big influx of pull requests to review

Re: Query on BooleanField with values other than True and False, bug or intentional?

It doesn't seem to me that changing the behavior at this point is worth possible backwards incompatibilities. On Friday, January 22, 2016 at 2:51:41 PM UTC-5, Kaveh wrote: > > Today I discovered I can use strings and numbers to query on BooleanFields. > > Let's say we have the following model: >

Re: SchemaEditor: Alter Default requires column definition

What sort of comments are you looking for? On Sunday, January 17, 2016 at 12:47:00 PM UTC-5, Max Bothe wrote: > > Hi all, > > Some databases (like SAP HANA) don't support adding or removing a default > value of a column without redefining the column [1]. > In order to support custom backends for

Re: [Review Request] Added support for database delegated fields (like AutoField)

It would be helpful if you could sketch out the proposal a bit more -- maybe write some documentation that explains and motivates the feature (and put explanation in this thread). The pull request description has some explanation but it doesn't seem suited toward someone unfamiliar with the bac

Re: ModelAdmin API (formfield_for_*)

For a quick glance, the high-level idea looks okay (subject to a deprecation path, of course), however, in my mind it would be more useful to try to move toward enhancing the forms library itself (if possible) so that less admin-specific code is needed. Have you thought about this at all? On Sa

Fellow Report - January 23, 2016

Triaged --- https://code.djangoproject.com/ticket/26096 - Django 1.9.1 fails to delete an existing test database on PostgreSQL and MySQL (fixed) https://code.djangoproject.com/ticket/26097 - UserCreationForm isn't using password_validators_help_text_html (accepted) https://code.djangopr

Re: Deprecate choices argument in Select.render

Please see https://code.djangoproject.com/ticket/25731 for some discussion. Feel free to offer a patch so we can assess if it's feasible. On Sunday, January 24, 2016 at 2:57:04 PM UTC-5, is_null wrote: > > Hi all, > > In Select widgets, as well as many other (including MultipleHiddenInput, > whe

Re: test --keepdb and explicitly migrating the test database

I've made similar mistakes (corrupting the test database) while working on djangoproject.com. For that project, test database creation is quick enough that I just drop "--keepdb" and start fresh. I think this will usually be the simplest option for most users, but I don't see a reason not to sup

Re: add prefered/default protocol in the sites framework #26079

I believe it's a common use case to import a copy of a production database and examine it locally -- that's what I meant about portability. I'm not aware of any Django usage that involves serving protocols other than http(s). Is this a case you've come across? On Monday, January 25, 2016 at 4:3

Re: 'noescape' filter for django template

Is there some reason you cannot mark the string safe in Python code using one of the following methods? I think that's where escaping logic belongs. https://docs.djangoproject.com/en/stable/ref/utils/#django.utils.html.format_html https://docs.djangoproject.com/en/stable/ref/utils/#django.utils.s

Re: add prefered/default protocol in the sites framework #26079

arts in development settings. Not sure if it'd be palatable to deprecation the models though. I don't think maintaining both versions would be worthwhile in the long run. On Monday, January 25, 2016 at 9:57:39 AM UTC-5, Aymeric Augustin wrote: > > On 25 janv. 2016, at 14:19, Tim

Re: two levels of m2m relationship & update values

Please write to django-users as this mailing list is for the development of Django itself. On Monday, January 25, 2016 at 6:07:41 PM UTC-5, Slomski wrote: > > Hi, > > I am trying to create a django app as follow: > > a Block with unique name can have few Flats. Flat name in each Block is > uniqu

Re: Module Index

Feel free to file a ticket and/or submit a patch. On Tuesday, January 26, 2016 at 6:05:55 AM UTC-5, Doug Epling wrote: > > shouldn't this be here: > https://docs.djangoproject.com/en/1.9/py-modindex/#t > -- You received this message because you are subscribed to the Google Groups "Django dev

Re: deadlock risk from using cache a load time

Oops, here's the pull request: https://github.com/django/django/pull/6044 WIth the fix reverted and the missing django.setup() call, the exception is "django.core.exceptions.AppRegistryNotReady: Models aren't loaded yet.". I don't think we need a different exception in model_unpickle(), but mayb

Re: deadlock risk from using cache a load time

m non-Django code is no longer possible? On Tuesday, January 26, 2016 at 2:13:21 PM UTC-5, Aymeric Augustin wrote: > > On 26 janv. 2016, at 14:40, Tim Graham > > wrote: > > > Something like "Models aren't loaded yet. Are you missing django.setup() > in a sta

Re: [#26151] Refactor MigrationWriter.serialize() to use a factory pattern

I doubt that serialization support is "feature complete", given some recent history. I guess it would be nice to have the hook so that users don't have to wait for the next release of Django. Django 1.8.1: Added support for serializing datetime.timedelta objects. Django 1.9: Added support for se

Re: deprecate CommaSeparatedIntegerField?

Thanks for feedback. Created ticket for the deprecation: https://code.djangoproject.com/ticket/26154 On Thursday, January 21, 2016 at 3:06:39 AM UTC-5, Shai Berger wrote: > > On Thursday 21 January 2016 09:59:49 Aymeric Augustin wrote: > > > On 21 janv. 2016, at 07:24, Josh Smeaton > wrote: >

Replacing the contrib.sites Site model with a setting?

In another thread about adding a "scheme" field to the Site model [1], I floated the idea of moving the data stored by the Site model into a setting: I've sometimes thought that the Site model violates the principle that you shouldn't put configuration in your database. I guess there's some use

Deprecate Cache.has_key()?

Any opposition to deprecating Cache.has_key()? Cache already implements __contains__() so converting has_key() to "in" can be done with existing versions of Django. Anyone using flake8 will get a warning about has_key() usage: W601 .has_key() is deprecated, use 'in'. -- You received this messa

Re: Deprecate Cache.has_key()?

Also the template BaseContext class has an undocumented has_key() method. I wonder if that can be removed without a deprecation? https://github.com/django/django/pull/6066 On Friday, January 29, 2016 at 6:11:54 PM UTC-5, Tim Graham wrote: > > Any opposition to deprecating Cache.has_key()?

Re: Deprecate Cache.has_key()?

th the dict interface? True, it's discouraged > now, but it's still there. > > > > On 30 January 2016 10:42:12 am LHDT, Tim Graham > wrote: >> >> Also the template BaseContext class has an undocumented has_key() method. >> I wonder if that can be remov

Fellow Report - January 30, 2016

Triaged --- https://code.djangoproject.com/ticket/26130 - Convert ModelAdmin views to class-based views (duplicate) https://code.djangoproject.com/ticket/26131 - model field choices are not enforced (invalid) https://code.djangoproject.com/ticket/26134 - Update MySQL GIS function names

Re: [admin] submit_row template tag reusability issue

Here is an accepted ticket: https://code.djangoproject.com/ticket/13875 Feel free to update and/or improve the patch, add tests, and send a pull request. Thanks! On Monday, February 1, 2016 at 6:18:35 AM UTC-5, Federico Capoano wrote: > > Hi all, > > I came across the need of modifying the submi

[ANNOUNCE] Django releases issued: 1.9.2 (security) and 1.8.9 (bugfix)

Today the Django team issued 1.9.2 as part of our security process. This releases address a security issue, and we encourage all users to upgrade as soon as possible. The Django 1.8.9 release fixes several bugs in 1.8.8 but no security issues as the issue fixed in 1.9.2 doesn't affect older ver

Re: Deprecate Cache.has_key()?

UTC-5, Adam Johnson wrote: > > Might be problematic for third-party cache backends which implement > *has_key* and rely on *__contains__* calling it - don't see how you can > show the warning in that case. > > On Saturday, January 30, 2016 at 12:34:14 PM UTC, Tim

Re: Adding SASL authentication support to PyLibMCCache

I found an old discussion about it, but it didn't attract much interest at the time: https://groups.google.com/d/topic/django-developers/pISp20wuu0E/discussion On Saturday, January 30, 2016 at 7:21:49 PM UTC-5, Ed Morley wrote: > > Hi > > For apps running on Heroku, two of the main memcached opt

Re: Extending ModelForm.save_m2m

Your description is a bit abstract for me to understand. Could you put together a before (how the code looks now) and after (how the code would look with this feature) for an example use case? On Monday, February 1, 2016 at 2:30:15 PM UTC-5, is_null wrote: > > Hi all, > > My understanding of th

Re: Extending ModelForm.save_m2m

I'm trying to understand what you're trying to accomplish at a very basic level. I'm not familiar with any of the third-party packages you mentioned. How will the proposed changes in Django simplify them? In your second mail you proposed a "form_business" kwarg with a "YourFormBusiness" argument

remove support for unsalted password hashers?

Django 0.90 stored passwords as unsalted MD5. Django 0.91 added support for salted SHA1 with automatic upgrade of passwords [0]. In Django 1.4, the new password hashing machinery was added and some users complained that they couldn't upgrade because the password format from Django 0.90 was no l

Re: [admin] submit_row template tag reusability issue

Hi Tim, > > thank you for letting me know of the open ticket. > The "patch needs improvement" flag is set to "no". Is that correct or not? > > Federico > > On Mon, Feb 1, 2016 at 1:18 PM Tim Graham > wrote: > >> Here is an accepted ticket: https://c

Re: remove support for unsalted password hashers?

eep them around if it needs them. > > > -- > Raphaël > > On Tue, 2 Feb 2016 08:10:50 -0800 (PST) > Tim Graham > wrote: > > > Django 0.90 stored passwords as unsalted MD5. Django 0.91 added support > for > > salted SHA1 with automatic upgrade of passwo

Re: #26165 new Cleanup/optimization wanted to start with a documentation ticket

The FAQ is at: https://github.com/django/django/tree/master/docs/faq Depending on how much content there is, it might make more sense to add the questions on the CSRF reference page instead: https://github.com/django/django/blob/master/docs/ref/csrf.txt Please read the contributing documentation

Remove null assingment check for non-nullable fields?

There's a proposal to remove this behavior: >>> obj.fk = None ValueError('Cannot assign None: "Obj.fk" does not allow null values.) (i.e. no more exception if you assign None to a non-nullable foreign key) Rationale presented on the ticket [1]: - Conceptually it is a programmer's respon

Re: Admin Improvement - Autocomplete & improved search for FKs

Here is an accepted ticket for autocomplete: https://code.djangoproject.com/ticket/14370 The "improved search" seems like what we already have when using raw_id_fields so it seems like it should be easy to include as part of the autocomplete UI. I don't see think it needs to be a separate optio

Re: #26165 new Cleanup/optimization wanted to start with a documentation ticket

Please send the pull request -- we do review there, not on this mailing list. Thanks! On Wednesday, February 3, 2016 at 10:27:32 AM UTC-5, Vivek unni wrote: > > Hi. I have compiled a list of questions. I made a section in the faq > folder. These are the questions and answers I wrote. These answe

Re: #25897 - managers defined on non-abstract base classes inherited by child classes

e, since 'SimpleComment' gives False in similar sitation. > print(models.Comment.objects.model) #, this manager > is not contributed to 'Comment' class > > Tim Graham suggests asking if anyone relying on this inheritance and > documentation should be fixed instead.

Re: remove support for unsalted password hashers?

need to change that, whether it's force_login() or some new "no-op test hasher" . On Tuesday, February 2, 2016 at 2:20:44 PM UTC-5, Donald Stufft wrote: > > > On Feb 2, 2016, at 1:52 PM, Tim Graham > > wrote: > > Just to be clear, my proposal here

Re: Remove null assingment check for non-nullable fields?

jango since 1.0: https://github.com/django/django/commit/1452d46240609ff39dacf9ea2f759ed600c2f09f On Wednesday, February 3, 2016 at 11:37:31 AM UTC-5, Florian Apolloner wrote: > > On Wednesday, February 3, 2016 at 12:26:26 AM UTC+1, Tim Graham wrote: >> >> There's

Re: GSOC 2016

Please see https://code.djangoproject.com/wiki/SummerOfCode2016 especially "How can I improve my chances of being accepted?" On Thursday, February 4, 2016 at 1:54:38 PM UTC-5, sharma1...@gmail.com wrote: > > Hi, > > I am a computer science undergraduate. I want to get started on > contributing

Re: Will Django be a part of Google's Summer of Code 2016 program?

Yes, please see https://code.djangoproject.com/wiki/SummerOfCode2016 especially "How can I improve my chances of being accepted?" On Thursday, February 4, 2016 at 1:54:38 PM UTC-5, Cory Kitchens wrote: > > Hello all, > > My name is Cory Kitchens and I am currently a Computer Science student > lo

Re: remove support for unsalted password hashers?

I wasn't sure how to upgrade passwords as Florian said. Here's the answer from Donald in IRC: You can always wrap hashers, e.g. if you have a hasher which is sha1(password), add a new hasher which is bcrypt(sha1(password)) You can convert your database in a migration and you immediately get all

Re: remove support for unsalted password hashers?

I'm not sure if we can keep support for unsalted hashes while removing the special logic in identify_hasher() for those hashers since they don't confirm to Django's normal hash format? https://github.com/django/django/pull/6082/files#diff-2f01db46550174ad3e55be7070b98ec9 I guess a use case where

Re: remove support for unsalted password hashers?

tufft wrote: > > > > On Feb 5, 2016, at 10:04 AM, Tim Graham > wrote: > > > > I'm not sure if we can keep support for unsalted hashes while removing > the special logic in identify_hasher() for those hashers since they don't > confirm to Django'

Re: remove support for unsalted password hashers?

I would guess most users aren't customizing the default list of hashers, so I'd rather remove weak hashers from the PASSWORD_HASHERS setting and let anyone who needs to use a weak hasher define their own setting (at which point a warning probably isn't needed). Does that seem okay? On Friday, F

Re: Changing the primary key of Django models

By the way, the django-developers mailing list is about the development of Django itself. Please keep usage questions limited to django-users. Thanks! On Friday, February 5, 2016 at 6:10:04 PM UTC-5, Dheerendra Rathor wrote: > > Yes you can keep custom primary key. Pass `primary_key=True` in your

Fellow Report - February 6, 2016

Triaged --- https://code.djangoproject.com/ticket/26162 - Data loss when ManyToManyField refers to the wrong table (accepted) https://code.djangoproject.com/ticket/26168 - BooleanField is forced to be blank=True (accepted) https://code.djangoproject.com/ticket/26171 - ForeignKey with d

Re: Detect languages for a short text and files

This mailing list is for the development of Django itself. Please write to django-users for usage questions (but this question doesn't seem to be Django related). On Monday, February 8, 2016 at 7:06:43 AM UTC-5, Allison A. wrote: > > I am looking for a python package for detecting language. So f

Re: Index expressions

I added "Custom indexes" to the ideas list at https://code.djangoproject.com/wiki/SummerOfCode2016. Feel free to revise the description or add yourself as a possible mentor. On Sunday, February 7, 2016 at 6:26:38 AM UTC-5, Josh Smeaton wrote: > > There are many places that expressions can extend

Re: remove support for unsalted password hashers?

allow us to trim the full list of hashers which is repeated > > several times in the docs. > > > > -- > > Aymeric. > > > >> On 6 févr. 2016, at 00:03, Tim Graham > >> <mailto:timog...@gmail.com >> wrote: > >> > >> I woul

Re: View permissions to admin

I think a view permission is reasonably within the scope of the admin, although I'm a bit nervous that we'll forget about it in some future feature and end up introducing a security issue. Since the topic comes up from time to time, I submitted a PR to remove "production-ready interface" from t

Re: Model Meta inheriting ordering from abstract models

Did you try looking through git blame and old tickets to find the reason for it? The issue is raised on https://code.djangoproject.com/ticket/11078. On Monday, February 8, 2016 at 11:19:02 PM UTC-5, Aron Podrigal wrote: > > Hi, > > While going through the code for ModelBase I came across the foll

thinking about the admin's scope and its description in the docs

The introduction to the admin in the docs [0] reads: "One of the most powerful parts of Django is the automatic admin interface. > It reads metadata in your model to provide a powerful and production-ready > interface that content producers can immediately use to start adding > content to the s

Re: remove support for unsalted password hashers?

itten instructions on how to upgrade such passwords without requiring all your users to login [1]. If it's warranted, we could make a blog post advising this. [1] https://github.com/django/django/pull/6114 On Monday, February 8, 2016 at 3:12:28 PM UTC-5, Tim Graham wrote: > > Thanks for the f

Re: Django & django-polymorphic

I'm not sure. Did you find this past discussion: https://groups.google.com/d/topic/django-developers/tSLuqu0UFrY/discussion ? The idea was also mentioned a month ago with no replies: https://groups.google.com/d/topic/django-developers/Ov91x7AXwmM/discussion Are you a maintainer of django-polymo

Re: How to let users to block private messages in Django-postman?

This mailing list is for the development of Django itself. Please write to django-users for usage questions. On Thursday, February 11, 2016 at 7:24:11 PM UTC-5, Lukas wrote: > > Hi all, > > I have instlled django-postman but it works great. However I'd like to > allow users to opt for not receiv

Fellow Report - February 13, 2016

Triaged --- https://code.djangoproject.com/ticket/26183 - PostgreSQL backend: TimeField is created without time zone (wontfix) https://code.djangoproject.com/ticket/26184 - Unable to use custom lookups or transforms in admin `search_fields` (accepted) https://code.djangoproject.com/tick

Re: [Discussion] Legacy documentation / Boken docs Django v1.2

s far back as 1.4 today. On Monday, April 13, 2015 at 11:08:59 AM UTC-4, Florian Apolloner wrote: > > As long as it doesn't hurt we can keep em there -- remove as soon as they > cause a problem ;) > > On Monday, April 13, 2015 at 4:30:01 PM UTC+2, Tim Graham wrote: >>

Re: thinking about the admin's scope and its description in the docs

Here's another try for the docs: One of the most powerful parts of Django is the automatic admin interface. It reads metadata from your models to provide a quick, model-centric interface where trusted users can manage content on your site. The admin's recommended use is limited to an organization

Re: remove support for unsalted password hashers?

ns in [1] 2. Remove SHA1PasswordHasher from the default PASSWORD_HASHERS in Django 1.10 to force projects to explicitly acknowledge use of an insecure hash if they require it. [1] https://github.com/django/django/pull/6114 On Wednesday, February 10, 2016 at 5:16:11 PM UTC-5, Tim Graham wrote: &

Re: Contribution to django

Please read our contributing documentation: https://docs.djangoproject.com/en/dev/internals/contributing/new-contributors/ On Thursday, February 18, 2016 at 8:28:07 AM UTC-5, ABHINAV RAI wrote: > > Hello > > I am Abhinav Rai, Sophomore from Computer Science Engineering from Indian > Institute of

Re: [Discussion] Legacy documentation / Boken docs Django v1.2

I guess I'm not strongly opposed if someone wants to do that, but I don't think I can justify spending time on the DSF's dime to help out users of unsupported versions. On Thursday, February 18, 2016 at 9:33:52 AM UTC-5, Fred Stluka wrote: > > I vote for a 301 to the matching ReadTheDocs page. >

<    6   7   8   9   10   11   12   13   14   15   >