%global _empty_manifest_terminate_build 0 Name: python-pydevd-pycharm Version: 231.8109.197 Release: 1 Summary: PyCharm Debugger (used in PyCharm and PyDev) License: Apache 2.0 URL: https://github.com/JetBrains/intellij-community Source0: https://mirrors.nju.edu.cn/pypi/web/packages/e0/0d/94518b2b81df5391d11b0b005a593c7753c281e24b83352d92529bb1970d/pydevd-pycharm-231.8109.197.tar.gz BuildArch: noarch %description The sources for the PyDev.Debugger (used in PyDev & PyCharm) may be seen at: https://github.com/fabioz/PyDev.Debugger In general, the debugger backend should **NOT** be installed separately if you're using an IDE which already bundles it (such as PyDev or PyCharm). It is however available in PyPi so that it can be installed for doing remote debugging with `pip` -- so, when debugging a process which runs in another machine, it's possible to `pip install pydevd-pycharm` and in the code use `pydevd_pycharm.settrace(host='10.1.1.1')` to connect the debugger backend to the debugger UI running in the IDE (whereas previously the sources had to be manually copied from the IDE installation). It should be compatible with Python 2.6 onwards (as well as Jython 2.7, IronPython and PyPy -- and any other variant which properly supports the Python structure for debuggers -- i.e.: sys.settrace/threading.settrace). Recent versions contain speedup modules using Cython, which are generated with a few changes in the regular files to `cythonize` the files. To update and compile the cython sources (and generate some other auto-generated files), `build_tools/build.py` should be run -- note that the resulting .pyx and .c files should be commited. To generate a distribution with the precompiled binaries for the IDE, `build_binaries_windows.py` should be run ( note that the environments must be pre-created as specified in that file). To generate a distribution to upload to PyPi, `python setup.py sdist bdist_wheel` should be run for each python version which should have a wheel and afterwards `twine upload -s dist/pydevd-*` should be run to actually upload the contents to PyPi. Travis (Linux CI): |travis| Appveyor (Windows CI): |appveyor| %package -n python3-pydevd-pycharm Summary: PyCharm Debugger (used in PyCharm and PyDev) Provides: python-pydevd-pycharm BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-pydevd-pycharm The sources for the PyDev.Debugger (used in PyDev & PyCharm) may be seen at: https://github.com/fabioz/PyDev.Debugger In general, the debugger backend should **NOT** be installed separately if you're using an IDE which already bundles it (such as PyDev or PyCharm). It is however available in PyPi so that it can be installed for doing remote debugging with `pip` -- so, when debugging a process which runs in another machine, it's possible to `pip install pydevd-pycharm` and in the code use `pydevd_pycharm.settrace(host='10.1.1.1')` to connect the debugger backend to the debugger UI running in the IDE (whereas previously the sources had to be manually copied from the IDE installation). It should be compatible with Python 2.6 onwards (as well as Jython 2.7, IronPython and PyPy -- and any other variant which properly supports the Python structure for debuggers -- i.e.: sys.settrace/threading.settrace). Recent versions contain speedup modules using Cython, which are generated with a few changes in the regular files to `cythonize` the files. To update and compile the cython sources (and generate some other auto-generated files), `build_tools/build.py` should be run -- note that the resulting .pyx and .c files should be commited. To generate a distribution with the precompiled binaries for the IDE, `build_binaries_windows.py` should be run ( note that the environments must be pre-created as specified in that file). To generate a distribution to upload to PyPi, `python setup.py sdist bdist_wheel` should be run for each python version which should have a wheel and afterwards `twine upload -s dist/pydevd-*` should be run to actually upload the contents to PyPi. Travis (Linux CI): |travis| Appveyor (Windows CI): |appveyor| %package help Summary: Development documents and examples for pydevd-pycharm Provides: python3-pydevd-pycharm-doc %description help The sources for the PyDev.Debugger (used in PyDev & PyCharm) may be seen at: https://github.com/fabioz/PyDev.Debugger In general, the debugger backend should **NOT** be installed separately if you're using an IDE which already bundles it (such as PyDev or PyCharm). It is however available in PyPi so that it can be installed for doing remote debugging with `pip` -- so, when debugging a process which runs in another machine, it's possible to `pip install pydevd-pycharm` and in the code use `pydevd_pycharm.settrace(host='10.1.1.1')` to connect the debugger backend to the debugger UI running in the IDE (whereas previously the sources had to be manually copied from the IDE installation). It should be compatible with Python 2.6 onwards (as well as Jython 2.7, IronPython and PyPy -- and any other variant which properly supports the Python structure for debuggers -- i.e.: sys.settrace/threading.settrace). Recent versions contain speedup modules using Cython, which are generated with a few changes in the regular files to `cythonize` the files. To update and compile the cython sources (and generate some other auto-generated files), `build_tools/build.py` should be run -- note that the resulting .pyx and .c files should be commited. To generate a distribution with the precompiled binaries for the IDE, `build_binaries_windows.py` should be run ( note that the environments must be pre-created as specified in that file). To generate a distribution to upload to PyPi, `python setup.py sdist bdist_wheel` should be run for each python version which should have a wheel and afterwards `twine upload -s dist/pydevd-*` should be run to actually upload the contents to PyPi. Travis (Linux CI): |travis| Appveyor (Windows CI): |appveyor| %prep %autosetup -n pydevd-pycharm-231.8109.197 %build %py3_build %install %py3_install install -d -m755 %{buildroot}/%{_pkgdocdir} if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi pushd %{buildroot} if [ -d usr/lib ]; then find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/lib64 ]; then find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/bin ]; then find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/sbin ]; then find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst fi touch doclist.lst if [ -d usr/share/man ]; then find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst fi popd mv %{buildroot}/filelist.lst . mv %{buildroot}/doclist.lst . %files -n python3-pydevd-pycharm -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Mon Apr 10 2023 Python_Bot - 231.8109.197-1 - Package Spec generated