Techy Things » python

ValueError: invalid mode: 'rU' while trying to load binding.gyp

frank — Fri, 29 Mar 2024 02:49:30 +0000

Traceback (most recent call last):
 File "C:\dev\react-scss-jest-typescript\node_modules\node-gyp\gyp\gyp_main.py", line 51, in 
 sys.exit(gyp.script_main())
 ^^^^^^^^^^^^^^^^^
 File "C:\dev\react-scss-jest-typescript\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 670, in script_main
 return main(sys.argv[1:])
 ^^^^^^^^^^^^^^^^^^
 File "C:\dev\react-scss-jest-typescript\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 662, in main
 return gyp_main(args)
 ^^^^^^^^^^^^^^
 File "C:\dev\react-scss-jest-typescript\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 629, in gyp_main
 [generator, flat_list, targets, data] = Load(
 ^^^^^
 File "C:\dev\react-scss-jest-typescript\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 150, in Load
 result = gyp.input.Load(
 ^^^^^^^^^^^^^^^
 File "C:\dev\react-scss-jest-typescript\node_modules\node-gyp\gyp\pylib\gyp\input.py", line 3021, in Load
 LoadTargetBuildFile(
 File "C:\dev\react-scss-jest-typescript\node_modules\node-gyp\gyp\pylib\gyp\input.py", line 411, in LoadTargetBuildFile
 build_file_data = LoadOneBuildFile(
 ^^^^^^^^^^^^^^^^^
 File "C:\dev\react-scss-jest-typescript\node_modules\node-gyp\gyp\pylib\gyp\input.py", line 239, in LoadOneBuildFile
 build_file_contents = open(build_file_path, "rU").read()
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: invalid mode: 'rU' while trying to load binding.gyp

Solution

Uninstall Python 3.12.X and install an older version like 3.10.X

The U file mode was removed in Python 3.11 because it had no effect so the U can merely be removed.

Python 3.10.11 was tested as working.

The post ValueError: invalid mode: 'rU' while trying to load binding.gyp appeared first on Techy Things.

Could not import runpy module Traceback (most recent call last) "Python-3.9.5/Lib/typing.py", line 21, in import collections SystemError: returned NULL without setting an error generate-posix-vars failed

frank — Thu, 06 May 2021 21:19:32 +0000

Could not import runpy module Traceback (most recent call last): File "Python-3.9.5/Lib/runpy.py", line 15, in import importlib.util File "Python-3.9.5/Lib/importlib/util.py", line 2, in from . import abc File "Python-3.9.5/Lib/importlib/abc.py", line 17, in from typing import Protocol, runtime_checkable File "Python-3.9.5/Lib/typing.py", line 21, in import collections SystemError: returned NULL without setting an error generate-posix-vars failed

Workaround

Compile without --enable-optimizations in the configure step

Solution

Update to gcc 8.1.0

The post Could not import runpy module Traceback (most recent call last) "Python-3.9.5/Lib/typing.py", line 21, in import collections SystemError: returned NULL without setting an error generate-posix-vars failed appeared first on Techy Things.

libfontconfig.so.1: cannot open shared object file: No such file or directory

frank — Fri, 11 Mar 2016 14:27:07 +0000

/usr/lib/node_modules/phantomjs/lib/phantom/bin/phantomjs: error while loading shared libraries: libfontconfig.so.1: cannot open shared object file: No such file or directory

Solution

sudo apt-get install libfontconfig1

The post libfontconfig.so.1: cannot open shared object file: No such file or directory appeared first on Techy Things.

fatal error: libxml/xpath.h: No such file or directory

frank — Thu, 10 Mar 2016 18:51:14 +0000

Running setup.py install for lxml ... error
Complete output from command /usr/bin/python -u -c "import setuptools, tokenize;__file
/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '
all --record /tmp/pip-PDRsRl-record/install-record.txt --single-version-externally-managed
Building lxml version 3.5.0.
Building without Cython.
ERROR: /bin/sh: 1: xslt-config: not found

** make sure the development packages of libxml2 and libxslt are installed **

(...)

/tmp/xmlXPathInit1Dz_M6.c:1:26: fatal error: libxml/xpath.h: No such file or directory

Solution

$> sudo apt-get install libxml2-dev libxslt-dev

The post fatal error: libxml/xpath.h: No such file or directory appeared first on Techy Things.

fatal error: Python.h: No such file or directory

frank — Wed, 09 Mar 2016 23:05:47 +0000

gcc -pthread -fno-strict-aliasing -fwrapv -Wall -Wstrict-prototypes -fPIC -std=c99 -O3 -fomit-frame-pointer -Isrc/ -
r/include/python2.7 -c src/MD2.c -o build/temp.linux-x86_64-2.7/src/MD2.o
src/MD2.c:31:20: fatal error: Python.h: No such file or directory
compilation terminated.
error: command 'gcc' failed with exit status 1

Solution

Debian:
sudo apt-get install python-dev

CentOS:
yum install python-devel

The post fatal error: Python.h: No such file or directory appeared first on Techy Things.

Solved Python error : from django.core.management import execute_manager

frank — Sat, 06 Sep 2014 20:59:17 +0000

Problem

C:\dev\browsershots-psycopg2.git\shotserver\shotserver04>python manage.py syncdb Traceback (most recent call last): File "manage.py", line 26, in from django.core.management import execute_manager ImportError: cannot import name execute_manager

Explanations

execute_manager was deprecated in Django 1.4 as part of the project layout refactor and was removed in 1.6 per the deprecation timeline: https://docs.djangoproject.com/en/1.4/internals/deprecation/#id3

Solution

Use the following layout

if __name__ == "__main__":
    os.environ.setdefault("DJANGO_SETTINGS_MODULE", "{{ project_name }}.settings")

    from django.core.management import execute_from_command_line

    execute_from_command_line(sys.argv)

Note: After you do your fix, you might need to re-install the module with $> sudo python setup.py install

The post Solved Python error : from django.core.management import execute_manager appeared first on Techy Things.