re out the
specifics".
https://www.djangoproject.com/weblog/2013/may/26/django-16-alpha-1/
Regards,
Michael Manfre
On Tue, Aug 6, 2013 at 10:42 AM, Jacob Kaplan-Moss wrote:
> Hi folks --
>
> At last week's Black Hat conference, researchers announced the BREACH
> attack (
x27;m only trying to further the discussion.
Regards,
Michael Manfre
On Tue, Aug 13, 2013 at 11:21 AM, Jacob Kaplan-Moss wrote:
> I'm sorry; I was snarkier and nastier than I should have been (and than I
> intended to be). Thanks for calling me on it; I'll try to do better next
This list is for the development of Django. Questions about about how to
use Django are located on the django-users list.
https://groups.google.com/forum/#!forum/django-users
Regards,
Michael Manfre
On Thu, Aug 15, 2013 at 9:14 AM, Tuten wrote:
> I am in a situation where if I can cach
rsion bundled with pywin32 doesn't
have the necessary changes yet.
Regards,
Michael Manfre
On Thu, Aug 15, 2013 at 2:28 PM, Larry Martell wrote:
>
>
> On Wednesday, May 8, 2013 5:02:02 AM UTC-4, VernonCole wrote:
>>
>> Hello all:
>>I just want to let ev
database schema. Perhaps a
better way to resolve the issue is to create a management command that
compares the model definitions against the database schemas. Part of its
check could be to identify potential issues with collation and length.
Regards,
Michael Manfre
On Wed, Aug 21, 2013 at 8:30 AM
d and GenericIPAddressField are similar to the various integer
fields. When BigIntegerField was added to the core, IntegerField and
SmallIntegerField still had their purpose.
Regards,
Michael Manfre
On Sat, Aug 24, 2013 at 3:40 PM, Erik Romijn wrote:
> Hello all,
>
> On May 18, 2013, at 2:07 P
e
> changed.
>
This is probably true for some databases, but not guaranteed to be true for
all.
Regards,
Michael Manfre
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving ema
On Sep 15, 2013 12:23 PM, "Aymeric Augustin" <
aymeric.augus...@polytechnique.org> wrote:
>
> On 15 sept. 2013, at 17:57, Simon Kern wrote:
>
> > Yes but management commands should be irrelevant for django-secure
>
> Well, in this case, I have a backup argument :)
>
> There's a non-negligible
backend specific
When the savepoint changes break the fragile tests, that will be a good
thing because they will need to be rewritten (hopefully with proper guards).
Regards,
Michael Manfre
--
You received this message because you are subscribed to the Google Groups
"Django developers" group
On Sun, Sep 22, 2013 at 5:09 PM, Shai Berger wrote:
> If this is agreed, then we should add an assertNoQueries, deprecate the
> existing assertNumQueries, and add a new assertNumQueries that takes a
> backend
> specification, shouldn't we? This is regardless of what we do with @atomic.
assertN
ed as a
string, int, or object.
Regards,
Michael Manfre
On Mon, Sep 23, 2013 at 10:36 AM, Zev Benjamin wrote:
> Hi,
>
> I'd like to be able to specify what kind of index the database should use
> for a particular field. I have a proof of concept branch that works with
> Postgre
7;m hoping
this can find its way in to 1.7, which drops Python 2.6 support and
effectively removes using cursors as context managers without this patch.
The patch has been replaced by a pull request against master.
https://code.djangoproject.com/ticket/17671#comment:12
Regards,
Michael Manfre
--
Yo
gsBackend would need to add reload() and
save().
Is rough idea worth pursing? If so, I'll be happy to spend time
brainstorming and prototyping it. Settings have been a very annoying pain
for me for many years.
Regards,
Michael Manfre
On Thu, Sep 26, 2013 at 9:21 AM, Andres Osinski wrote:
&g
ready. You can't do it as chained QuerySet calls, but the
only time this would make sense in code is when a QuerySet was passed with
a potentially unknown can_filter state, so you'd need to reset it before
using it.
if not qs.query.can_filter():
qs.query.clear_limits()
qs.filter(...)[:10]
I plan on creating a ticket for this. If this usage is deemed valid, then
it's a pretty serious issue for any site dealing with credit cards and it's
probably a release blocker. If this usage is not valid, then the ticket
will be to update the documentation so that others know not to do tha
Storing bits as a string is not an efficient use of space and is slower to
query. Any reason why you are not using the bit datatype with a length?
E.g. 'bit(%s)' % len(self.flags)
Regards,
Michael Manfre
On Fri, Nov 1, 2013 at 3:50 PM, Paul Kenjora wrote:
> Hi,
>
> I'
. The
current message is perfectly concise. Dumping the SQL would add a lot of
noise.
Regards,
Michael Manfre
On Thu, Nov 14, 2013 at 1:37 AM, Dominic Rodger wrote:
> Currently, when assertNumQueries fails, the output is perhaps less helpful
> than it might be:
>
> Traceback (most
MSSQL's schema tables.
[1] sp_rename - http://technet.microsoft.com/en-us/library/ms188351.aspx
[2] ALTER TABLE - http://msdn.microsoft.com/en-us/library/ms190273.aspx
Regards,
Michael Manfre
--
You received this message because you are subscribed to the Google Groups
"Django developers" gro
[2].
[1] https://github.com/django/django/pull/2143
[2]
https://bitbucket.org/Manfre/django-mssql/src/29c4d4ecc011cab0dcecadde6b7fe5f5e50bbf36/sqlserver_ado/schema.py?at=default
Regards,
Michael Manfre
--
You received this message because you are subscribed to the Google Groups
"Django dev
Thanks for the feedback. I've added answers to all of your questions and a
few extra comments about why I did certain things. Feel free to ask more
questions on the pull request or ping me on IRC.
Regards,
Michael Manfre
On Sun, Jan 5, 2014 at 7:13 PM, Andrew Godwin wrote:
> I'
(confusing name, why not
is_float), you could eliminate those and define output_type for each
Aggregate that does something special.
- What does is_summary mean?
Regards,
Michael Manfre
On Sat, Jan 11, 2014 at 3:06 AM, Josh Smeaton wrote:
> A milestone has been reached. The diff is
Git clean -fdx
I had the same problem the other day.
On Jan 13, 2014 7:51 AM, "Josh Smeaton" wrote:
> Hey Aymeric,
>
> I've just merged master back into a branch I'm working on, and I'm seeing
> the following error when trying to run the django test suite:
>
> (django)smeatonj ~/Development/repo
se. I'd rather see a top level TEST_DATABASES
or a IS_TEST_DATABASE (default False) key added to maintain that small
amount of configuration safety.
Regards,
Michael Manfre
On Tue, Jan 14, 2014 at 12:04 PM, Shai Berger wrote:
> Hi all,
>
> Django's database settings currently
= {
'default': {
'ENGINE': 'oracle',
'NAME': 'test_my_db', # This was TEST_NAME
'USER': 'dba_user', # This is a user with proper credentials to drop a
database
...
'OPTIONS': {
# backend specific settings bel
g) for
the cases when the caller wants no result and when the caller wants to
fetch the results from the cusor directly.
[1] https://code.djangoproject.com/ticket/21751
[2] https://github.com/django/django/pull/2154
Regards,
Michael Manfre
--
You received this message because you are subscri
There are a few other things that I need to try and get in before the 1.7
feature freeze. Since this is not slated for 1.7, I'll take a look a the PR
after the freeze and see if the comments I had still apply.
Regards,
Michael Manfre
On Sun, Jan 19, 2014 at 8:00 AM, Josh Smeaton wrote:
&
e is mostly
> common within Django's code.
>
You would rather deviate from PEP 249 to avoid requiring the users of a
cursor to explicitly close it? Interesting...
Regards,
Michael Manfre
--
You received this message because you are subscribed to the Google Groups
"Django develop
rebase it against master and submit it for merging.
Regards,
Michael Manfre
On Sun, Jan 19, 2014 at 1:36 PM, Shai Berger wrote:
> On Sunday 19 January 2014 10:44:32 Michael Manfre wrote:
> > On Sun, Jan 19, 2014 at 5:23 AM, Shai Berger wrote:
> > > Still, spreading with-block
cdb-esque behavior.
*Feedback*
Please share your questions and comments on the mailing list.
Regards,
Michael Manfre
[1] https://code.djangoproject.com/ticket/21841
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubs
t; SQL scripts to send to your DBA (and many DBAs appreciate having some SQL
> they can work from - I know ours do), so having the ability to make that
> SQL is useful even if Django never runs it.
>
Agreed. DBAs are happier to have a non-blank starting point.
Regards,
Michael Manfre
--
On Wed, Jan 22, 2014 at 12:26 PM, Andrew Godwin wrote:
> On Wed, Jan 22, 2014 at 5:15 PM, Michael Manfre wrote:
>
>>
>> My request would probably be better read as "Must a database backend
>> support schema alterations?", which also implies its ability to
The pull request has been rebased.
Thanks,
Michael Manfre
On Sun, Feb 2, 2014 at 9:40 AM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> Hi Michael,
>
> On 21 janv. 2014, at 19:05, Michael Manfre wrote:
> > The overall feedback I've gotten from my p
This mailing list is for the discussion of developing the Django framework.
Discussion about using the Django framework belong on the django-users
mailing list. https://groups.google.com/forum/#!forum/django-users
Regards,
Michael Manfre
On Wed, Feb 12, 2014 at 8:27 AM, Mironiuc Sergiu wrote
This discussion list is for the development of Django. Questions about how
to use Django with your project belong on the django-users mailing list.
Regards,
Michael Manfre
On Sat, Mar 8, 2014 at 5:36 AM, Pramod Jadhav wrote:
>
> --
> You received this message because you are subscrib
s that aren't
>> actually a filter.
>>
>
> I would be strong -1 on having a special keyword.
>
Even if the special keyword is 'default'? .get(..., default=None) is a
common python pattern that fits well with this usage.
Regards,
Michael Manfre
--
You received
Good point. I forgot that some people would do that.
On Fri, Mar 14, 2014 at 11:52 AM, Florian Apolloner
wrote:
>
>
> On Friday, March 14, 2014 4:50:49 PM UTC+1, Michael Manfre wrote:
>
>> On Fri, Mar 14, 2014 at 11:15 AM, Cal Leeming [Simplicity Med
pps with django-mssql. I do like the
proposal with an explicit .execute() and think documenting corner cases is
the sane way to proceed.
Regards,
Michael Manfre
[1] http://technet.microsoft.com/en-us/library/ms175528(v=sql.105).aspx
On Tue, Mar 25, 2014 at 10:22 AM, Anssi Kääriäinen
wrote:
>
atement correctly, you are asking for some one to create a
release blocker ticket because taking the position that TDD will be painful
in 1.7 and might improve for 1.8 seems wrong.
Regards,
Michael Manfre
On Tue, Mar 25, 2014 at 4:12 PM, Andrew Godwin wrote:
> So, the functionality whereb
llow PEP 249,
but that would have been a foolish decision.
Regards,
Michael Manfre
[1] http://legacy.python.org/dev/peps/pep-0249/#threadsafety
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group a
I think there would be value in adding DEPs for the major features that
will ship with 1.7.
Regards,
Michael Manfre
On Mon, Apr 14, 2014 at 2:17 PM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> On 14 avr. 2014, at 19:51, Adrian Holovaty wrote:
>
> > One
Are you thinking the next cycle would be 1.7.1 or 1.8?
On Mon, Apr 21, 2014 at 11:35 AM, Andrew Godwin wrote:
> Yes, no matter what it's too late to add anything to 1.7, which is a
> massive shame - we'll have to just heavily document this for now, and then
> investigate the dump/load data stuf
early
not spam and are technically feasible. I'm curious why they have not been
moved along in the process.
I think the DEP concept has a lot of potential, but it's already starting
to have the feel of a bureaucratic barrier that will probably discourage
people from contributing.
Regards,
Mic
e disabled by default and docs
> would say about the extra memory this feature needs.
>
The majority of projects wouldn't use this and it's possible to accomplish
with the existing cache API, so I don't think it makes sense to add this to
Django. This functionality sounds like it
Django that can be run with the rest of the test suite. If
the backend is used, then the test runner would find its tests and run them
if specified, or part of the "run everything" default. This would make the
test suite cleaner in general and also solve the awkwardness I face with
trying
o/deps before it was put in to practice?
3) Django lists over 30 current core developers. Does Django have enough
*active* core developers for its current user base and existing processes?
Is there a process in place for moving an inactive core developer from
"Current Developers" to "Devel
there are enough active core developers. This is a new process that
demands more time of the core team.
Regards,
Michael Manfre
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails
QL
in the schema tests that caused tests to fail for django-mssql. It appears
other non-core backends are also facing these issues.
Regards,
Michael Manfre
[1]
https://github.com/django/django/blob/stable/1.7.x/tests/schema/tests.py#L38
[2]
https://github.com/django/django/blob/stable/1.7.x/djan
th 1.7 by devoting a lot of time and effort trying
to get changes in, but in the end I gave up frustrated. My 1.7 plan is to
wait until it's released and then review schema migrations' growing list of
"we'll fix it later" issues and monkey patch as necessary.
Regards,
M
It was very clearly stated in the other email thread about this, by the no
longer offensively titled BDFL :P, that the rename will not be reverted.
It's nearly impossible to get a change in to core when there is a single
core dev opposed to it and there have been many core devs who are -1 on
revert
Today I learned that the devserver messages are supposed to be in color.
Having all output from Django controlled by logging would be a nice
improvement.
Regards,
Michael Manfre
On Wed, May 28, 2014 at 9:40 PM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
>
> On Wed, May
Each expression must be able to define it's own ordering because order_by
allows you to define a sort based upon multiple expressions.
On Mon, Jun 9, 2014 at 4:00 PM, Daniel Moisset
wrote:
> I see everyone trying to put the direction (ascending vs decending) inside
> the expression, while it's
for 3rd party
backends to flag as not supported or be able to tweak the underlying SQL.
The most likely tweak would be renaming the function to match the specifics
of the database. I have to do this for some of the aggregation functions,
so it's safe to assume that some database might need to do
That ticket seems to address issues with initial_data and not necessarily
deal with fixtures that are loaded for a specific TestCase. I do agree that
we should encourage people to not use fixtures and build their test data
within the scope of the test or the TestCase.
Regards,
Michael manfre
On
The feature was added by Aymeric for django-pymssql, which needs the
feature.
Regards,
Michael Manfre
On Thu, Jun 12, 2014 at 6:17 PM, Shai Berger wrote:
> Hi all,
>
> Bug #22816[1] is a test failure on Oracle. It was caused by the
> introduction
> of the "can_intro
ent". If people
feel strongly about staying on a no longer supported version of Oracle,
then they can either stick with an older version of Django or create
django-decrepit-oracle.
Django should strip this legacy code.
Regards,
Michael Manfre
On Sat, Jun 14, 2014 at 10:01 PM, Alex Gaynor wr
of these introspect features too. I'm not sure whether it makes
more sense to put assertFieldType on DatabaseFeatures or
DatabaseIntrospection.
[1]
https://github.com/django/django/blob/master/tests/inspectdb/tests.py#L36
Regards,
Michael Manfre
>
> >
> > Backwards-compatibi
work for two conflicting needs.
Regards,
Michael Manfre
On Wed, Jun 18, 2014 at 8:31 PM, Josh Smeaton
wrote:
> manfre has raised some issues about registering implementations in IRC. I
> had been assuming that AppConfigs could be used for backends to register
> their changes, but t
backend needs to support those, too.
>
All of the subclasses are going to inherit SQLCompiler.compile and do the
same exact logic. I don't understand what problem is caused by overriding
compile that is solved by a function call to compile on some other class.
Regards,
Michael Manfre
--
each compile. To me, it seems much more elegant to duck type the
nodes as they're being compiled, instead of a giant import and monkey patch
setup function.
Regards,
Michael Manfre
[1] http://docs.sqlalchemy.org/en/rel_0_9/core/compiler.html
On Tue, Jul 1, 2014 at 11:32 AM, Anssi Kääriäine
Python packaging is definitely a lot better than it was and starting to
move the contribs to their own repos and packages would be a good thing to
do.
Regards,
Michael Manfre
On Fri, Jul 11, 2014 at 8:15 PM, Josh Smeaton
wrote:
> I think the "blessed packages" idea is a good one
>
This is also used by 3rd party apps that support multiple versions of
Django with a single code base.
Regards,
Michael Manfre
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receivi
st you could do is generate the SQL from the migrations and manually
apply to the database.
Regards,
Michael Manfre
--
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
On Wed, Aug 6, 2014 at 8:59 PM, Josh Smeaton wrote:
> In that case, is it easy enough to support github oauth + the current trac
> auth concurrently? If a user chooses to go through the harder path, that's
> fine.
>
> I like the idea of using github oauth. Password managers usually have a
> miser
This mailing list is for the development of Django. Please direct questions
about how to use Django to the django-users mailing list.
Regards,
Michael Manfre
On Aug 7, 2014 12:06 PM, "Héctor Urbina" wrote:
> Hello,
>
> I'm developing a django project for my office, a
in
its own test suite.
Regards,
Michael Manfre
On Sun, Aug 17, 2014 at 2:52 AM, Roger Hunwicks
wrote:
> I'm doing some refactoring of a Django app and I want to make sure that I
> don't introduce any really poorly performing pages as a result of poor
> queries.
>
> I wa
On Thu, Aug 28, 2014 at 8:44 AM, Tim Graham wrote:
> I've implemented the ability to register "deployment checks" by adding
> deploy=True to register: @register("tag_name", deploy=True). These checks
> are only run if you pass the --deploy flag to check. So in development you
> can run `manage.py
ld argue it harms
> readability and the use of settings in general unless it's actually
> required.
>
Auto merging dicts is the wrong approach. Staging.py should contain exactly
what it appears to contain, SECURITY_MIDDLEWARE with a single key defined.
If some one needs to tweak one of the valu
n a day for the exact reason
brought up. The visible warnings could state why it is a good idea to
increase the duration, after it is tested in production.
Regards,
Michael Manfre
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To
llowing to provide init kwargs.
MIDDLEWARE_CLASSES = (
'django.middleware.clickjacking.XFrameOptionsMiddleware',
('django.middleware.security.SecurityMiddleware',
{'content_type_nosniff': True, 'xss_filter': True}),
)
Regards,
Michael Manfre
--
You recei
s someone who has used a very large number of stored procedures with
Django, I am a solid -1 on adding a generic "magic" layer to Django. Stored
procedures are purpose built. Their python usage should also be purpose
built to match the various combinations of input/output parameters, return
Having run in to this issue in the past, automatically changing the meaning
and/or breaking the query can turn in to a debug time sink. Option 3 could
save people a bit of time.
Cheers,
Michael Manfre
On Wednesday, October 28, 2020 at 8:46:46 PM UTC-4 charettes wrote:
> I'm also
On Tue, Sep 5, 2017 at 5:10 AM Adam Johnson wrote:
> from django.db.models import FilteredRelation is what I'd expect
>
This is what I'd expect too.
> On 5 September 2017 at 09:44, Nicolas Delaby wrote:
>
>> It seems we have a consensus.
>> I'll be glad to push that change.
>>
>> I just have
as definitely a
lot of fun to tinker on it, but not something I'd ever want to support in
production.
Regards,
Michael Manfre
On Fri, Sep 8, 2017 at 12:57 PM Adam Johnson wrote:
> I agree, I think forcing Django's ORM to work on MongoDB is not a great
> idea. Django relies he
me structure, how much of a safe assumption is this?
>
Every 3rd party database backend adheres to the internal API and must
provide its own or an inherited DatabaseWrapper. Adding config_from_url
seems like the best place to me.
Regards,
Michael Manfre
--
You received this message because you ar
Any improvements to documentation are greatly appreciated. Thank you for
taking the initiative.
Regards,
Michael Manfre
On Mon, Feb 5, 2018, 7:05 AM David Foster wrote:
> This weekend I spent several hours getting Channels configured to run a
> simple chat server <https://github.com/
On Mon, Jul 23, 2018 at 12:12 PM Florian Apolloner
wrote:
> * Any thoughts on asset pipelines?
>
This seems like it would be critical functionality. It might also help
users to avoid potential asset ordering issues without needing to create
more apps to resolve conflicts.
Regards,
M
that
they would likely ignore.
Regards,
Michael Manfre
On Sat, Aug 25, 2018 at 9:12 AM Tim Graham wrote:
> Alex proposed:
>
> ---
>
> Pickle serializer has long been known to be dangerous. This is mitigated
> by requiring MAC on pickle in cookies, but nevertheless, RCEs con
nk we
should improve that. I'm +1 on reopening the ticket to make it easier to
swap in a custom ExceptionReporter for AdminEmailHandler.
Regards,
Michael Manfre
On Mon, Aug 27, 2018 at 9:41 AM wrote:
> Email error reports sent from Django (when DEBUG=False) include
> information abo
This mailing list is for the development of Django itself, not how to use
Django. The mailing list django-users is where you can ask this type of
question, but you will need to make your question a bit more detailed, if
you'd like to get a helpful response.
Regards,
Michael Manfre
On Wed, O
This mailing list is for the development of the Django Framework. Questions
related to its usage should be posted to the django-users mailing list.
Regards,
Michael Manfre
On Fri, Nov 9, 2018 at 6:51 AM wrote:
> Hi all,
>
> I have a very simple Profile class:
>
> class Profi
tabase backend
API, I suggest clearly stating that it will still be exempt from the
standard deprecation policy. There was a lot of strong opposition to
changing that policy in the past.
Regards,
Michael Manfre
--
GPG Fingerprint: 74DE D158 BAD0 EDF8
keybase.io/manfre
--
You received this me
It should be configurable and I like the kwargs idea. I've also had to
monkey patch JSONField in this way for datetimes.
Regards,
Michael Manfre
On Tue, Jan 5, 2016 at 12:48 PM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> > On 5 janv. 2016, at 18:37, To
Agreed with the above for the same reasons.
On Wed, Jan 6, 2016 at 9:17 AM, Shai Berger wrote:
> What Marc and James said, and in particular what Daniele said : I get to
> use Jira on a daily basis and find it cumbersome and confusing.
>
> Shai see
>
>
> On 6 בינואר 2016 15:43:02 GMT+02:00, Marc
to me. Allowing both to be configurable requires a trivial
amount of extra effort to implement and maintain.
Regards,
Michael Manfre
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from t
of my primary
concerns because there are existing production sites that run Django on
Windows.
Regards,
Michael Manfre
On Wed, Jan 27, 2016 at 12:15 AM, Cristiano Coelho wrote:
> I'm interested in the progress of this as well :)
>
> Sorry I didn't read through all the posts, mostly
more
bandwidth starting the end of this month when things are finally settled.
Regards,
Michael Manfre
On Fri, Mar 11, 2016 at 1:54 PM, Tim Graham wrote:
> Yes, I wonder if Microsoft abandoned the idea of providing engineering
> resources to help out projects like django-mssql or if thin
Simple is better. Anyone who needs/wants something more complex is not
prevented by Django from doing so.
Regards,
Michael Manfre
On Mon, Mar 14, 2016 at 2:31 PM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> Indeed, for some reason, the URL and email validators get
ling with HIPAA (and some other compliance regulations) a few
months ago.
Regards,
Michael Manfre
--
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 stop receivin
I can't recall the last Django project I worked on that didn't require
pytz. It makes sense to me to require it.
Regards,
Michael Manfre
On Tue, May 17, 2016 at 6:07 AM Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> The reasoning was based on:
>
>
ase backend, please share them.
Regards,
Michael Manfre
--
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 stop receiving emails from it, send an email
to django-develope
;
I have no strong feelings either for or against it being in the official
Django documentation. I've been wanting to put together a talk about
creating a database backend and that will likely be the first pass at the
documentation.
Regards,
Michael Manfre
--
You received this message becaus
custom User model; bonus points if they make it a reusable app or even a
gist.
Regards,
Michael Manfre
On Mon, Aug 1, 2016 at 9:03 AM James Pic wrote:
> Aymeric, it doesn't matter if tens of milions of names fit into your
> model, it only takes one to have a issue that's goin
Hi Robert,
Thanks for doing this load testing. More context would be useful to help us
outside observers to understand the potentially different variables. Is
redis running locally or are you using elasticache?
Regards,
Michael Manfre
On Mon, Sep 12, 2016 at 9:41 PM Robert Roskam
wrote:
>
, I don't think this is something Django
should officially support for the same reasons mentioned by Marc.
Regards,
Michael Manfre
On Mon, Oct 3, 2016 at 9:44 AM James Pic wrote:
> True, this is a feature that's been invented a countless number of times.
> Perhaps one impleme
nd
> certainly nothing specific to OrderBy. Your proposed syntax is basically
> what would be required `order_by=[ .. ]`.
>
>
We (or anyone) could make an ExpressionList class that is essentially an
Expression that is a list of expressions. It would basically be a
Combinable with com
go.
https://docs.djangoproject.com/en/dev/internals/mailing-lists/#django-users
Regards,
Michael Manfre
On Wed, Nov 30, 2016 at 8:14 AM Reetika Aggarwal <
reetika.aggarwa...@gmail.com> wrote:
> Hi,
> Getting below exception while makingMigrations
>
> django.core.exceptions.ImproperlyConfigur
As some one who maintains django packages, I wouldn't use "django_" and
don't think it should be an official recommendation. I do support
documenting the potential collisions to let package maintainers make a more
informed decision.
On Thu, Dec 8, 2016 at 7:17 AM Adam Johnson wrote:
> +1 (to wha
it as easy as possible for them to do so (e.g.
pre-notification), but not by adding more support burden (conditional code,
build matricies, etc.) to Django or preventing us from using newer features
from Python.
Regards,
Michael Manfre
--
You received this message because you are subscribed to the G
SL sounds somewhat nice, I am -0 to -1 for the debugger --
> I've seen to many sites out there running with DEBUG=True, enabling RCE
> ootb seems to be pretty horrible.
>
I think anyone running devserver in prod deserves a breakpoint induced
outage.
Regards,
Michael Manfre
--
You
atabase backend, check out the
Custom Database Backends talk given at DUTH last year.
Regards,
Michael Manfre
On Sun, Feb 19, 2017 at 8:11 PM wrote:
How do I tell django to use --skip-secure-auth when connecting to mysql?
049, "Connection using old (pre-4.1.1) authentication protocol
101 - 200 of 202 matches
Mail list logo
