pkgsrc/devel/py-dialog/PLIST

@comment $NetBSD: PLIST,v 1.2 2020/02/04 17:17:06 adam Exp $
${PYSITELIB}/${EGG_INFODIR}/PKG-INFO
${PYSITELIB}/${EGG_INFODIR}/SOURCES.txt
${PYSITELIB}/${EGG_INFODIR}/dependency_links.txt
${PYSITELIB}/${EGG_INFODIR}/top_level.txt
${PYSITELIB}/dialog.py
${PYSITELIB}/dialog.pyc
${PYSITELIB}/dialog.pyo
py-dialog{2}: updated to 3.5.1 Main changes in version 3.5.1 The main changes in version 3.5.1 are: The default used when the PATH environment variable is unset is now "/bin:/usr/bin" instead of ":/bin:/usr/bin". This is relevant when the dialog argument of the Dialog constructor contains no slash (/), which is the case by default. The benefit of this change is that in such a situation (PATH unset and dialog argument containing no slash), the dialog-like program will not be searched in the current directory anymore (unless of course the current directory is /bin or /usr/bin). This is a much safer behavior; fortunately, the risky behavior only ever existed on bogus setups where the PATH environment variable is unset. Note that in this respect, we have been following what the GNU C Library (glibc) does for its execvp() function—the corresponding change in glibc happened in version 2.24, released in 2016. When a Dialog instance is created, it now immediately stores the result of calling os.path.realpath() on the specified executable (which is searched using the PATH if the dialog argument passed to the constructor contains no slash—cf. documentation of the Dialog constructor). This way, a pythondialog-based program can change its current directory after creating a Dialog instance without fearing that this might cause subsequent Dialog method calls to fail or to invoke an executable from a different directory (additionally, os.path.realpath() resolves symbolic links). The Python 2 backport of pythondialog has been released for this version and should be on par with pythondialog 3.5.1 (this is why version 3.5.0 of the backport has been skipped). The packaging of the backport has been switched from distutils to setuptools too, just as was done in pythondialog 3.5.0 (see below). As a consequence, it is now available in wheel format. However, as said above, Python 2 is deprecated and the Python 2 backport of pythondialog is not supported anymore. Don't expect any further updates to it. Main changes in version 3.5.0 The main change in version 3.5.0 is: pythondialog's packaging has been switched from distutils to setuptools (this is the modern way, see the Python Packaging User Guide). Thanks to this change, pythondialog is now available in wheel format. The normal installation method using pip didn't change (see the INSTALL file for details). The Python 2 backport of pythondialog has not been released for this version (version 3.5.1 will be the last one). 2020-02-04 18:17:06 +01:00			`@comment $NetBSD: PLIST,v 1.2 2020/02/04 17:17:06 adam Exp $`
			`${PYSITELIB}/${EGG_INFODIR}/PKG-INFO`
			`${PYSITELIB}/${EGG_INFODIR}/SOURCES.txt`
			`${PYSITELIB}/${EGG_INFODIR}/dependency_links.txt`
			`${PYSITELIB}/${EGG_INFODIR}/top_level.txt`
			`${PYSITELIB}/dialog.py`
Add ports for pythondialog and python2-pythondialog, frontends to the "dialog" utility. From DESCR: pythondialog is a Python wrapper for the dialog utility originally written by Savio Lam, and later rewritten by Thomas E. Dickey. Its purpose is to provide an easy to use, pythonic and comprehensive Python interface to dialog. This allows one to make simple text-mode user interfaces on Unix-like systems (including Linux). 2015-01-11 21:14:58 +01:00			`${PYSITELIB}/dialog.pyc`
			`${PYSITELIB}/dialog.pyo`