On Wed, Jun 12, 2019 at 4:41 PM Aaron Whitehouse <[email protected]> wrote:
> Ken, > > On Jun 2 2019, at 2:36 pm, Aaron Whitehouse <[email protected]> > wrote: > > > On py2 I cannot get *past* to import even though it's in tox and local > site-packages. This causes all of the functional tests to fail. > > Do we need this on Py2? Isn't it to provide Python 2-equivalent > functionality in Python 3? Can we put the import within a test for Python > version (and then obviously in future move over to using Python 3 > constructs). > > Yes, past.old_div() is used in multiple modules to keep away from py3's > broken division. > > I am still getting this when trying to do ./run-tests on trunk, but I see > you managed to get 0.8.00 out the door -- how did you fix it on your > machine? > > > I did a clean install on a Ubuntu Bionic VM and that worked. > > > I cannot make this work in a clean Bionic install, on my development box > or even the 16.04 docker image. > > I guess we can replace it with an equivalent old_div function in util, but > thought I would check there is not something I am missing that can get this > working. Any suggestions? > > Kind regards, > > Aaron > Aaron, Regrettably, I've managed to get myself back to the same situation, py3 passes but py2 fails with 'past' imports. Not good! I had not installed all of the backend imports, so when I uncommented those and installed them via "pip install -U -r requirements.txt", py27 functional tests broke. I think there is a name conflict somewhere. So, for now, I have one run of py2 that passed unittest and functional, but none sense. Anyone else running into this problem? Did you find a fix? Google seems to be full of unanswered or misleading questions about this! ...Thanks, ...Ken
_______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
