removed custom mypy

README.md

@@ -66,7 +66,7 @@ pipx install nox
 The easiest way to use the stubs while you're devleoping them is to create an editable install.  Simply create a `.pth` file in the site-packages directory of the venv where your other deps live:
 
 ```
-echo "/path/to/cg-stubs/ocio/stubs/" > /path/to/venv/lib/python3.7/site-packages/ocio.pth
+echo "/path/to/cg-stubs/ocio/stubs/" > /path/to/venv/lib/python3.9/site-packages/ocio.pth
 ```
 
 The name of the .pth file does not matter.  Note that if you're using the mypy daemon, be sure to run `dmypy stop` to reread freshly modified stubs.

houdini/stubgen_houdini.sh

@@ -12,7 +12,7 @@ setpkg -c python-3 houdini-$version
 
 outdir=$REPO_PATH/houdini/stubs/
 
-export PYTHONPATH=$REPO_PATH/../mypy:$REPO_PATH/core/python:$REPO_PATH/.venv-py37-linux/lib/python3.7/site-packages:$REPO_PATH/houdini/bin/
+export PYTHONPATH=$REPO_PATH/core/python:$REPO_PATH/.venv-py37-linux/lib/python3.7/site-packages:$REPO_PATH/houdini/bin/
 export PATH=${REPO_PATH}/houdini/bin:${PATH}
 hython -c "import stubgen_houdini;stubgen_houdini.main(['-m', 'hou', '--parse-only', '--verbose', '-o=.out'])"
 

nuke/stubgen_nuke.sh

@@ -10,7 +10,6 @@ outdir=$REPO_PATH/nuke/stubs/
 
 # using $NUKE_APP/python3 crashes in my latest tests
 # must import nuke to make nuke modules available, but this consumes sys.argv, so we have to get a bit hacky
-export PYTHONPATH=$REPO_PATH/../mypy
 
 $REPO_PATH/nuke/bin/nukepy -c "import _nuke;import sys;sys.argv=['foo', '-o=$outdir', '-m', '_nuke', '-p', 'nuke_internal', '-m', '_curveknob', '-m', '_nuke_color', '-m', '_curvelib', '-m', '_geo', '-m', '_localization', '-m', '_splinewarp']; import mypy.stubgen;mypy.stubgen.main()"
 

requirements.txt

@@ -1,3 +1,3 @@
 docstring_parser
 # mypy==1.9.0
-mypy @ git+https://github.com/chadrik/mypy@stubgen/nested-classes
+mypy @ git+https://github.com/chadrik/mypy@stubgen/nested-classes