I don't know whether it is related, but I had the same issue under Win10. I moved my stuff to Linux, where at first it didn't work either - it took me a few days until I discovered that for permissions reasons, one cannot have the code on a drive with a VFAT file system (I have all my data on a portable memory stick which is easy to carry around and to back up).
Once moved to a EXT4 file system, tox worked great. I didn't try back on Windows, whether that would fix the problem as well.
73 Bernhard
On 12/30/19 5:06 PM, Jim Unroe via chirp_devel wrote:
On Tue, Feb 20, 2018 at 9:27 PM Dan Smith via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
Added serial to tox deps and it gets a bit further, any thoughts? as before UNKNOWN-0.0.0.zp can't be write, and now we have no module named chirp. Is there something to be done with the build first? Thanks. Nicolas
nicolass-Mac-mini:chirp.hg nicolas$ tox -e driver -- -d Icom_IC-2820H GLOB sdist-make: /Users/nicolas/Documents/FT70CHIRP/chirp.hg/setup.py driver inst-nodeps: /Users/nicolas/Documents/FT70CHIRP/chirp.hg/.tox/dist/UNKNOWN-0.0.0.zip ERROR: invocation failed (exit code 1), logfile: /Users/nicolas/Documents/FT70CHIRP/chirp.hg/.tox/driver/log/driver-4.log ERROR: actionid: driver msg: installpkg cmdargs: ['/Users/nicolas/Documents/FT70CHIRP/chirp.hg/.tox/driver/bin/pip', 'install', '-U', '--no-deps', '/Users/nicolas/Documents/FT70CHIRP/chirp.hg/.tox/dist/UNKNOWN-0.0.0.zip']
Processing ./.tox/dist/UNKNOWN-0.0.0.zip Complete output from command python setup.py egg_info: Traceback (most recent call last): File "<string>", line 1, in <module> File "/private/var/folders/yf/rh0gfjk57pzfvdls7z6nwnmr0000gn/T/pip-kuILg4-build/setup.py", line 5, in <module> from chirp import CHIRP_VERSION ImportError: No module named chirp
Yeah, I dunno, sorry. I tried on a mac I had access to and I didn't even get this far. I can try to debug it more later, but no obvious ideas. The UNKNOWN-0.0.0 stuff definitely looks funky to me.
You can still run the driver tests manually by running tests/run_tests, which might be easier for you.
--Dan
This is the same error that is experienced in a DevelopersWin32Environment. What the file should look like is "chirp-0.3.0dev.zip". Not knowing much about it, it seem the CHIRP_VERSION can't be imported because the "module named chirp" is missing or otherwise can't be accessed. Whatever the issue is, it is common to Windows and macOS. I have finally figured out all the steps needed to setup a DevelopersLinuxEnvironment and submitted my first patch using it. I would much rather do it on my Win32 system, though.
Jim _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers