Re: [Django] #23446: mysqldb1 is no longer maintained and should not be recommended

2014-10-27 Thread Django 
#23446: mysqldb1 is no longer maintained and should not be recommended
-+-
 Reporter:  frewsxcv |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"b42930e4b7f344256cf5625d8b26c7626a354244"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b42930e4b7f344256cf5625d8b26c7626a354244"
 [1.7.x] Fixed #23446 -- Officially recommended mysqlclient as MySQL driver

 Thanks Corey Farwell for the report and Tim Graham for the review.
 Thanks also to Inada Naoki for creating and maintaining mysqlclient.
 Backport of 7f089ac2e3 from master.
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.f3ff630bcf904af32a2befcd47fec86a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23446: mysqldb1 is no longer maintained and should not be recommended

2014-10-27 Thread Django 
#23446: mysqldb1 is no longer maintained and should not be recommended
-+-
 Reporter:  frewsxcv |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"7f089ac2e3e6a7f4b2b41085a37d35e074fad805"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7f089ac2e3e6a7f4b2b41085a37d35e074fad805"
 Fixed #23446 -- Officially recommended mysqlclient as MySQL driver

 Thanks Corey Farwell for the report and Tim Graham for the review.
 Thanks also to Inada Naoki for creating and maintaining mysqlclient.
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.9765650361bd493dfbcd58612033f7ec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23446: mysqldb1 is no longer maintained and should not be recommended

2014-10-25 Thread Django 
#23446: mysqldb1 is no longer maintained and should not be recommended
-+-
 Reporter:  frewsxcv |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.a857d235a8fdcfd51714f4a07fc6ba19%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23446: mysqldb1 is no longer maintained and should not be recommended

2014-10-25 Thread Django 
#23446: mysqldb1 is no longer maintained and should not be recommended
-+-
 Reporter:  frewsxcv |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

 https://github.com/django/django/pull/3422

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.fbf153a6750c846616a0e4bd28cb2f8c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23446: mysqldb1 is no longer maintained and should not be recommended

2014-09-17 Thread Django 
#23446: mysqldb1 is no longer maintained and should not be recommended
-+-
 Reporter:  frewsxcv |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by streeter):

 * cc: django@… (added)


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.d9216c4c467175fad8c7a16dca978309%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23446: mysqldb1 is no longer maintained and should not be recommended

2014-09-12 Thread Django 
#23446: mysqldb1 is no longer maintained and should not be recommended
-+-
 Reporter:  frewsxcv |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by frewsxcv):

 * cc: frewsxcv (added)


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.dab8a31fbc6c862105709902c5a07821%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23446: mysqldb1 is no longer maintained and should not be recommended

2014-09-09 Thread Django 
#23446: mysqldb1 is no longer maintained and should not be recommended
-+-
 Reporter:  frewsxcv |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by timgraham):

 Test failures are fixed with mysqlclient 1.3.3. As noted on the thread,
 we'll need to drop Python 3.2/MySQL support since the client doesn't
 support it. I wonder if mysqlclient has added support for binary data? If
 so, we can drop the `supports_binary_field` flag (unless it might be
 needed by 3rd party backends). There is also some logic about the minimal
 MySQLdb version in `django.db.backends.mysql.base` which will need to be
 updated. And of course documentation updates are required.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.3ed98a3a50a9c07bc426e212333d8bbc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23446: mysqldb1 is no longer maintained and should not be recommended

2014-09-08 Thread Django 
#23446: mysqldb1 is no longer maintained and should not be recommended
-+-
 Reporter:  frewsxcv |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timgraham):

 * type:  Bug => New feature
 * component:  Documentation => Database layer (models, ORM)
 * stage:  Unreviewed => Accepted


Comment:

 There are some test failures as noted on the mailing list thread that need
 to be fixed before we can switch.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.a2282709d415336e97fd7e4ccd64e0c0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23446: mysqldb1 is no longer maintained and should not be recommended

2014-09-07 Thread Django 
#23446: mysqldb1 is no longer maintained and should not be recommended
---+--
 Reporter:  frewsxcv   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by timgraham):

 There's a thread related to this on the DevelopersMailingList:
 https://groups.google.com/d/topic/django-developers/n-TI8mBcegE/discussion

 Unfortunately, it hasn't gotten many replies. Perhaps you could chime in
 there as that's the place where we'd make this sort of decision.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.b12a1b5f6c4187658d8f5c1ea609914a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23446: mysqldb1 is no longer maintained and should not be recommended

2014-09-07 Thread Django 
#23446: mysqldb1 is no longer maintained and should not be recommended
---+--
 Reporter:  frewsxcv   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Description changed by frewsxcv:

Old description:

> Currently, the [https://docs.djangoproject.com/en/1.7/ref/databases
> /#mysql-db-api-drivers documentation] recommends
> [https://github.com/farcepest/MySQLdb1 mysqldb1]. Here is why this
> recommendation is hurting the community, especially new users using MySQL
> with Django:
>
> * mysqldb1 is not compatible with Python 3
> * mysqldb1 has not had a commit since November 2013 (besides one tox
> commit from January 2014).
> * mysqldb1's author, farcepest, is not addressing any of the GitHub
> issues (and is inactive on GitHub in general)
> * the latest version of mysqldb1, 1.2.5 has a regression from its
> previous version [https://github.com/farcepest/MySQLdb1/issues/45 1]
> [https://github.com/farcepest/MySQLdb1/issues/49 2] and it has not been
> addressed
>
> In an attempt to solve this dilemma, I propose we stop recommending it as
> a MySQL driver in the documentation.
>
> In replace of it, I would like to recommend a fork called
> [https://pypi.python.org/pypi/mysqlclient/1.3.2 mysqlclient]. A diff
> between mysqlclient and mysqldb1 can be found [https://github.com/PyMySQL
> /mysqlclient-python/compare/farcepest:master...master here]. Some of the
> benefits of mysqlclient over mysqldb1:
>
> * mysqlclient supports Python 2.7 and Python 3.x (same as Django)
> * mysqlclient is authored by the same team that authored PyMySQL and much
> more active
>
> If others agree, I would be happy to write the copy in the documentation
> to support this change.

New description:

 Currently, the [https://docs.djangoproject.com/en/1.7/ref/databases
 /#mysql-db-api-drivers documentation] recommends
 [https://github.com/farcepest/MySQLdb1 mysqldb1]. Here is why this
 recommendation is hurting the community, especially new users using MySQL
 with Django:

 * mysqldb1 is not compatible with Python 3
 * mysqldb1 has not had a commit since November 2013 (besides one tox
 commit from January 2014).
 * mysqldb1's author, farcepest, is not addressing any of the GitHub issues
 (and is inactive on GitHub in general)
 * the latest version of mysqldb1, 1.2.5 has a regression from its previous
 version [https://github.com/farcepest/MySQLdb1/issues/45 1]
 [https://github.com/farcepest/MySQLdb1/issues/49 2] and it has not been
 addressed

 In an attempt to solve this dilemma, I propose we stop recommending it as
 a MySQL driver in the documentation.

 In replace of it, I would like to recommend a fork called
 [https://pypi.python.org/pypi/mysqlclient/1.3.2 mysqlclient]. A diff
 between mysqlclient and mysqldb1 can be found [https://github.com/PyMySQL
 /mysqlclient-python/compare/farcepest:master...master here]. Some of the
 benefits of mysqlclient over mysqldb1:

 * mysqlclient supports Python 2.7 and Python 3.x (same as Django)
 * mysqlclient is authored by the same team that authored PyMySQL and much
 more active

 I've used the library for a couple months now and have not run into any
 issues. If others agree, I would be happy to write the copy in the
 documentation to support this change.

--

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.b730213a17edf15bd208671cf3190367%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23446: mysqldb1 is no longer maintained and should not be recommended

2014-09-07 Thread Django 
#23446: mysqldb1 is no longer maintained and should not be recommended
---+--
 Reporter:  frewsxcv   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by frewsxcv):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Old description:

> Currently, the [https://docs.djangoproject.com/en/1.7/ref/databases
> /#mysql-db-api-drivers documentation] recommends
> [https://github.com/farcepest/MySQLdb1 mysqldb1]. Here is why this
> recommendation is hurting the community, especially new users using MySQL
> with Django:
>
> * mysqldb1 is not compatible with Python 3
> * mysqldb1 has not had a commit since November 2013 (besides one tox
> commit from January 2014).
> * mysqldb1's author, farcepest, is not addressing any of the GitHub
> issues (and is inactive on GitHub in general)
> * the latest version of mysqldb1, 1.2.5 has a regression from its
> previous version [https://github.com/farcepest/MySQLdb1/issues/45 1]
> [https://github.com/farcepest/MySQLdb1/issues/49 2] and it has not been
> addressed
>
> In an attempt to solve this dilemma, I propose we stop recommending it as
> a MySQL driver in the documentation.
>
> In replace of it, I would like to recommend a fork called [mysqlclient
> https://pypi.python.org/pypi/mysqlclient/1.3.2]. A diff between
> mysqlclient and mysqldb1 can be found [https://github.com/PyMySQL
> /mysqlclient-python/compare/farcepest:master...master here]. Some of the
> benefits of mysqlclient over mysqldb1:
>
> * mysqlclient supports Python 2.7 and Python 3.x (same as Django)
> * mysqlclient is authored by the same team that authored PyMySQL and much
> more active
>
> If others agree, I would be happy to write the copy in the documentation
> to support this change.

New description:

 Currently, the [https://docs.djangoproject.com/en/1.7/ref/databases
 /#mysql-db-api-drivers documentation] recommends
 [https://github.com/farcepest/MySQLdb1 mysqldb1]. Here is why this
 recommendation is hurting the community, especially new users using MySQL
 with Django:

 * mysqldb1 is not compatible with Python 3
 * mysqldb1 has not had a commit since November 2013 (besides one tox
 commit from January 2014).
 * mysqldb1's author, farcepest, is not addressing any of the GitHub issues
 (and is inactive on GitHub in general)
 * the latest version of mysqldb1, 1.2.5 has a regression from its previous
 version [https://github.com/farcepest/MySQLdb1/issues/45 1]
 [https://github.com/farcepest/MySQLdb1/issues/49 2] and it has not been
 addressed

 In an attempt to solve this dilemma, I propose we stop recommending it as
 a MySQL driver in the documentation.

 In replace of it, I would like to recommend a fork called
 [https://pypi.python.org/pypi/mysqlclient/1.3.2 mysqlclient]. A diff
 between mysqlclient and mysqldb1 can be found [https://github.com/PyMySQL
 /mysqlclient-python/compare/farcepest:master...master here]. Some of the
 benefits of mysqlclient over mysqldb1:

 * mysqlclient supports Python 2.7 and Python 3.x (same as Django)
 * mysqlclient is authored by the same team that authored PyMySQL and much
 more active

 If others agree, I would be happy to write the copy in the documentation
 to support this change.

--

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.a5760f94b346545095e997de63e38af9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.