ImportError: No module named schematics.exceptions

[aquette]

happens for a few days now

Scanning files...
  [------------------------------------]  1  Scanning: .xxx
Scanning done.
Traceback (most recent call last):
  File "/home/arno/Projects/Eaton/BIOS/Legal/scancode-toolkit/bin/scancode", line 9, in <module>
    load_entry_point('scancode-toolkit==1.3.7', 'console_scripts', 'scancode')()
  File "/home/arno/Projects/Eaton/BIOS/Legal/scancode-toolkit/local/lib/python2.7/site-packages/click/core.py", line 664, in __call__
    return self.main(*args, **kwargs)
  File "/home/arno/Projects/Eaton/BIOS/Legal/scancode-toolkit/src/scancode/utils.py", line 61, in main
    standalone_mode=standalone_mode, **extra)
  File "/home/arno/Projects/Eaton/BIOS/Legal/scancode-toolkit/local/lib/python2.7/site-packages/click/core.py", line 644, in main
    rv = self.invoke(ctx)
  File "/home/arno/Projects/Eaton/BIOS/Legal/scancode-toolkit/local/lib/python2.7/site-packages/click/core.py", line 837, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/arno/Projects/Eaton/BIOS/Legal/scancode-toolkit/local/lib/python2.7/site-packages/click/core.py", line 464, in invoke
    return callback(*args, **kwargs)
  File "/home/arno/Projects/Eaton/BIOS/Legal/scancode-toolkit/src/scancode/cli.py", line 248, in scancode
    results = scan(input, copyright, license, package, email, url, info, verbose, quiet)
  File "/home/arno/Projects/Eaton/BIOS/Legal/scancode-toolkit/src/scancode/cli.py", line 315, in scan
    scan_result.update(scan_one(res, scanners))
  File "/home/arno/Projects/Eaton/BIOS/Legal/scancode-toolkit/src/scancode/cli.py", line 332, in scan_one
    scan = scan_func(input_file)
  File "/home/arno/Projects/Eaton/BIOS/Legal/scancode-toolkit/src/scancode/api.py", line 177, in get_package_infos
    from packagedcode.recognize import recognize_packaged_archives
  File "/home/arno/Projects/Eaton/BIOS/Legal/scancode-toolkit/src/packagedcode/__init__.py", line 25, in <module>
    from packagedcode import models
  File "/home/arno/Projects/Eaton/BIOS/Legal/scancode-toolkit/src/packagedcode/models.py", line 32, in <module>
    from schematics.exceptions import StopValidation
ImportError: No module named schematics.exceptions

[pombredanne]

@aquette How did you install ScanCode? It looks like you havce some combo of the devel branch (which is unstable and not yet ready to consumption) and a 1.3.7 version which was never released?

Can you tell me how this was installed? and what happens when you install the stable 1.6.0 release?
https://github.com/nexB/scancode-toolkit/releases/tag/v1.6.0 ?

[aquette]

simple "git clone https://github.com/nexB/scancode-toolkit.git" (so current master) running on a bamboo CI, reproduced on my Debian laptop.
I'll try with the 1.6.0 archive and report back

[aquette]

good with the 1.6.0 archive, scanned as usual. so in between the release and some commit ~ 3 days ago (our CI started to fail around that time)
et merci pour le support super reactif ;)

[pombredanne]

git clone https://github.com/nexB/scancode-toolkit.git gives you the current develop branch which is the default and not a stable branch. You would need to check out the master branch instead

[pombredanne]

@aquette Does this make sense?

[pombredanne]

You wrote:

so in between the release and some commit ~ 3 days ago (our CI started to fail around that time)

This is when I merged in devel the new package branch.... Now something is bugging me: even when using the devel branch things should not fail: Can you tell me which OS/version/architecture you are running?

[aquette]

Indeed makes sense, and sorry for not having checked the default branch on
which I'm sitting ;)

The OS is Debian 8 Jessie on both my laptop and the CI agents.

(sent from my S3... please excuse my brevity)
Le 28 juin 2016 19:01, "Philippe Ombredanne" notifications@github.com a
écrit :

You wrote:

so in between the release and some commit ~ 3 days ago (our CI started to
fail around that time)

This is when I merged in devel the new package branch.... Now something is
bugging me: even when using the devel branch things should not fail: Can
you tell me which OS/version/architecture you are running?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#276 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AA4ObY8HrjIgQzDCbs8DaQbOdKgnf27Wks5qQVOGgaJpZM4JAG_A
.

[pombredanne]

Thanks. Not you are getting me worried that the devel branch may not work on Debian 8.... I will need to run some tests.... But you are saying that if you fetch and install this https://github.com/nexB/scancode-toolkit/releases/tag/v1.6.3 for instance, it will not run correctly on Debian 8?

[pombredanne]

On another note, if you are running scans on each commit, one thing I have been thinking about is to be run scans on the increments only.

[aquette]

hi Philippe,
confirming that switching to the master branch works as expected.
The archive I've tested was scancode-toolkit-1.6.0, not 1.6.3.
I've just retried with the tag v1.6.3 and it fails.
Quickly ramping down, v1.6.2 fails too, v1.6.1 seems to work... So, issue between 1.6.1 and 1.6.2...
If you need me to run some tests on Jessie, don't hesitate to tell me ;)

on the incremental scan, could be cool indeed. We've just running this CI plan once a day for now, and things tend to be moving fast on the code side. So not sure how the incremental feature would behave (i.e. rescan if a file was changed, and not just when new files pop up?!)

[pombredanne]

@aquette Thanks! If you do not mind pasting your failure log here on 1.6.3 that would be really helpful.

[aquette]

sure, here we go:

$ git checkout v1.6.3
La position précédente de HEAD était 10eea0c... New temporary unpublished version 1.6.1
HEAD est maintenant sur 2e271ba... Bump to experimental 1.6.3

$ ./scancode -f html src/ > test.html
Traceback (most recent call last):
  File "/home/arno/Projects/Legal/scancode-toolkit/bin/scancode", line 9, in <module>
    load_entry_point('scancode-toolkit==1.3.7', 'console_scripts', 'scancode')()
  File "/home/arno/Projects/Legal/scancode-toolkit/local/lib/python2.7/site-packages/click/core.py", line 664, in __call__
    return self.main(*args, **kwargs)
  File "/home/arno/Projects/Legal/scancode-toolkit/src/scancode/utils.py", line 61, in main
    standalone_mode=standalone_mode, **extra)
  File "/home/arno/Projects/Legal/scancode-toolkit/local/lib/python2.7/site-packages/click/core.py", line 644, in main
    rv = self.invoke(ctx)
  File "/home/arno/Projects/Legal/scancode-toolkit/local/lib/python2.7/site-packages/click/core.py", line 837, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/arno/Projects/Legal/scancode-toolkit/local/lib/python2.7/site-packages/click/core.py", line 464, in invoke
    return callback(*args, **kwargs)
  File "/home/arno/Projects/Legal/scancode-toolkit/src/scancode/cli.py", line 248, in scancode
    results = scan(input, copyright, license, package, email, url, info, verbose, quiet)
  File "/home/arno/Projects/Legal/scancode-toolkit/src/scancode/cli.py", line 315, in scan
    scan_result.update(scan_one(res, scanners))
  File "/home/arno/Projects/Legal/scancode-toolkit/src/scancode/cli.py", line 332, in scan_one
    scan = scan_func(input_file)
  File "/home/arno/Projects/Legal/scancode-toolkit/src/scancode/api.py", line 177, in get_package_infos
    from packagedcode.recognize import recognize_packaged_archives
  File "/home/arno/Projects/Legal/scancode-toolkit/src/packagedcode/__init__.py", line 25, in <module>
    from packagedcode import models
  File "/home/arno/Projects/Legal/scancode-toolkit/src/packagedcode/models.py", line 32, in <module>
    from schematics.exceptions import StopValidation
ImportError: No module named schematics.exceptions

hope it will help you in identifying the regression or issue.
Sorry for not committing on digging more, don't have enough time and multiplexing a lot already...

[pombredanne]

could you try this right after checking out a branch?
./configure --clean
then you can run scancode as usual?

[pombredanne]

If this works, then you have a short term fix and I know what to do to provide a permanent fix

[aquette]

salut @pombredanne
I've tried with your solution, back to origin/develop branch and doing a "./configure --clean", still fails.
Same for tag v1.6.3. Or did I misunderstand your comment?
For now, I'll stick with using master, and that's good.
I'll let you close the bug once you have the permanent fix.
Thanks again very much for scancode and your platinum support ;)
And all the best from France / Grenoble