Hello,
I just tidied up this bug. It started off as a Django1.7 bug, then it got
retitled to a Python3 bug.
Then I wondered if maybe I should have cloned it, and retitled the original
back to the original value, and closed it. If you want to refine my
efforts, feel free to do so.
Thanks
Hi,
On Tue, 09 Sep 2014, Brian May wrote:
Can I please get the following change in python-django git?
Add the following to debian/control:
X-Python-Version: = 2.7
This will make backports to stable a lot easier. Otherwise the package
builds fine, but won't install in Python 2.6 is
On 9 September 2014 16:31, Raphael Hertzog hert...@debian.org wrote:
Yes, please commit that on the debian/experimental branch.
Will do that tomorrow.
(Sorry that I lost this in the git conversion.)
Thought I had made the change before. Not loosing my mind after all :-)
Not a problem,
* Josue Ortega josueort...@debian.org.gt, 2014-09-08, 21:21:
When the tests are running the docstrings are displayed in a terminal
pager making impossible run all tests without human interaction to
close the pager. I've found this really annoying if someone wants to
build the package even the
On Tue, Sep 9, 2014 at 4:59 AM, Jakub Wilk jw...@debian.org wrote:
* Josue Ortega josueort...@debian.org.gt, 2014-09-08, 21:21:
When the tests are running the docstrings are displayed in a terminal
pager making impossible run all tests without human interaction to close
the pager. I've found
I'm packaging a Python3-only library, PyMySQL [1], for internal usage,
chiefly using
dh $@ --with python3 --buildsystem=pybuild
This library includes a test suite, in a subdirectory named tests,
within its source tree. This directory gets packaged, installed and
byte-compiled (by the
On Sep 09, 2014, at 06:53 PM, Konstantin Khomoutov wrote:
Having the test suite packaged along with the code looks like having
not much sense to me, so should I try to exclude this subdirectory from
packaging? Is it considered a bad practice?
I'm not sure there's consensus on this, so I will
[Konstantin Khomoutov, 2014-09-09]
This library includes a test suite, in a subdirectory named tests,
within its source tree. This directory gets packaged, installed and
byte-compiled (by the generated postinst script) during the
installation.
Having the test suite packaged along with the
On 9 September 2014 16:53, Konstantin Khomoutov
flatw...@users.sourceforge.net wrote:
Having the test suite packaged along with the code looks like having
not much sense to me, so should I try to exclude this subdirectory from
packaging? Is it considered a bad practice? I don't have much
See:
https://code.djangoproject.com/ticket/22377
http://bugs.mysql.com/bug.php?id=73867
I will wait and see if I get any response to the above bug reports,
otherwise I will upload python-mysql.connector with a fix I gave in the
later bug report.
Think this might have been a problem for
10 matches
Mail list logo