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 subscribed to the Google Groups
"Django
l 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)" group.
To unsubscribe from this group and s
d 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 this message because you are subscribed to the Goog
> On May 6, 2016, at 1:45 PM, Andrew Godwin 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 <mailto:don...@stufft.io>> wrote:
>
> In short, I think that the message bus add
P/Websocket and you don't have to go and
teach say, Erlang how to ASGI.
[1] This gets exposed in a variety of ways in different servers. In gunicorn it
shows up as a SystemExit exception, in uWSGI I believe it shows up as an
IOError. In something like Twisted or AsyncIO it would
but 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
n 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: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 D
g 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 because you
, 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
"Django developers (Co
vial 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 developers (Cont
s 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 Stufft
PGP: 0x6E3
ible 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 received this message
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
> flask does? I'm not fam
on 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 fails the i
heir 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: 0x6E3CBCE93372DCFA // 7C6
widely used according 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: 0x6E3CBCE9337
nds “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 projects were
doing.
-
Donald Stufft
PGP: 0x6E
ers/5ae7be8e-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 subsc
elopers.
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
endency 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 F
en to be faster
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 Goog
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
> &
rs@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/55D49FEE.80503%40oddbird.net.
>
> For more options, visit https://groups.google.com/d/op
2BeXof9v0uBKCJ76owqH4dMzrShVKwVoLxUg%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
"Djan
d/django-developers/2d66a232-1f19-4bcc-8178-7e1e060f497b%40googlegroups.com?utm_medium=email&utm_source=footer>.
>> For more options, visit https://groups.google.com/d/optout
>> <https://groups.google.com/d/optout>.
>
>
> --
> You received this message be
I think we 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
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 problems
ipt would break
with this 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 de
or the 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
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-e
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 concise argument to the BDFL
rt 3.2?
>
> Donald might be able to offer better hard numbers based on e.g. PyPI
> usage, but my impression is that usage of 3.2 is very low, and dropping
> it for 1.8 would not be a major problem.
These numbers are about a month old, but https://gist.github.com/dstufft/8455306
>
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 visit
> https://groups.googl
st 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%40mail.gmail.com.
> 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
On Dec 4, 2013, at 5:51 PM, Florian Apolloner 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 Wheel with pip 1.5
>
> Is there a test-pyp
ail 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 visit
> https://groups.google.com/d/msg
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 2:37
7;s fast enough 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.
--
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-deve
em. Moving away 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
ely, 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
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
.
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 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
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: 0x6E3CBCE93372DCFA /
el 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 5E2B 6356 A926 F04
can 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
essage because you are subscribed to the Google Groups
> "Django developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.co
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.
>
>
--
elopers@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
gt;
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 modify it.
Using a class lets yo
opers?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
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.
>
>
I vote #3.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
On May 21, 2013, at 12:11 PM, peter 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 your db reflects reality
> > :/
>
.
> Visit 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 tabl
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.
>
>
This sounds ok to me.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
t 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 wrote:
>>&g
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
gt;
>
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post 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
gt; --
> Aymeric.
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.c
ngo-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_syncdb signal
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 oth
roblem with voting 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 id
On May 11, 2013, at 4:10 AM, Claude Paroz 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 using py-bcrypt which
> is
suming
a character set it can 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
De
ay, I wanted to take a few minutes and share the impressions I've had to
> date - perhaps this way, others will have a better experience in future.
>
> Thanks for reading
>
> Simon
>
> --
> You received this message because you are subscribed to the Google Groups
cal 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 required to
> abide
int 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
PGP: 0x6E3CBCE93372DC
igrate 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.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA
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
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
Thoughts?
-----
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
om/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
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
> work but just want some
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 an
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 t
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 Django's
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
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 o
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 to
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, 20
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:
> > Another long time user h
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 style
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 u
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
> setting
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 mes
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 markdown.
> > Specifically how
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 develo
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
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 t
better as it enables you to break apart 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 (mailto:donald.stu...@gmail.com)> wrote:
> > On Tues
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
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 the
en you
control the code where those views 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
On Tuesday, June 5, 2012 at 9:05 AM, Albert O'Connor wrote:
> My feeling is that though some people might have uses for CBV, we
> shouldn't be suggesting that developers should prefer CBV to function
> based views. When it comes to maintainability, FBV are better, and I
> would agree that they are
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, Victo
x27;re often 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 (mailto:donald.stu...@gmail.com)> wrote:
> > On Friday, May 18, 20
On Friday, May 18, 2012 at 12:30 PM, Anssi Kääriäinen wrote:
> On May 18, 6:08 pm, Donald Stufft (http://gmail.com)> wrote:
> > I personally prefer doing normal merges with --no-ff. While "clean up
> > whitespace"
> > commits are extraneous, they don&#
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 never
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
> > mailto:russ...@keith-magee.com)> wrote:
> > > On Thu, May 10, 2012
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 Meyerhttp://o
1 - 100 of 146 matches
Mail list logo
