Our main database in my division contains about 150,000 users total - from
across the world. Although the distribution is heavily weighted towards
North America and Europe, we do have a fair amount of Asian schools, and
one from Brazil. Many of these schools also have international students. I
I think this is better directed at a MySQL list. MySQL shouldn't crash, nothing
I see indicates that this is a Django issue.
Of course, it's best if you can reproduce the error. Barring that, you'll get a
much more useful stack trace if you build MySQL with debugging symbols. A quick
look at th
I'm not sure exceeding max_connections is the issue. We have up to 8
executors on each machine and the tests aren't running in parallel, so I
think we wouldn't have more than 8 connections unless running the tests can
open more than 1 connection? Also, we don't expect 8 all executors to all
be
Hi,
> Anyway, it seems that this issue is bound to die in a bikeshedding fest,
> so I’ll leave it there, with my apologies to Brazilian users who will
> remain unable to log into Django-based websites :-(
Please don't let this issue die because we cannot reach consensus between
60, 100, 192 and
Hi everyone,
> Can we consider “update setuptools” to be an adequate resolution for this
> issue?
I realize this is probably not the most substantial argument, but I want to
mention it anyway: Considering Django's popularity, requiring a recent
version of setuptools might be a positive side-eff
Hello,
Django used to create this file dynamically while running tests, but that got
in the way of test parallelization. To avoid race conditions, the git checkout
needs to be treated as readonly when running tests in parallel.
That’s why I switched to committing it to the git repository when I
On Tue, Aug 2, 2016 at 6:14 PM, Tim Graham wrote:
> A similar report was https://code.djangoproject.com/ticket/24761. I'm not
> sure if this is a bug in those install tools or if it's something we should
> try to fix in Django. You can use `git blame
> tests/staticfiles_tests/apps/test/static/test
Thank you Malcolm!
Let's see if we can reach a consensus in a reasonable time.
_
Raony Guimarães Corrêa Do Carmo Lisboa Cardenas
PhD in Bioinformatics
email: raonyguimar...@gmail.com
skype/hangouts: raonyguimaraes
phone: +48 722 148 478
__
hi. IMO vars for django may uses this values inside [MYSQLD], cause
max_connections default is 100
innodb_buffer_pool_instances=8
max_connections=255
you could verify your environment using console command
mysql -u your-user -p[your-password-whit-nospace]
show variables like '%connec%';
show v
On Tue, Aug 02, 2016 at 06:09:00PM +0300, Shai Berger wrote:
> Well, there's one precedent that is quite pertinent here, and that
> is AUTH_USER_MODEL. But a setting for the length of a field in a
> built-in app is problematic because it would imply a migration in
> that app, rather than user apps.
Well, there's one precedent that is quite pertinent here, and that is
AUTH_USER_MODEL. But a setting for the length of a field in a built-in app is
problematic because it would imply a migration in that app, rather than user
apps.
In principle we could write the d.c.auth migration by hand to t
A similar report was https://code.djangoproject.com/ticket/24761. I'm not
sure if this is a bug in those install tools or if it's something we should
try to fix in Django. You can use `git blame
tests/staticfiles_tests/apps/test/static/test/⊗.txt` to find the commit
where the file was introduce
Here you are:
[client]
port= 3306
socket= /var/run/mysqld/mysqld.sock
# Here is entries for some specific programs
# The following values assume you have at least 32M ram
# This was formally known as [safe_mysqld]. Both versions are currently
parsed.
[mysqld_safe]
socket
On 02 Aug 2016, at 14:23, James Pic wrote:
> I understand it can sometimes be hard for you
Indeed, some aspects of this discussion frustrate me and that showed in my
answer. Please accept my apologies for the unwarranted aggressiveness.
On an intellectual level, I understand why it’s more imp
I've opened ticket 26993 to track this -
https://code.djangoproject.com/ticket/26993#ticket
On Friday, 29 July 2016 12:15:43 UTC+1, Raony Guimaraes Corrêa Do Carmo
Lisboa Cardenas wrote:
>
> Hello everyone,
>
> For a long time I was having problems to login to djangopackages.com
> using my gith
I thought about that before I posted. I can't remember seeing any settings
that would also carry db consequences other than adding an app. (Or the db
setting dict itself).
On Tuesday, August 2, 2016, Malcolm Box wrote:
> A setting seems like a dangerous option here, since changing it would
> cau
A setting seems like a dangerous option here, since changing it would cause
a DB migration to be required.
It's not *that* hard for us to find a value and apply it. Any user that
really wanted something different could create their own migration to
change the default - but "leave it to the user" s
I know there's always resistance to adding more settings but this seems
like a candidate for a value in a setting with a sane default that a user
could quickly and easily change.
On Tuesday, August 2, 2016, James Pic wrote:
> Thanks for your reply Aymeric. If I understand correctly the best way
Thanks for your reply Aymeric. If I understand correctly the best way to
approach this, besides increasing the current limits - which I've had to do
myself a few times - is to create a separate app providing a custom model
with an ArrayField for name (sorting) and a migration script, and let time
t
Someone mentioned mysql not supporting nicely string of 255 unicode characters.
2016-08-02 13:42 GMT+02:00 Malcolm Box :
> Hi Aymeric,
>
> I'm sorry that you feel this has devolved to a bikeshedding fest, that
> certainly wasn't my intent, and I'd hate to see this issue die. I think we
> both agre
Hi Aymeric,
I'm sorry that you feel this has devolved to a bikeshedding fest, that
certainly wasn't my intent, and I'd hate to see this issue die. I think we
both agree that supporting people's names is important - which is the main
thing.
To summarise the available options discussed so far:
Sta
Hello Malcolm,
> On 02 Aug 2016, at 10:28, Malcolm Box wrote:
>
> Having read the W3C Q&A carefully, the relevant comment on field lengths is
> "avoid limiting the field size for names in your database".
Indeed. I chose to propose something else because I didn’t want the solution to
depend o
On Tuesday, July 26, 2016 at 11:16:18 PM UTC+2, Aymeric Augustin wrote:
>
>
> Specifically, please explain why this has to live in Django.
Because Django has an implementation which can be extended without
rewritting a whole thing from scratch?
Well... it is your decision about "including batteri
>
>
>> I'm using Buildout and virtualenv with Python 2.7.9.
>>
>>
> and setuptools 25.1.2
>
>
It works with setuptools 17.0, but displays warning:
Getting distribution for 'Django==1.8.14'.
'tests/staticfiles_tests/apps/test/static/test/⊗.txt' not ANSI_X3.4-1968
encodable -- skipping
warning: n
On Tuesday, August 2, 2016 at 12:40:27 PM UTC+2, Marcin Nowak wrote:
>
>
> I'm using Buildout and virtualenv with Python 2.7.9.
>
>
and setuptools 25.1.2
M.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" gro
Hi all,
Here is a file which breaks installation on fresh Debian system:
https://github.com/django/django/blob/master/tests/staticfiles_tests/apps/test/static/test/%E2%8A%97.txt
I'm using Buildout and virtualenv with Python 2.7.9.
The full traceback is:
Traceback (most recent call last):
Fi
Hi Malcolm,
It seen everyone here agree 30 characters is not enough for last names and
this should be changed. I also think 255 characters would cause less
trouble in a sense, cause we wouldn't have to deal with this problem again
until we decide to go full TextField. which is actually the bes
On Monday, 1 August 2016 13:56:55 UTC+1, Aymeric Augustin wrote:
>
> > On 30 Jul 2016, at 23:15, Donald Stufft >
> wrote:
> >
> > See #6 of
> https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/
>
>
> I’m aware of this article. It's a entertaining read but, unlike
28 matches
Mail list logo
