[JdeRobot] [jderobot][MavLink-SITL] problem in import "from future import standard_library"

Jose Antonio cbyte18 at gmail.com
Sun Dec 18 18:58:03 CET 2016


I' ve seen too in the future library's web that the standard_library is 
located in the importlib package. But when I do pip3 install importlib 
crashes too

/Traceback (most recent call last):
       File "<string>", line 1, in <module>
       File "/usr/lib/python3/dist-packages/setuptools/__init__.py", 
line 5, in <module>
         import distutils.core
       File "/usr/lib/python3.5/distutils/core.py", line 16, in <module>
         from distutils.dist import Distribution
       File "/usr/lib/python3.5/distutils/dist.py", line 19, in <module>
         from distutils.util import check_environ, strtobool, rfc822_escape
       File "/usr/lib/python3.5/distutils/util.py", line 9, in <module>
         import importlib.util
     ImportError: No module named 'importlib.util'
     Error in sys.excepthook:
     Traceback (most recent call last):
       File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 
63, in apport_excepthook
         from apport.fileutils import likely_packaged, get_recent_crashes
       File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, 
in <module>
         from apport.report import Report
       File "/usr/lib/python3/dist-packages/apport/report.py", line 13, 
in <module>
         import fnmatch, glob, traceback, errno, sys, atexit, locale, imp
       File "/usr/lib/python3.5/imp.py", line 19, in <module>
         from importlib._bootstrap import _ERR_MSG, _exec, _load, 
_builtin_from_name
     ImportError: No module named 'importlib._bootstrap'

     Original exception was:
     Traceback (most recent call last):
       File "<string>", line 1, in <module>
       File "/usr/lib/python3/dist-packages/setuptools/__init__.py", 
line 5, in <module>
         import distutils.core
       File "/usr/lib/python3.5/distutils/core.py", line 16, in <module>
         from distutils.dist import Distribution
       File "/usr/lib/python3.5/distutils/dist.py", line 19, in <module>
         from distutils.util import check_environ, strtobool, rfc822_escape
       File "/usr/lib/python3.5/distutils/util.py", line 9, in <module>
         import importlib.util
     ImportError: No module named 'importlib.util'

     ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in 
/tmp/pip-build-2m9qjc26/importlib//

Thanks


El 18/12/16 a las 18:45, Jose Antonio escribió:
> Hi all,
>
> I'm on install SITL software to emulate a plane which can be operated 
> over MAVLink commands, all the install instruction are here 
> http://ardupilot.org/dev/docs/setting-up-sitl-on-linux.html for anyone 
> interested.
>
> /I had a trouble finished the installation on the first launch.
>
> Waf: Entering directory `/home/josete/ardupilot/build/sitl'
> [4/4] Processing 
> modules/mavlink/message_definitions/v1.0/ardupilotmega.xml
> Traceback (most recent call last):
>   File 
> "/home/josete/ardupilot/modules/mavlink/pymavlink/tools/mavgen.py", 
> line 16, in <module>
>     from pymavlink.generator import mavgen
>   File 
> "/home/josete/ardupilot/modules/mavlink/pymavlink/generator/mavgen.py", 
> line 12, in <module>
>     from future import standard_library
> ImportError: No module named future
>
> mavgen returned 1 error code
> Waf: Leaving directory `/home/josete/ardupilot/build/sitl'
> Build failed
>  -> task in 'mavlink' failed (exit status 1):
>     {task 140126879052096: mavgen ardupilotmega.xml -> }
> ''/
>
> It seems can't do the import " from future import standard_library". 
> Future library is installed and in the last version but for import 
> future y usually use __future__ not future. Searching more information 
> I saw in the future's web http://python-future.org/quickstart.html the 
> import is correct but ¿what can I do to solve the problem?
>
> Thanks a lot 

------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: <http://gsyc.urjc.es/pipermail/jde-developers/attachments/20161218/abe4f6fc/attachment.html>


More information about the Jde-developers mailing list