[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#755066: marked as done (Restore Python 3 compatibility and ensure we keep it in the future)

Your message dated Sun, 24 Aug 2014 17:41:02 +0200
with message-id <20140824154102.GA25028@x230-buxy.home.ouaza.com>
and subject line Re: Bug#755066: Restore Python 3 compatibility and ensure we keep it in the future
has caused the Debian Bug report #755066,
regarding Restore Python 3 compatibility and ensure we keep it in the future
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
755066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755066
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: tracker.debian.org
Severity: normal

In its initial development phase, we ensured that the codebase would work
well with Python 3. Unfortunately nobody cared since then and now we have
a lot of failing tests when we run it with Python 3.

There are also a couple of dependencies that are still missing (at least in Debian):
- python3-beautifulsoup
- python3-soappy
- python3-django-debug-toolbar
- python3-django-south (but this will be replaced by Django's native migration in Django 1.7)
- there's no python3-ldap, but there's a python3-ldap3 so maybe we should switch
  to that module as dependency

$ python3 ./manage.py test
Creating test database for alias 'default'...
.........E........EE..........................................F.EEEFE.............................................................................FFFFFFF.FFFF.................................................F........................................................................................................F..F....E.....FF.......E...........................F..F....E......F..F....E.....EEE...........................................................................EE

We should really try to setup tox so that everybody can easily run the tests in
all supported environments. And idealy we should configure jenkins.debian.net
to run the tests for us.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
On Mon, 21 Jul 2014, Raphael Hertzog wrote:
> On Thu, 17 Jul 2014, Raphaël Hertzog wrote:
> > In its initial development phase, we ensured that the codebase would work
> > well with Python 3. Unfortunately nobody cared since then and now we have
> > a lot of failing tests when we run it with Python 3.
> 
> To make it easier to test in the various combinations that we care about,
> I added a tox.ini file so that one can run "tox" after having installed
> python-tox.

All tests are now passing in Python 3. Now we must keep it that way.

$ tox
[...]
  py27-django16: commands succeeded
  py27-django17: commands succeeded
  py34-django16: commands succeeded
  py34-django17: commands succeeded
ERROR:   flake8: commands failed

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Discover the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/

--- End Message ---
Reply to: