Installation not working on Mac OSX Big Sur

Hi!
I have problem with installation SMD on Mac OSX Big Sur.
ducho@DSs-MacBook-Pro smd % xcode-select -v
xcode-select version 2384
ducho@DSs-MacBook-Pro smd % pip -V
pip 21.2.1 from /usr/local/lib/python3.9/site-packages/pip (python 3.9)
ERROR: Failed building wheel for lxml
Running setup.py clean for lxml
Building wheel for pygame (setup.py) ... error
ERROR: Command errored out with exit status 1:
ducho@DSs-MacBook-Pro smd % pip3 install -r requirements.txt
WARNING: Value for scheme.platlib does not match. Please report this to <https://github.com/pypa/pip/issues/10151>
distutils: /usr/local/lib/python3.9/site-packages
sysconfig<EMAIL_ADDRESS>WARNING: Value for scheme.purelib does not match. Please report this to <https://github.com/pypa/pip/issues/10151>
distutils: /usr/local/lib/python3.9/site-packages
sysconfig<EMAIL_ADDRESS>WARNING: Value for scheme.headers does not match. Please report this to <https://github.com/pypa/pip/issues/10151>
distutils: /usr/local/include/python3.9/UNKNOWN
sysconfig<EMAIL_ADDRESS>WARNING: Value for scheme.scripts does not match. Please report this to <https://github.com/pypa/pip/issues/10151>
distutils: /usr/local/bin
sysconfig<EMAIL_ADDRESS>WARNING: Value for scheme.data does not match. Please report this to <https://github.com/pypa/pip/issues/10151>
distutils: /usr/local
sysconfig<EMAIL_ADDRESS>WARNING: Additional context:
user = False
home = None
root = None
prefix = None
Collecting notify2==0.3.1
  Using cached notify2-0.3.1-py2.py3-none-any.whl (8.0 kB)
Requirement already satisfied: spotipy==2.4.4 in /usr/local/lib/python3.9/site-packages (from -r requirements.txt (line 2)) (2.4.4)
Collecting lyricsgenius==1.4.0
  Using cached lyricsgenius-1.4.0-py3-none-any.whl (13 kB)
Collecting lxml==4.3.3
  Using cached lxml-4.3.3.tar.gz (4.4 MB)
Collecting mutagen==1.41.0
  Using cached mutagen-1.41.0-py3-none-any.whl
Requirement already satisfied: requests==2.21.0 in /usr/local/lib/python3.9/site-packages (from -r requirements.txt (line 6)) (2.21.0)
Collecting moviepy==<IP_ADDRESS>
  Using cached moviepy-<IP_ADDRESS>-py3-none-any.whl
Requirement already satisfied: imageio==2.3.0 in /usr/local/lib/python3.9/site-packages (from -r requirements.txt (line 8)) (2.3.0)
Collecting humanize==0.5.1
  Using cached humanize-0.5.1-py3-none-any.whl
Collecting pygame==1.9.6
  Using cached pygame-1.9.6.tar.gz (3.2 MB)
Requirement already satisfied: youtube_dl==2019.7.30 in /usr/local/lib/python3.9/site-packages (from -r requirements.txt (line 11)) (2019.7.30)
Collecting Flask==0.12.2
  Using cached Flask-0.12.2-py2.py3-none-any.whl (83 kB)
Requirement already satisfied: pytube==9.5.1 in /usr/local/lib/python3.9/site-packages (from -r requirements.txt (line 13)) (9.5.1)
Requirement already satisfied: PyQt5==5.13.0 in /usr/local/lib/python3.9/site-packages (from -r requirements.txt (line 14)) (5.13.0)
Requirement already satisfied: beautifulsoup4==4.6.0 in /usr/local/lib/python3.9/site-packages (from -r requirements.txt (line 15)) (4.6.0)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.9/site-packages (from requests==2.21.0->-r requirements.txt (line 6)) (2021.5.30)
Requirement already satisfied: chardet<3.1.0,>=3.0.2 in /usr/local/lib/python3.9/site-packages (from requests==2.21.0->-r requirements.txt (line 6)) (3.0.4)
Requirement already satisfied: urllib3<1.25,>=1.21.1 in /usr/local/lib/python3.9/site-packages (from requests==2.21.0->-r requirements.txt (line 6)) (1.24.3)
Requirement already satisfied: idna<2.9,>=2.5 in /usr/local/lib/python3.9/site-packages (from requests==2.21.0->-r requirements.txt (line 6)) (2.8)
Requirement already satisfied: decorator<5.0,>=4.0.2 in /usr/local/lib/python3.9/site-packages (from moviepy==<IP_ADDRESS>->-r requirements.txt (line 7)) (4.4.2)
Requirement already satisfied: tqdm<5.0,>=4.11.2 in /usr/local/lib/python3.9/site-packages (from moviepy==<IP_ADDRESS>->-r requirements.txt (line 7)) (4.61.2)
Requirement already satisfied: numpy in /usr/local/lib/python3.9/site-packages (from moviepy==<IP_ADDRESS>->-r requirements.txt (line 7)) (1.21.0)
Requirement already satisfied: pillow in /usr/local/lib/python3.9/site-packages (from imageio==2.3.0->-r requirements.txt (line 8)) (8.3.1)
Requirement already satisfied: click>=2.0 in /usr/local/lib/python3.9/site-packages (from Flask==0.12.2->-r requirements.txt (line 12)) (8.0.1)
Requirement already satisfied: Werkzeug>=0.7 in /usr/local/lib/python3.9/site-packages (from Flask==0.12.2->-r requirements.txt (line 12)) (2.0.1)
Requirement already satisfied: itsdangerous>=0.21 in /usr/local/lib/python3.9/site-packages (from Flask==0.12.2->-r requirements.txt (line 12)) (2.0.1)
Requirement already satisfied: Jinja2>=2.4 in /usr/local/lib/python3.9/site-packages (from Flask==0.12.2->-r requirements.txt (line 12)) (3.0.1)
Requirement already satisfied: PyQt5_sip<13,>=4.19.14 in /usr/local/lib/python3.9/site-packages (from PyQt5==5.13.0->-r requirements.txt (line 14)) (12.9.0)
Requirement already satisfied: MarkupSafe>=2.0 in /usr/local/lib/python3.9/site-packages (from Jinja2>=2.4->Flask==0.12.2->-r requirements.txt (line 12)) (2.0.1)
Building wheels for collected packages: lxml, pygame
  Building wheel for lxml (setup.py) ... error
  ERROR: Command errored out with exit status 1:
   command<EMAIL_ADDRESS>-u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/pip-install-99l1vp5j/lxml_cbfc8b3e1a734519b4414c9fe9d24fde/setup.py'"'"'; __file__='"'"'/private/var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/pip-install-99l1vp5j/lxml_cbfc8b3e1a734519b4414c9fe9d24fde/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /private/var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/pip-wheel-f2rky2sg
       cwd: /private/var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/pip-install-99l1vp5j/lxml_cbfc8b3e1a734519b4414c9fe9d24fde/
  Complete output (146 lines):
  Building lxml version 4.3.3.
  Building without Cython.
  Using build configuration of libxslt 1.1.29
  Building against libxml2/libxslt in the following directory: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.macosx-11-x86_64-3.9
  creating build/lib.macosx-11-x86_64-3.9/lxml
  copying src/lxml/_elementpath.py -> build/lib.macosx-11-x86_64-3.9/lxml
  copying src/lxml/sax.py -> build/lib.macosx-11-x86_64-3.9/lxml
  copying src/lxml/pyclasslookup.py -> build/lib.macosx-11-x86_64-3.9/lxml
  copying src/lxml/__init__.py -> build/lib.macosx-11-x86_64-3.9/lxml
  copying src/lxml/builder.py -> build/lib.macosx-11-x86_64-3.9/lxml
  copying src/lxml/doctestcompare.py -> build/lib.macosx-11-x86_64-3.9/lxml
  copying src/lxml/usedoctest.py -> build/lib.macosx-11-x86_64-3.9/lxml
  copying src/lxml/cssselect.py -> build/lib.macosx-11-x86_64-3.9/lxml
  copying src/lxml/ElementInclude.py -> build/lib.macosx-11-x86_64-3.9/lxml
  creating build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/__init__.py -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  creating build/lib.macosx-11-x86_64-3.9/lxml/html
  copying src/lxml/html/soupparser.py -> build/lib.macosx-11-x86_64-3.9/lxml/html
  copying src/lxml/html/defs.py -> build/lib.macosx-11-x86_64-3.9/lxml/html
  copying src/lxml/html/_setmixin.py -> build/lib.macosx-11-x86_64-3.9/lxml/html
  copying src/lxml/html/clean.py -> build/lib.macosx-11-x86_64-3.9/lxml/html
  copying src/lxml/html/_diffcommand.py -> build/lib.macosx-11-x86_64-3.9/lxml/html
  copying src/lxml/html/html5parser.py -> build/lib.macosx-11-x86_64-3.9/lxml/html
  copying src/lxml/html/__init__.py -> build/lib.macosx-11-x86_64-3.9/lxml/html
  copying src/lxml/html/formfill.py -> build/lib.macosx-11-x86_64-3.9/lxml/html
  copying src/lxml/html/builder.py -> build/lib.macosx-11-x86_64-3.9/lxml/html
  copying src/lxml/html/ElementSoup.py -> build/lib.macosx-11-x86_64-3.9/lxml/html
  copying src/lxml/html/_html5builder.py -> build/lib.macosx-11-x86_64-3.9/lxml/html
  copying src/lxml/html/usedoctest.py -> build/lib.macosx-11-x86_64-3.9/lxml/html
  copying src/lxml/html/diff.py -> build/lib.macosx-11-x86_64-3.9/lxml/html
  creating build/lib.macosx-11-x86_64-3.9/lxml/isoschematron
  copying src/lxml/isoschematron/__init__.py -> build/lib.macosx-11-x86_64-3.9/lxml/isoschematron
  copying src/lxml/etree.h -> build/lib.macosx-11-x86_64-3.9/lxml
  copying src/lxml/etree_api.h -> build/lib.macosx-11-x86_64-3.9/lxml
  copying src/lxml/lxml.etree.h -> build/lib.macosx-11-x86_64-3.9/lxml
  copying src/lxml/lxml.etree_api.h -> build/lib.macosx-11-x86_64-3.9/lxml
  copying src/lxml/includes/xmlerror.pxd -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/c14n.pxd -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/xmlschema.pxd -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/__init__.pxd -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/schematron.pxd -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/tree.pxd -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/uri.pxd -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/etreepublic.pxd -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/xpath.pxd -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/htmlparser.pxd -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/xslt.pxd -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/config.pxd -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/xmlparser.pxd -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/xinclude.pxd -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/dtdvalid.pxd -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/relaxng.pxd -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/lxml-version.h -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  copying src/lxml/includes/etree_defs.h -> build/lib.macosx-11-x86_64-3.9/lxml/includes
  creating build/lib.macosx-11-x86_64-3.9/lxml/isoschematron/resources
  creating build/lib.macosx-11-x86_64-3.9/lxml/isoschematron/resources/rng
  copying src/lxml/isoschematron/resources/rng/iso-schematron.rng -> build/lib.macosx-11-x86_64-3.9/lxml/isoschematron/resources/rng
  creating build/lib.macosx-11-x86_64-3.9/lxml/isoschematron/resources/xsl
  copying src/lxml/isoschematron/resources/xsl/XSD2Schtrn.xsl -> build/lib.macosx-11-x86_64-3.9/lxml/isoschematron/resources/xsl
  copying src/lxml/isoschematron/resources/xsl/RNG2Schtrn.xsl -> build/lib.macosx-11-x86_64-3.9/lxml/isoschematron/resources/xsl
  creating build/lib.macosx-11-x86_64-3.9/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
  copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_abstract_expand.xsl -> build/lib.macosx-11-x86_64-3.9/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
  copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_dsdl_include.xsl -> build/lib.macosx-11-x86_64-3.9/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
  copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_schematron_skeleton_for_xslt1.xsl -> build/lib.macosx-11-x86_64-3.9/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
  copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_svrl_for_xslt1.xsl -> build/lib.macosx-11-x86_64-3.9/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
  copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_schematron_message.xsl -> build/lib.macosx-11-x86_64-3.9/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
  copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/readme.txt -> build/lib.macosx-11-x86_64-3.9/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
  running build_ext
  building 'lxml.etree' extension
  creating build/temp.macosx-11-x86_64-3.9
  creating build/temp.macosx-11-x86_64-3.9/src
  creating build/temp.macosx-11-x86_64-3.9/src/lxml
  clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk -DCYTHON_CLINE_IN_TRACEBACK=0 -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include -Isrc -Isrc/lxml/includes -I/usr/local/include<EMAIL_ADDRESS>-I/usr/local/opt/sqlite/include<EMAIL_ADDRESS>-c src/lxml/etree.c -o build/temp.macosx-11-x86_64-3.9/src/lxml/etree.o -w -flat_namespace
  src/lxml/etree.c:231155:33: error: no member named 'tp_print' in 'struct _typeobject'
    __pyx_type_4lxml_5etree_Error.tp_print = 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231163:37: error: no member named 'tp_print' in 'struct _typeobject'
    __pyx_type_4lxml_5etree_LxmlError.tp_print = 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231171:37: error: no member named 'tp_print' in 'struct _typeobject'
    __pyx_type_4lxml_5etree_C14NError.tp_print = 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231181:38: error: no member named 'tp_print' in 'struct _typeobject'
    __pyx_type_4lxml_5etree__TempStore.tp_print = 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231194:45: error: no member named 'tp_print' in 'struct _typeobject'
    __pyx_type_4lxml_5etree__ExceptionContext.tp_print = 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231204:37: error: no member named 'tp_print' in 'struct _typeobject'
    __pyx_type_4lxml_5etree__LogEntry.tp_print = 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231219:41: error: no member named 'tp_print' in 'struct _typeobject'
    __pyx_type_4lxml_5etree__BaseErrorLog.tp_print = 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231231:41: error: no member named 'tp_print' in 'struct _typeobject'
    __pyx_type_4lxml_5etree__ListErrorLog.tp_print = 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231242:44: error: no member named 'tp_print' in 'struct _typeobject'
    __pyx_type_4lxml_5etree__ErrorLogContext.tp_print = 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231258:37: error: no member named 'tp_print' in 'struct _typeobject'
    __pyx_type_4lxml_5etree__ErrorLog.tp_print = 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231270:43: error: no member named 'tp_print' in 'struct _typeobject'
    __pyx_type_4lxml_5etree__DomainErrorLog.tp_print = 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231282:45: error: no member named 'tp_print' in 'struct _typeobject'
    __pyx_type_4lxml_5etree__RotatingErrorLog.tp_print = 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231295:38: error: no member named 'tp_print' in 'struct _typeobject'
    __pyx_type_4lxml_5etree_PyErrorLog.tp_print = 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231312:20: error: no member named 'tp_print' in 'struct _typeobject'
    LxmlDocumentType.tp_print = 0;
    ~~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231322:35: error: no member named 'tp_print' in 'struct _typeobject'
    __pyx_type_4lxml_5etree_DocInfo.tp_print = 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231330:19: error: no member named 'tp_print' in 'struct _typeobject'
    LxmlElementType.tp_print = 0;
    ~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231410:48: error: no member named 'tp_print' in 'struct _typeobject'
    __pyx_type_4lxml_5etree___ContentOnlyElement.tp_print = 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231450:36: error: no member named 'tp_print' in 'struct _typeobject'
    __pyx_type_4lxml_5etree__Comment.tp_print = 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
  src/lxml/etree.c:231461:50: error: no member named 'tp_print' in 'struct _typeobject'
    __pyx_type_4lxml_5etree__ProcessingInstruction.tp_print = 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
  fatal error: too many errors emitted, stopping now [-ferror-limit=]
  20 errors generated.
  Compile failed: command '/usr/bin/clang' failed with exit code 1
  creating var
  creating var/folders
  creating var/folders/87
  creating var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn
  creating var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T
  cc -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include -I/usr/include/libxml2 -c /var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/xmlXPathInitjsadwtm9.c -o var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/xmlXPathInitjsadwtm9.o
  cc var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/xmlXPathInitjsadwtm9.o -L/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib -lxml2 -o a.out
  error: command '/usr/bin/clang' failed with exit code 1
  ----------------------------------------
  ERROR: Failed building wheel for lxml
  Running setup.py clean for lxml
  Building wheel for pygame (setup.py) ... error
  ERROR: Command errored out with exit status 1:
   command<EMAIL_ADDRESS>-u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/pip-install-99l1vp5j/pygame_5ca8188a50984e97bae7d1a7ecc3ce3c/setup.py'"'"'; __file__='"'"'/private/var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/pip-install-99l1vp5j/pygame_5ca8188a50984e97bae7d1a7ecc3ce3c/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /private/var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/pip-wheel-9qa62yea
       cwd: /private/var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/pip-install-99l1vp5j/pygame_5ca8188a50984e97bae7d1a7ecc3ce3c/
  Complete output (218 lines):
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.macosx-11-x86_64-3.9
  creating build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/surfarray.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/sysfont.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/_camera_vidcapture.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/sndarray.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/version.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/compat.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/draw_py.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/colordict.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/ftfont.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/midi.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/cursors.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/font.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/_numpysndarray.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/sprite.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/macosx.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/_numpysurfarray.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/camera.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/freetype.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/_camera_opencv_highgui.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/pkgdata.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/locals.py -> build/lib.macosx-11-x86_64-3.9/pygame
  copying src_py/_dummybackend.py -> build/lib.macosx-11-x86_64-3.9/pygame
  creating build/lib.macosx-11-x86_64-3.9/pygame/threads
  copying src_py/threads/Py25Queue.py -> build/lib.macosx-11-x86_64-3.9/pygame/threads
  copying src_py/threads/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/threads
  creating build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/base_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/font_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/mixer_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/rwobject_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/pixelcopy_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/overlay_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/scrap_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/touch_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/imageext_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/pixelarray_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/draw_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/transform_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/blit_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/bufferproxy_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/surfarray_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/mouse_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/surfarray_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/event_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/imageext_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/sprite_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/touch_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/gfxdraw_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/rect_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/scrap_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/overlay_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/color_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/camera_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/surflock_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/key_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/sysfont_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/font_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/mixer_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/constants_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/mixer_music_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/sndarray_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/image_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/version_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/freetype_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/joystick_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/midi_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/ftfont_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/image__save_gl_surface_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/cdrom_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/cursors_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/fastevent_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/display_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/fastevent_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/compat_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/ftfont_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/cdrom_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/mask_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/midi_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/freetype_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/math_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/time_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/image_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/threads_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/__main__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/mixer_music_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/sndarray_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/test_test_.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  copying test/surface_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
  creating build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
  copying test/test_utils/run_tests.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
  copying test/test_utils/endian.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
  copying test/test_utils/test_machinery.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
  copying test/test_utils/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
  copying test/test_utils/png.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
  copying test/test_utils/test_runner.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
  copying test/test_utils/arrinter.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
  copying test/test_utils/buftools.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
  copying test/test_utils/async_sub.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
  creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests
  copying test/run_tests__tests/run_tests__test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests
  copying test/run_tests__tests/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests
  creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
  copying test/run_tests__tests/all_ok/fake_3_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
  copying test/run_tests__tests/all_ok/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
  copying test/run_tests__tests/all_ok/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
  copying test/run_tests__tests/all_ok/fake_4_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
  copying test/run_tests__tests/all_ok/fake_5_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
  copying test/run_tests__tests/all_ok/no_assertions__ret_code_of_1__test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
  copying test/run_tests__tests/all_ok/zero_tests_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
  copying test/run_tests__tests/all_ok/fake_6_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
  creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/failures1
  copying test/run_tests__tests/failures1/fake_3_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/failures1
  copying test/run_tests__tests/failures1/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/failures1
  copying test/run_tests__tests/failures1/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/failures1
  copying test/run_tests__tests/failures1/fake_4_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/failures1
  creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/incomplete
  copying test/run_tests__tests/incomplete/fake_3_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/incomplete
  copying test/run_tests__tests/incomplete/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/incomplete
  copying test/run_tests__tests/incomplete/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/incomplete
  creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/infinite_loop
  copying test/run_tests__tests/infinite_loop/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/infinite_loop
  copying test/run_tests__tests/infinite_loop/fake_1_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/infinite_loop
  copying test/run_tests__tests/infinite_loop/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/infinite_loop
  creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stderr
  copying test/run_tests__tests/print_stderr/fake_3_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stderr
  copying test/run_tests__tests/print_stderr/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stderr
  copying test/run_tests__tests/print_stderr/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stderr
  copying test/run_tests__tests/print_stderr/fake_4_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stderr
  creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stdout
  copying test/run_tests__tests/print_stdout/fake_3_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stdout
  copying test/run_tests__tests/print_stdout/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stdout
  copying test/run_tests__tests/print_stdout/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stdout
  copying test/run_tests__tests/print_stdout/fake_4_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stdout
  creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/incomplete_todo
  copying test/run_tests__tests/incomplete_todo/fake_3_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/incomplete_todo
  copying test/run_tests__tests/incomplete_todo/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/incomplete_todo
  copying test/run_tests__tests/incomplete_todo/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/incomplete_todo
  creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/exclude
  copying test/run_tests__tests/exclude/magic_tag_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/exclude
  copying test/run_tests__tests/exclude/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/exclude
  copying test/run_tests__tests/exclude/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/exclude
  copying test/run_tests__tests/exclude/invisible_tag_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/exclude
  creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/timeout
  copying test/run_tests__tests/timeout/sleep_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/timeout
  copying test/run_tests__tests/timeout/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/timeout
  copying test/run_tests__tests/timeout/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/timeout
  creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/everything
  copying test/run_tests__tests/everything/sleep_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/everything
  copying test/run_tests__tests/everything/magic_tag_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/everything
  copying test/run_tests__tests/everything/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/everything
  copying test/run_tests__tests/everything/incomplete_todo_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/everything
  copying test/run_tests__tests/everything/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/everything
  creating build/lib.macosx-11-x86_64-3.9/pygame/docs
  copying docs/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/docs
  copying docs/__main__.py -> build/lib.macosx-11-x86_64-3.9/pygame/docs
  creating build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/playmus.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/mask.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/sound.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/overlay.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/aacircle.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/chimp.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/liquid.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/audiocapture.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/sound_array_demos.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/midi.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/scroll.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/cursors.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/moveit.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/blit_blends.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/testsprite.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/textinput.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/vgrade.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/arraydemo.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/stars.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/camera.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/blend_fill.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/fonty.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/headless_no_windows_needed.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/fastevents.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/prevent_display_stretching.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/glcube.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/aliens.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/freetype_misc.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/scaletest.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/video.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/eventlist.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/scrap_clipboard.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/oldalien.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/pixelarray.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  copying examples/dropevent.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
  running build_ext
  building 'pygame.gfxdraw' extension
  creating build/temp.macosx-11-x86_64-3.9
  creating build/temp.macosx-11-x86_64-3.9/src_c
  creating build/temp.macosx-11-x86_64-3.9/src_c/SDL_gfx
  clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk -DENABLE_NEWBUF=1 -I/NEED_INC_PATH_FIX -I/usr/local/include<EMAIL_ADDRESS>-I/usr/local/opt/sqlite/include<EMAIL_ADDRESS>-c src_c/SDL_gfx/SDL_gfxPrimitives.c -o build/temp.macosx-11-x86_64-3.9/src_c/SDL_gfx/SDL_gfxPrimitives.o
  In file included from src_c/SDL_gfx/SDL_gfxPrimitives.c:14:
  src_c/SDL_gfx/SDL_gfxPrimitives.h:17:10: fatal error: 'SDL.h' file not found
  #include "SDL.h"
           ^~~~~~~
  1 error generated.
  ---
  For help with compilation see:
      https://www.pygame.org/wiki/MacCompile
  To contribute to pygame development see:
      https://www.pygame.org/contribute.html
  ---
  error: command '/usr/bin/clang' failed with exit code 1
  ----------------------------------------
  ERROR: Failed building wheel for pygame
  Running setup.py clean for pygame
Failed to build lxml pygame
Installing collected packages: pygame, notify2, mutagen, moviepy, lyricsgenius, lxml, humanize, Flask
  WARNING: Value for scheme.headers does not match. Please report this to <https://github.com/pypa/pip/issues/10151>
  distutils: /usr/local/include/python3.9/pygame
  sysconfig<EMAIL_ADDRESS>    Running setup.py install for pygame ... error
    ERROR: Command errored out with exit status 1:
     command<EMAIL_ADDRESS>-u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/pip-install-99l1vp5j/pygame_5ca8188a50984e97bae7d1a7ecc3ce3c/setup.py'"'"'; __file__='"'"'/private/var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/pip-install-99l1vp5j/pygame_5ca8188a50984e97bae7d1a7ecc3ce3c/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /private/var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/pip-record-td10c6a_/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/include/python3.9/pygame
         cwd: /private/var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/pip-install-99l1vp5j/pygame_5ca8188a50984e97bae7d1a7ecc3ce3c/
    Complete output (218 lines):
    running install
    running build
    running build_py
    creating build
    creating build/lib.macosx-11-x86_64-3.9
    creating build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/surfarray.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/sysfont.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/_camera_vidcapture.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/sndarray.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/version.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/compat.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/draw_py.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/colordict.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/ftfont.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/midi.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/cursors.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/font.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/_numpysndarray.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/sprite.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/macosx.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/_numpysurfarray.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/camera.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/freetype.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/_camera_opencv_highgui.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/pkgdata.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/locals.py -> build/lib.macosx-11-x86_64-3.9/pygame
    copying src_py/_dummybackend.py -> build/lib.macosx-11-x86_64-3.9/pygame
    creating build/lib.macosx-11-x86_64-3.9/pygame/threads
    copying src_py/threads/Py25Queue.py -> build/lib.macosx-11-x86_64-3.9/pygame/threads
    copying src_py/threads/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/threads
    creating build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/base_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/font_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/mixer_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/rwobject_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/pixelcopy_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/overlay_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/scrap_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/touch_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/imageext_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/pixelarray_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/draw_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/transform_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/blit_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/bufferproxy_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/surfarray_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/mouse_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/surfarray_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/event_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/imageext_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/sprite_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/touch_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/gfxdraw_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/rect_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/scrap_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/overlay_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/color_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/camera_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/surflock_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/key_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/sysfont_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/font_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/mixer_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/constants_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/mixer_music_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/sndarray_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/image_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/version_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/freetype_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/joystick_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/midi_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/ftfont_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/image__save_gl_surface_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/cdrom_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/cursors_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/fastevent_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/display_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/fastevent_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/compat_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/ftfont_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/cdrom_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/mask_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/midi_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/freetype_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/math_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/time_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/image_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/threads_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/__main__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/mixer_music_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/sndarray_tags.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/test_test_.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    copying test/surface_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests
    creating build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
    copying test/test_utils/run_tests.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
    copying test/test_utils/endian.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
    copying test/test_utils/test_machinery.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
    copying test/test_utils/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
    copying test/test_utils/png.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
    copying test/test_utils/test_runner.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
    copying test/test_utils/arrinter.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
    copying test/test_utils/buftools.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
    copying test/test_utils/async_sub.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/test_utils
    creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests
    copying test/run_tests__tests/run_tests__test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests
    copying test/run_tests__tests/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests
    creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
    copying test/run_tests__tests/all_ok/fake_3_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
    copying test/run_tests__tests/all_ok/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
    copying test/run_tests__tests/all_ok/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
    copying test/run_tests__tests/all_ok/fake_4_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
    copying test/run_tests__tests/all_ok/fake_5_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
    copying test/run_tests__tests/all_ok/no_assertions__ret_code_of_1__test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
    copying test/run_tests__tests/all_ok/zero_tests_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
    copying test/run_tests__tests/all_ok/fake_6_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/all_ok
    creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/failures1
    copying test/run_tests__tests/failures1/fake_3_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/failures1
    copying test/run_tests__tests/failures1/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/failures1
    copying test/run_tests__tests/failures1/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/failures1
    copying test/run_tests__tests/failures1/fake_4_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/failures1
    creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/incomplete
    copying test/run_tests__tests/incomplete/fake_3_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/incomplete
    copying test/run_tests__tests/incomplete/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/incomplete
    copying test/run_tests__tests/incomplete/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/incomplete
    creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/infinite_loop
    copying test/run_tests__tests/infinite_loop/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/infinite_loop
    copying test/run_tests__tests/infinite_loop/fake_1_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/infinite_loop
    copying test/run_tests__tests/infinite_loop/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/infinite_loop
    creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stderr
    copying test/run_tests__tests/print_stderr/fake_3_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stderr
    copying test/run_tests__tests/print_stderr/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stderr
    copying test/run_tests__tests/print_stderr/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stderr
    copying test/run_tests__tests/print_stderr/fake_4_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stderr
    creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stdout
    copying test/run_tests__tests/print_stdout/fake_3_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stdout
    copying test/run_tests__tests/print_stdout/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stdout
    copying test/run_tests__tests/print_stdout/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stdout
    copying test/run_tests__tests/print_stdout/fake_4_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/print_stdout
    creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/incomplete_todo
    copying test/run_tests__tests/incomplete_todo/fake_3_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/incomplete_todo
    copying test/run_tests__tests/incomplete_todo/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/incomplete_todo
    copying test/run_tests__tests/incomplete_todo/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/incomplete_todo
    creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/exclude
    copying test/run_tests__tests/exclude/magic_tag_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/exclude
    copying test/run_tests__tests/exclude/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/exclude
    copying test/run_tests__tests/exclude/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/exclude
    copying test/run_tests__tests/exclude/invisible_tag_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/exclude
    creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/timeout
    copying test/run_tests__tests/timeout/sleep_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/timeout
    copying test/run_tests__tests/timeout/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/timeout
    copying test/run_tests__tests/timeout/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/timeout
    creating build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/everything
    copying test/run_tests__tests/everything/sleep_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/everything
    copying test/run_tests__tests/everything/magic_tag_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/everything
    copying test/run_tests__tests/everything/fake_2_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/everything
    copying test/run_tests__tests/everything/incomplete_todo_test.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/everything
    copying test/run_tests__tests/everything/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/tests/run_tests__tests/everything
    creating build/lib.macosx-11-x86_64-3.9/pygame/docs
    copying docs/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/docs
    copying docs/__main__.py -> build/lib.macosx-11-x86_64-3.9/pygame/docs
    creating build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/playmus.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/mask.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/sound.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/overlay.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/aacircle.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/chimp.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/liquid.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/audiocapture.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/sound_array_demos.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/midi.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/scroll.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/cursors.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/moveit.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/__init__.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/blit_blends.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/testsprite.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/textinput.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/vgrade.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/arraydemo.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/stars.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/camera.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/blend_fill.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/fonty.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/headless_no_windows_needed.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/fastevents.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/prevent_display_stretching.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/glcube.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/aliens.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/freetype_misc.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/scaletest.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/video.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/eventlist.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/scrap_clipboard.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/oldalien.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/pixelarray.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    copying examples/dropevent.py -> build/lib.macosx-11-x86_64-3.9/pygame/examples
    running build_ext
    building 'pygame.gfxdraw' extension
    creating build/temp.macosx-11-x86_64-3.9
    creating build/temp.macosx-11-x86_64-3.9/src_c
    creating build/temp.macosx-11-x86_64-3.9/src_c/SDL_gfx
    clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk -DENABLE_NEWBUF=1 -I/NEED_INC_PATH_FIX -I/usr/local/include<EMAIL_ADDRESS>-I/usr/local/opt/sqlite/include<EMAIL_ADDRESS>-c src_c/SDL_gfx/SDL_gfxPrimitives.c -o build/temp.macosx-11-x86_64-3.9/src_c/SDL_gfx/SDL_gfxPrimitives.o
    In file included from src_c/SDL_gfx/SDL_gfxPrimitives.c:14:
    src_c/SDL_gfx/SDL_gfxPrimitives.h:17:10: fatal error: 'SDL.h' file not found
    #include "SDL.h"
             ^~~~~~~
    1 error generated.
    ---
    For help with compilation see:
        https://www.pygame.org/wiki/MacCompile
    To contribute to pygame development see:
        https://www.pygame.org/contribute.html
    ---
    error: command '/usr/bin/clang' failed with exit code 1
    ----------------------------------------
ERROR: Command errored out with exit status 1<EMAIL_ADDRESS>-u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/pip-install-99l1vp5j/pygame_5ca8188a50984e97bae7d1a7ecc3ce3c/setup.py'"'"'; __file__='"'"'/private/var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/pip-install-99l1vp5j/pygame_5ca8188a50984e97bae7d1a7ecc3ce3c/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /private/var/folders/87/6l726q2x6bg_sc6p99hq8px00000gn/T/pip-record-td10c6a_/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/include/python3.9/pygame Check the logs for full command output.```

Troubleshooting Spotify Music Downloader installation on macOS Big Sur
Hi there,
I understand you're facing issues while installing SMD on your Mac running Big Sur. Here are some steps you can try to troubleshoot the error:
1. Install Xcode Command Line Tools:

Open a terminal window.
Run the following command:

xcode-select --install

Follow the on-screen prompts to install the Xcode Command Line Tools if they are not already installed.

2. Reinstall or upgrade libxml2 and libxslt:
These libraries are dependencies for lxml and might be causing the build failure. Try reinstalling or upgrading them using Homebrew:
brew install libxml2 libxslt

3. Ensure you have the correct Python version:
SMD might have specific Python version requirements. Check the project's documentation or GitHub repository to confirm the supported Python version. If necessary, install the appropriate version using the official Python installer (https://www.python.org/downloads/) or using tools like pyenv for managing multiple Python versions.
4. Try installing from pre-built wheels:
Instead of building from source, try installing lxml using pre-built wheels:
pip install lxml --no-cache-dir

The --no-cache-dir flag ensures that pip downloads the latest wheel from the PyPI repository.
5. Check for conflicting installations:
If you have multiple Python environments or conflicting installations of libraries, it could lead to issues. Consider creating a clean virtual environment to isolate the dependencies for SMD:
python3 -m venv venv
source venv/bin/activate
pip install smd

6. Check online resources:

Search for solutions related to "SMD installation error" or "lxml build error on macOS Big Sur" on forums like Stack Overflow or the SMD project's GitHub issue tracker.
Refer to the SMD documentation or GitHub repository for any specific installation instructions relevant to your environment.

Additional Tips:

Make sure you have administrator privileges when running pip commands.
If you're still encountering issues, provide more details about your setup, including the exact error message you're receiving, any additional configuration steps you've taken, and the SMD version you're trying to install. This information can help diagnose the problem more effectively.

By following these steps and referencing online resources, you should be able to resolve the installation issue and successfully install SMD on your Mac.


Proposal: Support ThemeShadow entirely within XAML

Proposal: Support ThemeShadow entirely within XAML
Summary
I know I'll get some flack for calling this a bug but I consider it one :) ThemeResource cannot be used without registering the control with the shadow in code-behind. This is a design bug in the way ThemeShadows are implemented. It breaks MVVM and lookless control principles as a shadow is entirely a styling choice.
Expected behavior
<Grid>
    <Grid.Resources>
        <ThemeShadow x:Name="SharedShadow" />
    </Grid.Resources>

    <Grid x:Name="BackgroundGrid" Background="{ThemeResource ApplicationPageBackgroundThemeBrush}" />

    <Rectangle x:Name="Rectangle1" Height="100" Width="100" Fill="Turquoise" Shadow="{StaticResource SharedShadow}" />

    <Rectangle x:Name="Rectangle2" Height="100" Width="100" Fill="Turquoise" Shadow="{StaticResource SharedShadow}" />
</Grid>

Should produce:

Without having to add the following in code behind (I realize Translation can already be set in XAML).
SharedShadow.Receivers.Add(BackgroundGrid);

Rectangle1.Translation += new Vector3(0, 0, 16);
Rectangle2.Translation += new Vector3(120, 0, 32);

https://docs.microsoft.com/en-us/windows/uwp/design/layout/depth-shadow
Rationale
Slowly MVVM and lookless control principles are getting broken. We need to maintain the ability to style shadows entirely within XAML. This came up when talking about styling a new control that has a a selected color that should have a drop-shadow effect. The shadow receiver would need to become a template part and registered in code-behind with the current ThemeShadow implementation. It doesn't make sense that an additional template part should be required for this situation. We need the ability to do things like shadows directly and entirely in XAML:

Scope

Capability
Priority

Remove the need to register shadow receivers before use or add ability to register in XAML
Must

@ranjeshj @StephenLPeters What is Microsoft's position on this? I keep seeing the lookless control concepts getting violated with new feature additions. ThemeShadow is one case, the new ProgressBar Lottie animations are another (although there is a hacky work-around). A control's style and re-templating should not depend on code-behind at all.
@chingucoding Voices a different opinion and it's the same I've heard from @jevansaks before. Therefore, I wonder if Microsoft is really moving away from MVVM and lookless controls (i.e. re-templating).

A control's style and re-templating should not depend on code-behind at all.

This is very hard to achieve, especially with growing complexity!
The issue is that it's hard to have a complex and fully functional control which is also easy to retemplate (TabView, NavigationView etc). I would also love to have every control be easily be retemplateable, but this would come at the cost of functionality in a lot of cases. Ideally developers shouldn't have the need to retemplate but rather use existing customization options such as control properties or lightweight styling. But that's just my opinion on this.

Regarding your proposal:
Would putting it inside the resources of a page or control automatically make that the receiver? How would multiple receivers work with that?
Also: I think your sample needs the translation properties, if that should be an all XAML sample.

This is very hard to achieve, especially with growing complexity!

Well, I meant the link is template parts. Template parts are always required but should be kept to a minimum amount. As we discussed, I don't want to add template parts just to be a shadow receiver.

Would putting it inside the resources of a page or control automatically make that the receiver? How would multiple receivers work with that?

Ideally, by default, whatever control(s) are underneath are the receiver. A new property like IsShadowReceiver="False" could be added to override this behavior and make a control invisible for shadows (similar to hit testing). A shadow should be added in the compositing process and I don't understand why there is added complexity to make it work. There are likely implementation limitations I'm unaware of in how shadows work.

Also: I think your sample needs the translation properties, if that should be an all XAML sample.

Yes, I just copy-pasted for now. I'll update it as the discussion progresses.

🦙 @robloo we have a proposal for this in the Toolkit here which should be in our 7.0 release. I already prototyped a POC that is working.
There's other things to consider here, especially to use these in any library components as I'd imagine that'd eat into the total limit of shadows which is small, see #2132.

@michael-hawker Great, that should be quite useful in the toolkit! Fundamentally, I don't understand this shadow limit either. I'll follow-up with that over on your other issue.

Xaml elements could get an Elevation property which applies the Vector 3 to the Z index value

Concerning the discussion about re-templating in general: I notice a while ago ALL the documentation seemed to disappear for re-templating specific controls. You used to be able to go to Microsoft docs online and see the default template as well as which parts were required. This documentation for each control is really critical for developers to understand specific quirks and concerns when re-templating is required for any given control. It would go a long way to helping alleviate @chingucoding concerns that re-templating is dangerous -- it would be far less dangerous if it was documented for every control.
@mdtauk, could you elaborate? I'm not sure how that is different from Translate.

Concerning the discussion about re-templating in general: I notice a while ago ALL the documentation seemed to disappear for re-templating specific controls. You used to be able to go to Microsoft docs online and see the default template as well as which parts were required. This documentation for each control is really critical for developers to understand specific quirks and concerns when re-templating is required for any given control. It would go a long way to helping alleviate @chingucoding concerns that re-templating is dangerous -- it would be far less dangerous if it was documented for every control.

I think the main problem with that kind of documentation is that it is a lot of work to keep it up to date and requires a lot of effort. You would need to update that every time you change the template, which can happen quite often.

Concerning the discussion about re-templating in general: I notice a while ago ALL the documentation seemed to disappear for re-templating specific controls. You used to be able to go to Microsoft docs online and see the default template as well as which parts were required. This documentation for each control is really critical for developers to understand specific quirks and concerns when re-templating is required for any given control. It would go a long way to helping alleviate @chingucoding concerns that re-templating is dangerous -- it would be far less dangerous if it was documented for every control.

I think the main problem with that kind of documentation is that it is a lot of work to keep it up to date and requires a lot of effort. You would need to update that every time you change the template, which can happen quite often.

Link to Github Xaml ResourceDIctionaries?

I think the main problem with that kind of documentation is that it is a lot of work to keep it up to date and requires a lot of effort. You would need to update that every time you change the template, which can happen quite often.

@chingucoding I agree it's difficult but only more so now with WinUI separate from the windows templates/styles. With WinUI 3 everything is coming together again and it will make a lot more sense. Additionally, the parts of the documents you are concerned about could be auto-generated. All controls, at least in c#, should declare their parts:
[TemplatePart(Name = nameof(CurrencyBox.LayoutRoot),               Type = typeof(FrameworkElement))]
Then the XAML could automatically be added to docs and the parts automatically detected.
The areas of the documentation I'm more concerned are notes from the original control authors. Those authors should provide quirks/instructions for downstream developers that may have to re-template. These notes shouldn't really change and don't need to be kept up-to date with automated tooling. I'm guessing Microsoft has lost this information internally too which is why bugs get re-introduced when the original control author is no longer working on it. Docs are key. Re-templating is fundamental.

Link to Github Xaml ResourceDIctionaries?

What @robloo was referring to is also what parts of the template are necessary. For that, it is not enough to link to the XAML but you also need someone to sit down, decide what is necssary and document it.

Then the XAML could automatically be added to docs and the parts automatically detected.

Yes that is something one could do, though I already have found different places where I can see the default template (e.g. through Visual Studio which can generate you a copy of a control template).

The areas of the documentation I'm more concerned are notes from the original control authors. Those authors should provide quirks/instructions for downstream developers that may have to re-template. These notes shouldn't really change and don't need to be kept up-to date with automated tooling. I'm guessing Microsoft has lost this information internally too which is why bugs get re-introduced when the original control author is no longer working on it. Docs are key. Re-templating is fundamental.

Yes that is the main problem, as the control changes those would need to get updated again and again. And requiring the author of the control to do that would make it very difficult to contribute to controls.

Link to Github Xaml ResourceDIctionaries?

What @robloo was referring to is also what parts of the template are necessary. For that, it is not enough to link to the XAML but you also need someone to sit down, decide what is necssary and document it.

Then the XAML could automatically be added to docs and the parts automatically detected.

Yes that is something one could do, though I already have found different places where I can see the default template (e.g. through Visual Studio which can generate you a copy of a control template).

The areas of the documentation I'm more concerned are notes from the original control authors. Those authors should provide quirks/instructions for downstream developers that may have to re-template. These notes shouldn't really change and don't need to be kept up-to date with automated tooling. I'm guessing Microsoft has lost this information internally too which is why bugs get re-introduced when the original control author is no longer working on it. Docs are key. Re-templating is fundamental.

Yes that is the main problem, as the control changes those would need to get updated again and again. And requiring the author of the control to do that would make it very difficult to contribute to controls.

If I am understanding the problem properly - This is about those controls which use Template Parts right?
Could docs be generated from the code, that calls these out - so highlighting the controls' construction, and labelling those required parts.
This could be listed in the docs for the control itself, as well as in autocomplete and comments in the templates?

@chingucoding

Yes that is the main problem, as the control changes those would need to get updated again and again. And requiring the author of the control to do that would make it very difficult to contribute to controls.

Most styling changes when touching templates don't affect the logic and template parts. So there is a lesser chance this gets out of date. All development requires discipline keeping the documentation up to date (maybe that's just because I come from automotive where documentation standards are very stict?). Anyway, now you don't want to support re-templating and also don't want to document things!? ;) It's not too much work, it just needs to be clearly defined and enforced by the project maintainers. In most cases only when a brand new control is written or a template part added would this really have to be revisited.
Aside from general quirks/instructions. The most useful documentation is also 'why' template parts were added. It should be explained someplace what is going on internally that require these. In some cases, the backgrounds/Fill are automatically calculated. That should all be explained. It should also be explained which template parts are designed to be safely excluded.
Honestly, I don't understand how these fundamental lookless control concept pioneering with WPF are getting lost and yet we are still using XAML. We need to correct this before it gets impossible to correct. I know other UI frameworks don't take this approach and that's fine, it's a totally different concept though.

If I am understanding the problem properly - This is about those controls which use Template Parts right?
Could docs be generated from the code, that calls these out - so highlighting the controls' construction, and labelling those required parts.
This could be listed in the docs for the control itself, as well as in autocomplete and comments in the templates?

Yes provided all of the template parts have been documented in code, theoretically you could auto generate the documentation for that.

Anyway, now you don't want to support re-templating and also don't want to document things!? ;)

I never implied either things ;) I just want to point out that both are a lot of work for limited reward, even if you say that we all need to have lookless controls. In my opinion, ideally, you wouldn't have to retemplate controls because they are already customizable enough through properties and lightweight styling and only in very specific scenarios a retemplate is needed to get the desired result.

Aside from general quirks/instructions. The most useful documentation is also 'why' template parts were added. It should be explained someplace what is going on internally that require these. In some cases, the backgrounds/Fill are automatically calculated. That should all be explained. It should also be explained which template parts are designed to be safely excluded.

Yes knowing why something was added is quite useful to know. I'm not sure what you mean by "backgrounds/Fill" here though.

I never implied either things ;) I just want to point out that both are a lot of work for limited reward, even if you say that we all need to have lookless controls. In my opinion, ideally, you wouldn't have to retemplate controls because they are already customizable enough through properties and lightweight styling and only in very specific scenarios a retemplate is needed to get the desired result.

Moving away from Lookless Controls would be a big change (should probably go hand in hand with a wholesale change from Xaml to Xaml Next) - and could be a good thing.  But it would not be Xaml in the way it has existed since Avalon and WinXP's days.
Android and Apple have their own UI paradigms - none as flexible as Xaml for changing control designs - but with Rendering offloaded to GPUs, could there be a call for a new approach - without Xaml trees to parse, but deeper aspects of primitive shapes, shadows, etc?

@chingucoding

Yes knowing why something was added is quite useful to know. I'm not sure what you mean by "backgrounds/Fill" here though.

The control I wrote over the past few days renders custom backgrounds for sliders to show color gradients. That's just an example I had in mind. Other controls do things like this too though. It's very useful to understand what's going on behind the scenes (and the intention) without reading the code.
@mdtauk I wholeheartedly agree with you. Like you said that's a paradigm shift. For now we should be consistent with what we have. XAML is getting old though and there are ideas for improving it or even going to a brand new Flutter-like or Blazor-like system.

The control I wrote over the past few days renders custom backgrounds for sliders to show color gradients. That's just an example I had in mind. Other controls do things like this too though. It's very useful to understand what's going on behind the scenes (and the intention) without reading the code.

Oh right, I see. Yes, not needing to read the code to understand what happens under the hood is quite useful. However some controls are very complex and "under the hood" becomes quite a lot (see NavigationView or ItemsRepeater).

Concerning the discussion about re-templating in general: I notice a while ago ALL the documentation seemed to disappear for re-templating specific controls. You used to be able to go to Microsoft docs online and see the default template as well as which parts were required. This documentation for each control is really critical for developers to understand specific quirks and concerns when re-templating is required for any given control.

🦙 Hey All (@robloo , @mdtauk, @chingucoding), think we got a bit off topic here. If you want to share all your thoughts on having templates better documented, I had an issue I filed on that subject over here: https://github.com/MicrosoftDocs/windows-uwp/issues/1870 (probably needs a better title). Though to my knowledge the UWP ones were never documented, it was only WPF that did this (they're still online).

@michael-hawker Yes, we were definitely getting off track for this issue. Thanks for linking to the relevant one, I didn't know it already existed and I'll copy some comments over to it.
I also could have sworn when UWP first released (years ago now) the docs looked very much like WPF for templates. What I remember looks exactly like the WPF docs though so it's possible I was just confusing the two.

Would be nice to make shadows more MVVM friendly and usable in XAML.


[docs] Update TS config docs

Hi, I updated the example code setting up react-docgen-typescript-loader after having fought with it for quite some time.
I'm also wondering if recommending react-docgen-typescript-webpack-plugin is really necessary since configuring directly with react-docgen-typescript-loader is the same amount of code...
const path = require("path");

module.exports = (baseConfig, env, config) => {
    config.module.rules.push({
        test: /\.(ts|tsx)$/,
        include: path.resolve(__dirname, "../"),
        use: [require.resolve("ts-loader"), require.resolve("react-docgen-typescript-loader")],
    });
    config.resolve.extensions.push(".ts", ".tsx");

    return config;
};

^ hm interesting. Can you open a feature request?

@wuweiweiwu do you mean a feature request about the react-docgen-typescript-webpack-plugin recommendation?

@cosmith yep!


update atlantis configmap

atlantis plan -p project-quick-demo

Ran Plan for project: project-quick-demo dir: Terraform/quick_demo workspace: default
Show Output

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+ create

Terraform will perform the following actions:

  # google_compute_network.default will be created
+ resource "google_compute_network" "default" {
+       auto_create_subnetworks                   = false
+       delete_default_routes_on_create           = false
+       gateway_ipv4                              = (known after apply)
+       id                                        = (known after apply)
+       internal_ipv6_range                       = (known after apply)
+       mtu                                       = (known after apply)
+       name                                      = "wade-test-network"
+       network_firewall_policy_enforcement_order = "AFTER_CLASSIC_FIREWALL"
+       project                                   = "adept-presence-396401"
+       routing_mode                              = "GLOBAL"
+       self_link                                 = (known after apply)
    }

Plan: 1 to add, 0 to change, 0 to destroy.

:arrow_forward: To apply this plan, comment:

atlantis apply -p project-quick-demo

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -p project-quick-demo

Plan: 1 to add, 0 to change, 0 to destroy.

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

atlantis plan -p project-quick-demo -- -target=none.none

Ran Plan for project: project-quick-demo dir: Terraform/quick_demo workspace: default
Show Output

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
╷
│ Warning: Resource targeting is in effect
│
│ You are creating a plan with the -target option, which means that the
│ result of this plan may not represent all of the changes requested by the
│ current configuration.
│
│ The -target option is not for routine use, and is provided only for
│ exceptional situations such as recovering from errors or mistakes, or when
│ Terraform specifically suggests to use it as part of an error message.
╵

:arrow_forward: To apply this plan, comment:

atlantis apply -p project-quick-demo

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -p project-quick-demo -- -target=none.none

No changes. Your infrastructure matches the configuration.

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

atlantis plan -p project-quick-demo -- -target=none.none

Ran Plan for project: project-quick-demo dir: Terraform/quick_demo workspace: default
Show Output

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
╷
│ Warning: Resource targeting is in effect
│
│ You are creating a plan with the -target option, which means that the
│ result of this plan may not represent all of the changes requested by the
│ current configuration.
│
│ The -target option is not for routine use, and is provided only for
│ exceptional situations such as recovering from errors or mistakes, or when
│ Terraform specifically suggests to use it as part of an error message.
╵

:arrow_forward: To apply this plan, comment:

atlantis apply -p project-quick-demo

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -p project-quick-demo -- -target=none.none

No changes. Your infrastructure matches the configuration.

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

atlantis apply

Ran Apply for project: project-quick-demo dir: Terraform/quick_demo workspace: default
Show Output
╷
│ Warning: Applied changes may be incomplete
│
│ The plan was created with the -target option in effect, so some changes
│ requested in the configuration may have been ignored and the output values
│ may not be fully updated. Run the following command to verify that no other
│ changes are pending:
│     terraform plan
│
│ Note that the -target option is not suitable for routine use, and is
│ provided only for exceptional situations such as recovering from errors or
│ mistakes, or when Terraform specifically suggests to use it as part of an
│ error message.
╵

Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Automatically merging because all plans have been successfully applied.

Locks and plans deleted for the projects and workspaces modified in this pull request:

dir: Terraform/quick_demo workspace: default


test-branch/execute-job/wrong-commit-sha-on-pr/b05f78cf-8ca7-4b0f-8572-3e4e3a9d6c88

PR for testing 962a91696d017952d59210c00d93aa5de32ffcca

/canonical/self-hosted-runners/run-workflows 931ad21dd9ace68aaa0a7d341e94de96ad93fa6b


Add more validation and tests for $unset

Description
Closes #1432.

Added validation of $unset input for invalid path.
Moved conflict path detection logic to types package, previously it was in update.go.

Readiness checklist

[ ] I added/updated unit tests.
[x] I added/updated integration/compatibility tests.
[ ] I added/updated comments and checked rendering.
[x] I made spot refactorings.
[ ] I updated user documentation.
[ ] I ran task all, and it passed.
[x] I ensured that PR title is good enough for the changelog.
[x] (for maintainers only) I set Reviewers (@FerretDB/core), Labels, Project and project's Sprint fields.
[x] I marked all done items in this checklist.

:wave: @shibasisp, I added additional validation of $unset arguments in this PR :hugs:


Paperpile, Google moving to hyperlinking

(Related info: https://paperpile.com/blog/google-drive-sync-improvements/)
I've been trying to sync "Starred Papers" folder to Remarkable 2 now, but Paperpile has changed so that that folder only consists of links to original files. The nice sync script here does not work with links (i.e. can't fetch the original file).
Would be a great addition, if this could do that as well. I changed the folder structure in Paperpile to suit better Remarkable use and sync all Paperpile papers from Drive, but there will be a size issue soonish with that solution. Thus, "Starred Papers" would be great to have as an option.
I understand that Paperpile is just one use case, not close to so many hearts, but there should be many instances of services facing this new Google Policy, and thus affected users. Thanks for the script anyways!!

From some very light reading around this topic it seems Google Drive no longer supports placing files in multiple places and use shortcuts instead (as of 30th Sept). Perhaps these shortcuts will have the special MimeType SHORTCUT; if they do it might be worked into generateZipBlob. This is only guessing as right now I don't think this affects me; so a low priority from my perspective. That said, I'm open to PRs that add this support (if accompanied with some instructions for manual testing). It would be a nice optional feature - to support following shortcuts.

I've just uploaded an update that should follow shortcuts. Let me know if that also works for you.

I think this issue is likely to be resolved now. I'll close it for now. Feel free to open another issue if it's not working for you.


App isn't available on Australian App store

Is this a $ issue?
Or just something that Apple decided that you have to apply separately?

Not available in the Swiss store as well.

Same issue in the US

Also not available in Italy

Also not in Canada

Unavailable in the UK, USA, and Netherlands.
Can you at least give us an IPA or a TestFlight link?

It is not available in Germany as well.

Last commit was 3 months ago, I hope dev is well.

out of curiosity, where is the app available?

out of curiosity, where is the app available?

Compiling from source via Xcode, I guess.

Suggest removal of the App Store link in the meantime, it only causes confusion.
Best of luck with your efforts, look forward to seeing the results when ready.

with the new reddit API policy is looming and recent AMA by the CEO. I suppose there are lots of redditors want to try Lemmy.ml. I hope this app can get ready soon.


Appears to be no way to copy a texture to CPU memory

I want to add the ability to save screenshots/record videos to my rendering engine (it's aimed at generative art so saving screenshots is a core feature). I can render to a texture but there doesn't seem to be any way to use glReadPixels or a related function to copy from a texture to a local buffer. I do not know enough about OpenGL to implement this myself (I used to use raw OpenGL but I only ever did simple stuff), but some quick Googling showed up glReadPixels and glReadPixel, neither of which appear in gfx at all.
I don't know whether I'm just missing a way to load information back from the GPU or whether it's just not implemented.

@Vurich there is an issue template here for a reason. In particular, you need to specify what version of gfx-rs you are using.
For 0.17, you may want to look at the gamma example that has a screenshot function.

Thanks, it looks like the Reader type was the missing piece that I was looking for. Apologies for not using the template.

Awesome, I suppose it's resolved then.


Enable low resolution data access

In the docs page it's stated that by default only resolutions to 250m area available. Would it make sense to add previewMode: EXTENDED_PREVIEW to the SentinelHubRequest? I noticed that I need to make the change here, since it's not possible to do it in `eo-learn.

This functionality is already possible with SentinelHubRequest class. You can pass previewMode to a parameter other_args of input_data method. More in documentation.

This functionality is already possible with SentinelHubRequest class. You can pass previewMode to a parameter other_args of input_data method. More in documentation.

I'm not sure that's correct, or I might not understand it correctly. I was aware of this parameter, but it didn't work the way I wanted it to.
Example here:
a) the original request
{
  "bounds":{
    "bbox":[
      46.16,
      -16.15,
      46.51,
      -15.58
    ],
    "properties":{
      "crs":"http://www.opengis.net/def/crs/EPSG/0/4326"
    }
  },
  "data":[
    {
      "dataFilter":{
        "maxCloudCoverage":100,
        "mosaickingOrder":"mostRecent",
        "timeRange":{
          "from":"2020-06-12T00:00:00Z",
          "to":"2020-06-13T23:59:59Z"
        }
      },
      "type":"S2L1C"
    }
  ]
}

If I add other_args = {'previewMode': 'EXTENDED_PREVIEW'} I get
{
  "bounds":{
    "bbox":[
      46.16,
      -16.15,
      46.51,
      -15.58
    ],
    "properties":{
      "crs":"http://www.opengis.net/def/crs/EPSG/0/4326"
    }
  },
  "data":[
    {
      "dataFilter":{
        "maxCloudCoverage":100,
        "mosaickingOrder":"mostRecent",
        "timeRange":{
          "from":"2020-06-12T00:00:00Z",
          "to":"2020-06-13T23:59:59Z"
        }
      },
      "previewMode":"EXTENDED_PREVIEW",
      "type":"S2L1C"
    }
  ]
}

and you can see that the previewMode is in the wrong position, so I can add the nested one other_args = {'dataFilter': {'previewMode': 'EXTENDED_PREVIEW'}}
{
  "bounds":{
    "bbox":[
      46.16,
      -16.15,
      46.51,
      -15.58
    ],
    "properties":{
      "crs":"http://www.opengis.net/def/crs/EPSG/0/4326"
    }
  },
  "data":[
    {
      "dataFilter":{
        "maxCloudCoverage":100,
        "mosaickingOrder":"mostRecent",
        "timeRange":{
          "from":"2020-06-12T00:00:00Z",
          "to":"2020-06-13T23:59:59Z"
        }
      },
      "type":"S2L1C"
    }
  ]
}

but in this case, the whole dataFilter fields gets overridden.
Is this the expected behaviour?

In any case, of course, there are workarounds, I just wanted to suggest to add this to the request since it doesn't really change the existing functionality anyways. EOBrowser works in the same way, iirc.

Fixed in SH, now it needs to be exposed in eolearn


Add Remove-RubrikVMSnapshot cmdlet and additional logging

Description
This PR adds a new Remove-RubrikVMSnapshot cmdlet and associated unit test, along with some additional verbose logging. It also modifies the logic so that DELETE API calls return a response when the API call is successful. Previously the user was given no response in this scenario.
Related Issue
This project only accepts pull requests related to open issues.

If suggesting a new feature or change, please discuss it in an issue first.
If fixing a bug, there should be an issue describing it with steps to reproduce

https://github.com/rubrikinc/rubrik-sdk-for-powershell/issues/148
Motivation and Context
Why is this change required? What problem does it solve?
This PR addresses #148, and it provides additional useful output to the user
How Has This Been Tested?

Please describe in detail how you tested your changes.
Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc.

Tested against CDM 5.0.1 from MacOS. I tested almost all of the Remove-* cmdlets to verify the new response would not affect them, and tested several Get-* cmdlets as a smoke test to verify that the code needed for additional verbose logging did not have unintentional effects.
Screenshots (if appropriate):
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:
Go over all the following points, and put an x in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!

[X] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTION document.
[X] I have updated the CHANGELOG file accordingly for the version that this merge modifies.
[X] I have added tests to cover my changes.
[X] All new and existing tests passed.

Resolve #148


Allow the market password to be stored in a file.

I use an Option[File] which will revert to the old behavior if the setting is None.

I added a generic password caching mechanism to the plugin, to enable it:
  cachePasswords in Android := true

At the moment it's used by the github task and the jar signer.

jberkel, I don't think this works for me. I do my release builds on jenkins which pulls directly from github without my intervention. Being able to specify a password file (optionally None) seems like a more general solution.

the keystore passwords files are expected in a well known location ~.sbt/sbt-android-plugin-passwords/keystore. so just create that file (with account=password entries), enable password caching and it should work.

Great, seems to work fine. Thanks!


Include statistics

enable multipe data visualization that are created in OS-Dashboard.

We implemented the feature as described in the #36. We took care to comment the code and build an appealing frontend.

A lot of commits for small changes. Next time! Please consider squashing ( https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History) the multiple commits into a single commit for better code organization.
It's preferable to have fewer commits when the changes are minimal or when they can be logically grouped together.
This will help maintain a cleaner commit history and make it easier for reviewers to understand the changes made. Thank you for your attention to this matter.

tbh., I don't think so. There is no need to go through every commit by itself, you can just have a look at the "Files changed"-Section (or by a single use of git diff) to see all changes at once.
In Addition, smaller commits make it easier to revert single changes, if they where not necessary.
If you like to, we can discuss this in person, maybe this is a better place than this pull request, at least for a longer discussion

I think the visualization looks good so far. Therefore we can merge this branch into main!

I like it. I will merge it into main for the release shortly


[conan.io/center] Cookies don't save in Firefox

What is your problem/feature request?
Every time I load your site in Firefox I see a message to accept cookies, I accept them, but even opening your site in the separate tab shows the same message again...

We have fixed the problem with saving cookie preferences. If you see it happening again, please open a new ticket, thanks!


Global os.environ usage begone.

No more use of global os.environ in credentials.

It looks like this stacks on #53, at least.  Maybe also #54?

Yeah they're all in order, it stacks on both of those

Great.  Thank you.  Merging.


FEAT: support QwQ-32B-Preview

can we support qwq quantization ?

Yes, awq is included already, but hf only.

thanks for reply!


Add summary to capi

User of nntrainer should have ways to review current model construct. so there should be a way to print summary of a model.

:octocat: cibot: Thank you for posting issue #270. The person in charge will reply soon.

[ ] Add print methods to tensors
[ ] Add print methods to layers
[ ] Add print methods to neural network

Need polishing a bit though, it is done for now.