Re: Extend support for long surnames in Django Auth

nt number of people have a last name that contains more than > 100 characters and that isn’t a joke. How would it fit on a passport? See #6 of https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ — Donald Stufft -- You received this message because you are subs

Re: Should we require pytz for timezone support in Django?

rly when those things are something as trivial to install as a pure python library like pytz. [1] Using the now public metrics database. — Donald Stufft -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)&q

Re: Thoughts on ASGI or Why I don't see myself ever wanting to use ASGI

except instead of using the network and a queue to allow calling sync user code from an async process, you just use the primitives provided by the async framework. ----- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- You received

Re: Thoughts on ASGI or Why I don't see myself ever wanting to use ASGI

> On May 6, 2016, at 1:45 PM, Andrew Godwin <and...@aeracode.org> wrote: > > Want to just cover a few more things I didn't in my reply to Aymeric. > > On Fri, May 6, 2016 at 9:11 AM, Donald Stufft <don...@stufft.io > <mailto:don...@stufft.io>> wrote: > &

Thoughts on ASGI or Why I don't see myself ever wanting to use ASGI

I believe it shows up as an IOError. In something like Twisted or AsyncIO it would likely show up as a CancelledError. - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- You received this message because you are subscribed

Re: Vendoring multipledispatch

t nice quality of life things are: * Massively reduced verbosity on install. * Nicer progress bars. > Anyway as long as Django is installed in a virtualenv this shouldn't be too > much of an issue, but I think we should expect some issues from the users and > these should be documente

Re: Vendoring multipledispatch

u have to install something or if you want to use an ImageField, or bcrypt, etc. Having ``pip install Django`` work but not ``pip install Django psycopg2`` when you’re running a site that uses PostgreSQL doesn’t get you anything extra there. - Donald Stufft PGP: 0x6E3CBCE93372

Re: Vendoring multipledispatch

ut looking at this specific thing too closely, maybe it’s time for Django to gain a required dependency instead of bundling or reinventing everything? - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- You received this message

Re: Feedback on Django Channels

connections natively so, at least from Python, it’s not any harder to connect to a TLS’d Redis server. ----- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- You received this message because you are subscribed to the Google Groups "Djan

Re: remove support for unsalted password hashers?

uld be trivial to migrate the database to make the hashed password conform to the format. - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- You received this message because you are subscribed to the Google Groups "Django

Re: remove support for unsalted password hashers?

and > your passwords happen to use md5(md5(pass) + md5(pass)) for passwords? You can implement them still sure, there’s nothing stopping you. You can also do bcrypt(md5(md5(pass) + md5(pass)) and then you’ve fixed the issue without needing to issue a password reset. - Donald S

Re: remove support for unsalted password hashers?

e MD5 of every single possible lower case alpha numeric of 6 characters or less in under a minute on a single regular desktop/server.. I don’t believe the distinction is useful. --------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- You

Re: Channels integration plan, first draft

That syntax allows you to add extra, opt in lists of dependencies to install. It does not pass through to runtime. Sent from my iPhone > On Dec 18, 2015, at 12:34 PM, Marc Tamlyn wrote: > > On a packaging note, is there a way to use django[channels] type syntax like >

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

s. > > Is your main opposition to the change a "purity" one? Sure, we could add a > pip version check, but I don't see any downside to the proposed change. > pip 1.5.6 will print the warning but it’s just a warning. Newer pips will silence it. A failure to compile to .pyc never

Re: annoyance with Python 3.2 support in Django 1.8

ckport security fixes to their own > versions of Python 3.2, but it seems that Ubuntu 12.04's version of Python > 3.2 didn't incorporate the security fix which caused breakage. FTR the next major version of pip does not support Python 3.2. - Donald Stufft PGP: 0x6E3CBCE93372

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

ccording to GitHub > search. > Whoever generated the tarballs is probably using a version of setuptools older than 8.0 in their Python 2 environment and a version of setuptools newer than 8.0 in their Python 3 environment. - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D

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

. PEP 386 has been superseded by PEP 440 which recommends “rc” because almost everyone was using “rc” and not “c”. It didn’t seem reasonable to have a decision which was solely bike shedding (it can handle rc as easily as it can handle c) to favor an option that flew in the face of what most

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

ae7be8e-949c-4074-b613-04ca2a62fed8%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. > - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- You received this message because you are subscribed

Re: Static type checking for public API

rs. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/81f6b5a2-14a2-4a7a-82c4-74d3016ff59f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F

Re: Methodology for increasing the number of PBKDF2 iterations

cy for those old versions of > Python in new versions of Django. > https://cryptography.io/en/latest/hazmat/primitives/key-derivation-functions/#cryptography.hazmat.primitives.kdf.pbkdf2.PBKDF2HMAC   ----- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6

Re: Methodology for increasing the number of PBKDF2 iterations

than CPU increases because if it was equal to that we'd never catch up to where we should be. ----- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- You received this message because you are subscribed to the Google Groups "Dja

Re: Pre-DEP: community support of unmaintained versions of Django

On August 19, 2015 at 11:31:46 AM, Carl Meyer (c...@oddbird.net) wrote: > On 08/19/2015 09:28 AM, Donald Stufft wrote: > > On August 19, 2015 at 11:25:55 AM, Carl Meyer (c...@oddbird.net) wrote: > >> In my ideal world, the version number would help convey unofficial-ness > &

Re: Pre-DEP: community support of unmaintained versions of Django

e.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/55D49FEE.80503%40oddbird.net. > > For more options, visit https://groups.google.com/d/optout. > - Donald Stufft PGP: 0x6E3CBCE93372

Re: Proposal: deprecate and remove egg template loader

6owqH4dMzrShVKwVoLxUg%40mail.gmail.com. > > For more options, visit https://groups.google.com/d/optout. > --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- You received this message because you are subscribed to the Google Groups "Django developers

Re: Requiring GitHub login for actions on Trac

could just pull permissions from GitHub? --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails fro

Re: Django and BREACH (remember that?)

On August 3, 2014 at 9:48:53 PM, Adam Brenecki (adambrene...@gmail.com) wrote: > The patch I've written implements this mitigation, with one difference: > instead of using xor, it uses a Vigenère cipher (as suggested by FunkyBob), > as xor was creating non-printable characters which caused

Re: FR: Setting for CSRF Header (pull-request included)

setting although i’m inclined to say you shouldn’t change the setting in that case. -- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- You received this message because you are subscribed to the Google Groups "Django developers" group.

Re: Pull django-registration into contrib?

e registration system since generally most pieces of a site do not interact with the registration system, especially not at the level as they would for the generic concept of users or database migrations. -- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9

Re: use semantic versioning after 2.0?

subscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/5fab23be-1411-4813-bfbe

Re: DEPs: Django Enhancement Proposals

Draft to Accepted and it stays that way until it gets implemented and committed. Then it changes from accepted to final and the PEP process is done. One thing i’m not sure of, how is DEPs going to work without a BDFL? Generally they are used to get feedback and provide a clear c

Re: [GSoC] Switching to Jinja2 proposal

com/dstufft/8455306 > >> 3) Supporting Jinja2 out-of-the-box means introducing dependencies. Are we >> ready for this? > > I think so, yes. > > Carl > - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA signature.asc Description: Message signed with OpenPGP using GPGMail

Re: [GSoC] Switching to Jinja2 proposal

and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web vis

Re: [GSoC] Switching to Jinja2 proposal

post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAG_XiSBmOU%3D4orZnW13bw-ZLT_O416unynhtnQ9%3DhgPtL9Bbtw

Re: Using setuptools to make django-admin.py runnable on Windows (#21340)

On Dec 4, 2013, at 5:51 PM, Florian Apolloner <f.apollo...@gmail.com> wrote: > On Wednesday, December 4, 2013 11:20:39 PM UTC+1, Donald Stufft wrote: > entry points are kinda wonky with pip 1.4, pip 1.5 makes them sane. You would > not need a Windows specific Whe

Re: Using setuptools to make django-admin.py runnable on Windows (#21340)

@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/f3195fb1-1505-41ce-b34a-0cf147f33e1f%4

Re: Using setuptools to make django-admin.py runnable on Windows (#21340)

The recommended build tool at the moment is setuptools. It's up to the individual project to decide if they think the install story for setutpools pre 3.4 is appropriate for them. This'll get better in general in the future with MSI installers for setuptools and pip > On Nov 24, 2013, at

Re: BCrypt and PBKDF2 Password Hash Caching

that it doesn't negatively impact your site but as slow as possible otherwise. The higher the work factor/iterations the harder it is to brute force, but the more negative impact each login has. I would tune bcrypt or PBKDF2 down before I implemented this custom scheme. -- Donald Stufft don

Re: Performance Docs

top receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > For more options, visit https://grou

Re: Default session data serializer doesn't support extended data types

from pickle as the default serialization engine ensures this property for the storage of session data. - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA signature.asc Description: Message signed with OpenPGP using GPGMail

Re: Idea about authentication

kely, but who knows). According to Thomas Porin in the context of bcrypt pre-hashing the password is fine (and we already do this in Django 1.6). I see no reason the same wouldn't hold true for PBKDF2. - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9

Re: Idea about authentication

t;Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > For more options, visit https://groups.google.com/groups/opt_out. - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA signature.asc Description: Message signed with OpenPGP using GPGMail

Re: Idiot makes mistake

ups.google.com/groups/opt_out. If anyone made any commits in the last hour you should probably double check to make sure they are there. I'm pretty sure we got it restored but doesn't hurt to double check. - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3

Re: Deprecation a little harsh?

alid answer. Lack of CI is probably going to be one of the biggest blockers. Without CI it's up to the merging developers to run the tests on all the combinations of stuff we support which isn't the easiest or the quickest thing to setup and maintain. - Donald Stufft PGP: 0x6E

Re: GZipMiddleWare documentation

ation level is going to be important. The application knows what *kind* of data exists in a response body and wether or not it is safe to compress it. The web server does not (except by crude heuristics such as path). - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2

Re: Security Advisory: BREACH and Django

an be > set in location. Yes, any response which does not include secret data can be compressed. --------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA signature.asc Description: Message signed with OpenPGP using GPGMail

Re: Security Advisory: BREACH and Django

bscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com

Re: Security Advisory: BREACH and Django

g emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > For more options, visit https://groups.google.com/group

Re: Question about password salt and encryption

s@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > For more options, visit https://groups.google.com/groups/opt_out. > > Backwards compatibility is easy. Just add a new hasher. - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA signature.asc Description: Message signed with OpenPGP using GPGMail

Re: RFC: "universal" view decorators

//groups.google.com/groups/opt_out. > > Part of the reasoning of my original Change to make decorators classes was that it enabled much easier customization of them. Currently you basically either hope there was an option for doing what you wanted, or you copy/paste the entire thing and m

Re: Meta-Proposal: Write *above* quotations in mailing list replies

oup/django-developers?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > I think trying to get anyone to change their posting habit is a futile effort. - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA signature.asc Description: Message signed with OpenPGP using GPGMail

Re: Anyone have ideas on #16550 - custom SQL before/after syncdb?

On May 21, 2013, at 12:11 PM, peter <peter.vo...@ff.com> wrote: > +1 on pre_syncdb > > On Tuesday, May 21, 2013 8:29:49 AM UTC-7, Shai Berger wrote: > On Tuesday 21 May 2013, Donald Stufft wrote: > > I run migrations in test. How else will you know

Re: Proposal: implement Postgres CLUSTER USING by default for MtM tables

it this group at http://groups.google.com/group/django-developers?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > What do you mean by "clustering by default". CLUSTER is a one time operation. You use to to arrange the orders of the row in a table but afte

Re: Combine localflavor apps again

it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers?hl=en. > For more options, visit https://groups.google.com/groups/opt_out.

Re: Anyone have ideas on #16550 - custom SQL before/after syncdb?

t >> right at the end for every model you think you touched). >> >> However, the patch Donald linked would be a lot easier to emulate, so I'm >> not that against it. >> >> Andrew >> >> >> On Sat, May 18, 2013 at 7:15 PM, Donald Stufft <don

Re: Anyone have ideas on #16550 - custom SQL before/after syncdb?

group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers?h

Re: RFC: "universal" view decorators

you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA signature.asc Description: Message signed with OpenPGP using GPGMail

Re: BCrypt + Python3

ause you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com.

Re: Anyone have ideas on #16550 - custom SQL before/after syncdb?

jango-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > pre

Re: Ticket 13978: Allow inline js/css in forms.Media

Re CSP It's more or less fine to start using it. It needs a clean API for configuring it still but it's pretty solid. However a newish feature that has been added is the ability to allow _some_ inline scripts but not all. This feature doesn't have widespread support yet sadly though. The

Re: Perception of attitude in tickets

on an issue is that it will make people feel justified in asking/demanding a feature that doesn't have a chance of going on. A bad idea with a 100 yes votes isn't going to get in any more than a bad idea with 1 yes vote. That's not to say it's not an ok idea. I don't know if it is or not. Bu

Re: BCrypt + Python3

On May 11, 2013, at 4:10 AM, Claude Paroz <cla...@2xlibre.net> wrote: > Le samedi 11 mai 2013 07:59:18 UTC+2, Donald Stufft a écrit : > I went looking for BCrypt + Django + Python3 today and this is what I found: > > The current recommended solution to bcrypt + Django is usi

BCrypt + Python3

encode(). [2] Found at https://crate.io/packages/bcrypt/ or https://github.com/dstufft/bcrypt [2] Found at http://www.openwall.com/crypt/ - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA signature.asc Description: Message signed

Re: Perception of attitude in tickets

erience in future. > > Thanks for reading > > Simon > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-dev

Re: Recommending a Python 3-compatible MySQL connector

ecause there is nothing a typical Django project > would be doing with that library that would actually require them to > accept the terms of the license. > > The GPL allows *using* of the code for any purpose. It's only when a > project becomes a distributor of the GPL code that it is r

Re: test discovery

UNNER > to point to the old runner and get back the old behavior, which they can > keep using until Django 1.8 (or longer, if they package the old runner > externally). This sounds reasonable to me. Tests are not production code so I agree with Jacob. - Donald Stufft

Re: Django 1.6 release timeline

> > Andy There is no requirement to migrate for the new way to handle user models. The only time you'd need to migrate is if you want to swap out your existing user models that Django provides with new ones. If you don't do that then you don't need to migrate. -

Re: Django 1.6 release timeline

ly as Aug 8, or later if more RCs are needed. Sounds reasonable. - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA signature.asc Description: Message signed with OpenPGP using GPGMail

Re: Request method in urls.py

gle.com/group/django-developers?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this gro

Remove download_url from setup.py

? - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA signature.asc Description: Message signed with OpenPGP using GPGMail

Re: Documenting lazy() and memoize()

s.google.com/group/django-developers?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > https://docs.djangoproject.com/en/1.5/ref/urlresolvers/#reverse-lazy ? - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA signature.asc Description: Message signed with OpenPGP using GPGMail

Re: Proposal: deprecate and remove django.contrib.comments

On Mar 7, 2013, at 11:48 AM, Jacob Kaplan-Moss wrote: > Hi folks -- > > This one's simple: I'd like to deprecate `django.contrib.comments`, > scheduling it to be removed in a couple of releases. > > My rationale is this: if you don't really care much about how comments >

Re: Switch to database-level autocommit

On Friday, March 1, 2013 at 7:48 AM, Aymeric Augustin wrote: > Hello, > > I'd like to improve transactions handling in Django. The first step is the > current emulation of autocommit with database-level autocommit. > > ** Rationale ** > > PEP249 says that any SQL query opens a transaction

Re: Proposal: use SQLAlchemy Core for query generation

On Wednesday, December 26, 2012 at 10:56 PM, Russell Keith-Magee wrote: > That depends entirely on what you consider the goal of the ORM to be. > > You have assumed that the goal would be "allow an arbitrary query to run on > any underlying data store, and run with equivalent efficiency". In

Re: Proposal: use SQLAlchemy Core for query generation

On Wednesday, December 26, 2012 at 10:00 PM, Russell Keith-Magee wrote: > Why? Because we've gone to extraordinary lengths to make sure this sort of > thing is at least theoretically possible. > > Although we use the term "ORM", and there's currently only relational > implementations of

Re: Proposal: use SQLAlchemy Core for query generation

On Sunday, December 23, 2012 at 4:08 PM, Florent Gallaire wrote: > Django ORM should work for SQL and NoSQL DBMS. > NoSQL integration in Django is a more interesting and needed subject, > but who cares about that in the core team ? > > Why should the Django Object Relational Mapper be modified

Re: proposal: post-collectstatic signal

On Tuesday, November 13, 2012 at 10:43 PM, Justin Holmes wrote: > > My only concern is that we'll limit our audience by requiring users to use a > specific STATICFILES_STORAGE. What if they're already using a custom one? Put the meat of your backend in a mixin, provide options for the default

Re: 1.5, update_fields and PostgreSQL (or other MVCC style database) - request for documentation note

The major help is preventing clobbering a value for concurrency. Prior to this when you loaded an object from SQL into a django model, it would fetch all the values as they were at that time, and store them in the model instance. Then when you saved it it would write all those values back out

Re: Updating default errors in contrib.auth.forms.PasswordResetForm

The canonical way of handling this so as not to leak information like that is to do exactly the same thing UX wise for success and failures, and just update the message to state that if an email address by that account has been registered they will get an email soon. On Friday, November 2,

Re: How to test patch

Travis or Jenkins can be setup to test PR's and use Github's API to mark the PR as good to merge or not. On Sunday, October 28, 2012 at 5:20 AM, Russell Keith-Magee wrote: > > On Sun, Oct 28, 2012 at 3:55 PM, Dominic Rodger (mailto:dominicrod...@gmail.com)> wrote:

Re: The key of permissions model

Can't you add the constraint in both code and in the DB. On older sites the constraint just won't exist in the DB (Could include it in the release notes so people can add it to existing sites if they wish). On Wednesday, September 19, 2012 at 6:40 PM, Anssi Kääriäinen wrote: > We use the

Re: #3011 - Custom User Models -- Call for final review

On Tuesday, September 18, 2012 at 10:34 PM, Ben Slavin wrote: > Those apps that require (or choose to offer) a deeper stack of version > support can choose to do so, but the pragmatism of making the common case > easy (and removing the need for cross-project duplication) seems to justify > the

Re: #3011 - Custom User Models -- Call for final review

On Tuesday, September 18, 2012 at 9:13 PM, Ben Slavin wrote: > Lastly, I haven't seen a path to easily allow third-party apps to gracefully > support both The Old Way and The New Way (1.4 and 1.5). It feels a bit wrong, > but should we be considering the addition of get_user_model and >

Re: Django 1.5 release plans

On Wednesday, September 12, 2012 at 11:58 PM, timest wrote: > Can django support mongodb in version 1.5 ? If by supports you mean via the ORM, that's highly unlikely. Other then that there's nothing stopping you from using MongoDB within Django in any version of Django. -- You received this

Re: Improve Django markdown rendering.

https://bitbucket.org/ionata/django-bleach On Thursday, September 6, 2012 at 10:48 PM, Waylan Limberg wrote: > On Thu, Sep 6, 2012 at 8:22 PM, Thomas Purchas (mailto:tpurc...@gmail.com)> wrote: > > I have submitted a path to improve the way Django handles html in

Re: Testing multidb with TEST_MIRROR

On Thursday, September 6, 2012 at 6:10 PM, Jeremy Dunck wrote: > What's the base branch for the fast_tests_merged comparison? https://github.com/akaariai/django/compare/django:master...fast_tests_merged -- You received this message because you are subscribed to the Google Groups "Django

Re: Backporting some Python 3 support features to 1.4.x?

Just as an additional aside, the apps can also depend on the actual six library itself instead of Django's embedded version (It could be an optional dependency on Django < 1.5). The major things I think would be anything Django specific that don't come from six. On Thursday, September 6, 2012

Re: Breaking out localflavor

I could be wrong but offhand to make a namespace package you're going to need to make a namespace package for everything above it. So for a namespace at django.contrib.localflavor.* I *think* that django and django.contrib would both need to be namespace packages as well. If i'm right about that

Re: Django's CVB - Roadmap?

a view into smaller and more manageable chunks, without polluting the views.py namespace with multiple functions for every view. > Albert > > On Tue, Jun 5, 2012 at 10:46 AM, Donald Stufft <donald.stu...@gmail.com > (mailto:donald.stu...@gmail.com)> wrote: > > On T

Re: Django's CVB - Roadmap?

On Tuesday, June 5, 2012 at 10:35 AM, Carl Meyer wrote: > > > On 06/05/2012 08:12 AM, Donald Stufft wrote: > > In order to do this with FBV's i'd either need to modify the existing > > FBV to accept > > a parameter that says if it should filter by logged in us

Re: Django's CVB - Roadmap?

On Tuesday, June 5, 2012 at 9:55 AM, Zach Mathew wrote: > I'm not suggesting that CBVs make it harder to test (I actually think it > should be no different because the tests should avoid being implementation > specific). I just feel that the pattern of testing/refactoring is different > than

Re: Django's CVB - Roadmap?

s come from. However if you do not control that code (if it for instance, comes from Django or comes from an external library) now you have the ability to really make those kinds of tweaks. > > Albert > > On Tue, Jun 5, 2012 at 9:14 AM, Donald Stufft <donald.stu...@gmail.com >

Re: Django's CVB - Roadmap?

I tend to agree, in general, with the reply that there should be a function based api to cover the 80% use case, but in the case of Django's CBV's this is likely covered by the as_view method. On Friday, June 1, 2012 at 10:54 AM, Jacob Kaplan-Moss wrote: > On Fri, Jun 1, 2012 at 10:14 AM,

Re: Django git guidelines

en given a large change where you must then determine which change out of the entire commit caused the issue. > > Best, > Alex Ogier > > On Fri, May 18, 2012 at 12:48 PM, Donald Stufft <donald.stu...@gmail.com > (mailto:donald.stu...@gmail.com)> wrote: >

Re: Django git guidelines

On Friday, May 18, 2012 at 12:30 PM, Anssi Kääriäinen wrote: > On May 18, 6:08 pm, Donald Stufft <donald.stu...@gmail.com > (http://gmail.com)> wrote: > > I personally prefer doing normal merges with --no-ff. While "clean up > > whitespace" > > commits

Re: Django git guidelines

On Friday, May 18, 2012 at 11:04 AM, Carl Meyer wrote: > Hi Anssi, > > Thanks for working on git usage guidelines! I very much agree that a > pull request should only be created when the contributor considers the > branch finished and ready for review and merge (for instance, there > should

Re: Djangopeople.net status

djangopeople.me ? On Thursday, May 10, 2012 at 7:39 PM, Russell Keith-Magee wrote: > On Thu, May 10, 2012 at 8:55 PM, Bruno Renié (mailto:bubu...@gmail.com)> wrote: > > On Thu, May 10, 2012 at 8:04 AM, Russell Keith-Magee > >

Re: GitHub migration done!

Pretty sure this isn't going to make a compatible with the existing mirror mirror but http://hg-git.github.com/ should make it easy to go from git -> hg. On Tuesday, May 1, 2012 at 12:39 PM, Carl Meyer wrote: > On 05/01/2012 12:45 AM, Vinay Sajip wrote: > > On May 1, 2:19 am, Carl

Re: GitHub migration planning

trace instance. On Wednesday, April 18, 2012 at 7:39 PM, Łukasz Rekucki wrote: > On 19 April 2012 00:55, Donald Stufft <donald.stu...@gmail.com > (mailto:donald.stu...@gmail.com)> wrote: > > Github Issues are not flexible enough for Django. > > > That's rathe

Re: GitHub migration planning

Github Issues are not flexible enough for Django. On Wednesday, April 18, 2012 at 6:53 PM, Alex Ogier wrote: > On Wed, Apr 18, 2012 at 6:46 PM, Dalton Barreto (mailto:daltonma...@gmail.com)> wrote: > > Em 18 de abril de 2012 18:44, philipn >

Re: auth.user refactor: the profile aproach

cess to the admin. Those users > shouldn't need to have values (even default values, e.g. is_staff=False) for > admin-specific fields, and admin-specific fields shouldn't be selected every > time any user is retrieved from the database. > > Cheers. > Tai. > > > On 11/04/201

  1   2   >