Re: [RFC] Python 3 and MySQL

I've fixed `%(xxx)s` style formatting. I have not changed error switch: https://github.com/PyMySQL/mysqlclient-python/blob/master/_mysql.c#L150 https://github.com/farcepest/MySQLdb1/blob/master/_mysql.c#L180 I'll investigate the problem, but I can't promise any date for fixing it. On Tuesday, S

Re: Two proposals for the Django Code of Conduct.

Hi Kevin, And thanx for responding to my question about the need for such a policy with Django. Last night, as I had not yet had a response from anyone about this question I searched the archives of both django groups looking for any events or circumstances in which the code of conduct was invo

Re: Two proposals for the Django Code of Conduct.

Thanks Russ, I assumed as much, having read https://www.djangoproject.com/conduct/changes/. -- Perhaps Daniele's keynote talk at Djangocon this year, combined with the already very good Django code of condu

Re: The greatest proposal yet: rename this damn group

On Mon, Sep 8, 2014 at 11:24 PM, Carl Meyer wrote: > On 09/08/2014 08:56 AM, Aymeric Augustin wrote: > > 2014-09-08 16:21 GMT+02:00 Thomas Leo > >: > > > > +1 for django-contributors > > > > > > That would be "Django Contributors" since we're talking about changing >

Re: Two proposals for the Django Code of Conduct.

Hi Kevin, Thanks for these suggestions. By way of settings expectations - a patch of this nature has a little more procedural overhead than a normal patch, because it requires a change to our community policies. Regardless of the merit (or otherwise) of a specific proposal, a change to these poli

Re: #20824 - Email-based auth contrib module; some help required

Hi JJ, On Mon, Sep 8, 2014 at 2:26 AM, JJ Zolper wrote: > Hey guys, > > I can only imagine how busy everyone has been with Django 1.7 and getting > that wrapped up with all the great new features it includes. I know I have > been spending a good bit of time updating my work. > > I know Russell s

Re: Bug in django\forms\models.py in _construct_form, line 593?

At this point I think you're in the realm of django-users. This is probably a bug in user code rather than django, and you'll get better help from the django-users mailing list or IRC. At a guess the issue may be related to your views not being threadsafe, so you should show your entire view, an

Re: The greatest proposal yet: rename this damn group

+1 for Django Contributors. This also aligns with all the documentation on djangoproject.com where there is an entire section on 'Contribution'. We even have a "Contributor Licence Agreement'. Atul On 9 September 2014 01:24, Carl Meyer wrote: > On 09/08/2014 08:56 AM, Aymeric Augustin wrote:

Re: Two proposals for the Django Code of Conduct.

If you think you could do it better, maybe you should submit your own version for consideration. I assume that's how the process works. On Mon, Sep 8, 2014 at 11:20 AM, Benjamin Scherrey wrote: > Daniele, > > You're reading me completely wrong. I am not being sarcastic at all. > I'm pointin

Re: [RFC] Python 3 and MySQL

I also don't need python 3.2 support (or even python 3.3 support for that matter) -- 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+unsubsc

Re: Two proposals for the Django Code of Conduct.

Daniele, You're reading me completely wrong. I am not being sarcastic at all. I'm pointing out the absurdity that one style of "code of conduct" inevitably leads to versus another affirmative style which could actually serve it's intended purpose. I'm not against any code - I'm quite specifica

Re: Bug in django\forms\models.py in _construct_form, line 593?

My project is not python 2 compatibile so I've tried to create a minimal project that would reproduce the error, but failed to do so. Turned out the view throwing KeyError was not the problem, at least not by itself. I went back to the original project and started poking at it. Finally I've noti

Re: [RFC] Python 3 and MySQL

I don't think it'd be a problem, but I don't use MySQL or Python 3.2 on a regular basis. On Monday, September 8, 2014 11:19:56 AM UTC-4, Naoki INADA wrote: > > On Mon, Sep 8, 2014 at 11:28 PM, Tim Graham > wrote: > > We'd need mysqlclient to support Python 3.2 (or drop official support > for

Re: [RFC] Python 3 and MySQL

On Monday, September 8, 2014 5:19:56 PM UTC+2, Naoki INADA wrote: > > On Mon, Sep 8, 2014 at 11:28 PM, Tim Graham > wrote: > > We'd need mysqlclient to support Python 3.2 (or drop official support > for > > MySQL/Python 3.2): > > Python 3.3 introduces PEP 393 (Flexible String Representation) a

Re: The greatest proposal yet: rename this damn group

On 09/08/2014 08:56 AM, Aymeric Augustin wrote: > 2014-09-08 16:21 GMT+02:00 Thomas Leo >: > > +1 for django-contributors > > > That would be "Django Contributors" since we're talking about changing > the display name of the group, not its email address. > > It's a

Re: [RFC] Python 3 and MySQL

On Mon, Sep 8, 2014 at 11:28 PM, Tim Graham wrote: > We'd need mysqlclient to support Python 3.2 (or drop official support for > MySQL/Python 3.2): Python 3.3 introduces PEP 393 (Flexible String Representation) and many Unicode API has been changed and deprecated. It also introduce unicode liter

Re: The greatest proposal yet: rename this damn group

2014-09-08 16:21 GMT+02:00 Thomas Leo : > +1 for django-contributors > That would be "Django Contributors" since we're talking about changing the display name of the group, not its email address. It's a good proposal. -- Aymeric. -- You received this message because you are subscribed to the

Re: [RFC] Python 3 and MySQL

We'd need mysqlclient to support Python 3.2 (or drop official support for MySQL/Python 3.2): django.core.exceptions.ImproperlyConfigured: Error loading MySQLdb module: /var/lib/jenkins/workspace/django-selenium/database/mysql/python/python3.2/tests/.env/lib/python3.2/site-packages/_mysql.cpython

Re: The greatest proposal yet: rename this damn group

+1 for django-contributors django-contributors is clearer than django developers. When companies are hiring web developers, they will often title the position "django developer". Usually these companies are not looking for people who "contribute" to the framework, but use the framework to deve

Re: Two proposals for the Django Code of Conduct.

On Mon, Sep 8, 2014, Benjamin Scherrey wrote: >I thought I made my objections pretty clear in my original email but I'll >attempt to be more pedantic about it now. The specific language in the PR >86 is: > >"In addition, violations of this code outside these spaces may affect a >person's ability

Re: [RFC] Python 3 and MySQL

It's great to see us moving forward on this. Thanks to Naoki for all of the work on this! -- 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

Re: [RFC] Python 3 and MySQL

I'll test mysqlclient-python on my staging CI server today. On Monday, September 8, 2014 3:08:41 AM UTC-4, Claude Paroz wrote: > > Le lundi 8 septembre 2014 08:33:39 UTC+2, Naoki INADA a écrit : >> >> >> On Monday, September 8, 2014 2:04:26 PM UTC+9, Naoki INADA wrote: >>> >>> > >>> > Naoki, >>>

Re: [RFC] Python 3 and MySQL

Ohh wow. I also just noticed CyMySQL, which is a fork of PyMySQL with optional C speedups. It seems like a good idea in theory, though it appears to have diverged from PyMySQL a bit. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsu

Re: Two proposals for the Django Code of Conduct.

All, I appreciate the effort you're putting into explaining your arguments. However, the relationship with the original proposal is becoming increasingly unclear. Hopefully by now you've voiced your arguments. I think it's time to let the Code of Conduct committee decide whether to accept the pro

Re: Two proposals for the Django Code of Conduct.

Hi Stephen, No, I'm not saying that at all. I'm saying that the scope of what is apparently being attempted (precisely as stated) cannot be constrained in a manner that is objective or inline with the rest of the inclusionary aspects of the policy. It's already dangerous ground to start enu

Re: The greatest proposal yet: rename this damn group

> > Changing the group display name wouldn't change any links. > > This is the main point, I think. In this thread, and the one linked to by Sam Lai, the main objection was link rot. Despite how strongly this was asserted, this isn't an objection, as renaming a group doesn't change any URLs.

Re: Two proposals for the Django Code of Conduct.

Yeah I agree with Ben; this is one of those highly conservative things that might sound good, but just allow more and more extreme responses to nonconformist behaviour. Every unpleasant system at some point had good intentions, and asked the question, "But why wouldn't you want people to be lik

Re: Two proposals for the Django Code of Conduct.

Turns out there *is* a document detailing enforcement policies and it *does* involve a range of possible responses to violations. https://github.com/django/djangoproject.com/blob/master/templates/conduct/enforcement.html https://www.djangoproject.com/conduct/enforcement-manual/ On Mon, Sep 8, 20

Re: Two proposals for the Django Code of Conduct.

Ben, Just to clarify, it sounds like what you're saying is the following: If there were a member of the django community who (may this never be the case) was harassing members of the django community, but limited their harassment to non-django-specific forums, you would want it to not affect their

Re: Two proposals for the Django Code of Conduct.

I thought I made my objections pretty clear in my original email but I'll attempt to be more pedantic about it now. The specific language in the PR 86 is: "In addition, violations of this code outside these spaces may affect a person's ability to participate within them." for both faq.html and ind

Re: [RFC] Python 3 and MySQL

Le lundi 8 septembre 2014 08:33:39 UTC+2, Naoki INADA a écrit : > > > On Monday, September 8, 2014 2:04:26 PM UTC+9, Naoki INADA wrote: >> >> > >> > Naoki, >> > >> > Are you aware of performance benchmarks comparing your MySQLdb1 fork >> and >> > mysql-connector-python? >> > > I've posted qui