[ANNOUNCEMENT] Updated: Perl distributions
The following Perl distributions have been updated to their latest version on CPAN: x86/x86_64 -- perl-Text-CSV_XS-1.44-1 noarch -- perl-Log-Log4perl-1.50-1 perl-Mail-Transport-3.005-1 perl-String-Util-1.30-1 -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: python packages
Several python packages have been uploaded python27-decorator-4.4.2-1 python27-docutils-0.16-1 python27-ipython_genutils-0.2.0-2 python27-pexpect-4.8.0-1 python27-pickleshare-0.7.5-2 python27-ptyprocess-0.6.0-2 python27-requests-2.24.0-1 python27-simplegeneric-0.8.1-5 python27-traitlets-4.3.3-1 python27-wcwidth-0.2.5-1 python36-decorator-4.4.2-1 python36-docutils-0.16-1 python36-ipython_genutils-0.2.0-2 python36-ipython-7.16.1-1 python36-pexpect-4.8.0-1 python36-pickleshare-0.7.5-2 python36-prompt_toolkit-3.0.5-1 python36-ptyprocess-0.6.0-2 python36-pygments-2.6.1-1 python36-requests-2.24.0-1 python36-simplegeneric-0.8.1-5 python36-traitlets-4.3.3-1 python36-wcwidth-0.2.5-1 python37-decorator-4.4.2-1 python37-docutils-0.16-1 python37-ipython_genutils-0.2.0-2 python37-ipython-7.16.1-1 python37-pexpect-4.8.0-1 python37-pickleshare-0.7.5-2 python37-prompt_toolkit-3.0.5-1 python37-ptyprocess-0.6.0-2 python37-pygments-2.6.1-1 python37-requests-2.24.0-1 python37-simplegeneric-0.8.1-5 python37-traitlets-4.3.3-1 python37-wcwidth-0.2.5-1 python38-decorator-4.4.2-1 python38-docutils-0.16-1 python38-ipython_genutils-0.2.0-2 python38-ipython-7.16.1-1 python38-pexpect-4.8.0-1 python38-pickleshare-0.7.5-2 python38-prompt_toolkit-3.0.5-1 python38-ptyprocess-0.6.0-2 python38-pygments-2.6.1-1 python38-requests-2.24.0-1 python38-simplegeneric-0.8.1-5 python38-traitlets-4.3.3-1 python38-wcwidth-0.2.5-1 CHANGES These are the latest upstream releases DESCRIPTION Python is a programming language that lets you work quickly and integrate systems more effectively. Python is powerful... and fast; plays well with others; runs everywhere; is friendly & easy to learn; is Open. HOMEPAGE https://www.python.org/ Regards Marco Atzeri If you have questions or comments, please send them to the cygwin mailing list at: cygwin (at) cygwin (dot) com . -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
missing Python 3.7 for python3 package version
Hi, I'm trying to make my default Python 3 to Python 3.7, but when I open the version chooser, only Python 3.6 and 3.8 available. Can I get Python 3.7 in this version chooser? Screenshot attached. Thank you. -- Sharuzzaman Ahmat Raslan -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Needing readline to build a local 64-bit exec
Of more than 640 *.c files incorporated into a locally-built executable, exactly one contains many references to readline, such as "#include ". The 32-bit build proceeds impeccably to completion: there is a subdirectory x86/release/readline in the Cygwin resource and a paragraph for @ readline in the file x86/setup.ini, albeit with "obsolete" qualifiers. However the 64-bit build fails at the compilation of the file containing the reference to readline: various *.h not found. There is a subdirectory x86_64/release/readline in the resource but it contains only subdirectories, not the root readline-7.*.tar.xz files. The file x86_64/setup.ini contains no paragraph for @ readline. I do not fully understand the interpretation or consequences of obsoletion, but this changed provision relating to readline is the key difference between x86/ and x86_64/. I tried supplementing the resource under x86_64/release/readline with the "missing" *.tar.xz files and editing x86_64/setup.ini to include the paragraph for @ readline, but this broke setup.ini.sig. (I use a constantly updated mirror on a local drive. It takes 62G but it's worth it.) It is clear (well, given my limited understanding of the handling of obsoleted files) that in some way the provision under x86/release/readline and its referencing in x86/setup.ini remains critical to the successful build of the 32-bit executable, and the lack of provision under x86_64/release/readline and omission from x86_64/setup.ini is critical to the failed build. It seems to be located, picked up and used, despite its obsolete status? Can it be recovered into the x86_64 provision? Or can somebody who understands it better please explain the discrepancy in x86 and x86_64 provision that triggers the contrasting success and failure for 32-bit and 64-bit version build attempts. And, even better, how to achieve 64-bit success? Thank you! -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: missing Python 3.7 for python3 package version
On 27.07.2020 06:47, Sharuzzaman Ahmat Raslan via Cygwin wrote: Hi, I'm trying to make my default Python 3 to Python 3.7, but when I open the version chooser, only Python 3.6 and 3.8 available. Can I get Python 3.7 in this version chooser? probably not, as by default the last one will be in any way proposed the next time you will update python. I still need to figure how to effectively manage the 3 python3.x in parallel Screenshot attached. Thank you. all the content of that package is link to the 3.6 or 3.8 binary $ ls -l $(cygcheck -l python3) lrwxrwxrwx 1 Marco Kein 8 Jun 20 06:27 /usr/bin/pydoc3 -> pydoc3.8 lrwxrwxrwx 1 Marco Kein 13 Jun 20 06:27 /usr/bin/python3 -> python3.8.exe -rw-rw-r-- 1 Marco Kein 46 Jun 15 21:21 /usr/share/man/man1/python3.1.gz if you install python37 package and than modify the link by yourself to point to pydoc3.7 and python3.7m.exe than python3 will execute python3.7 Question: any reason to not use python 3.8 ? Regards Marco -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Needing readline to build a local 64-bit exec
On 27.07.2020 07:47, Fergus Daly via Cygwin wrote: Of more than 640 *.c files incorporated into a locally-built executable, exactly one contains many references to readline, such as "#include ". The 32-bit build proceeds impeccably to completion: there is a subdirectory x86/release/readline in the Cygwin resource and a paragraph for @ readline in the file x86/setup.ini, albeit with "obsolete" qualifiers. However the 64-bit build fails at the compilation of the file containing the reference to readline: various *.h not found. There is a subdirectory x86_64/release/readline in the resource but it contains only subdirectories, not the root readline-7.*.tar.xz files. The file x86_64/setup.ini contains no paragraph for @ readline. I do not fully understand the interpretation or consequences of obsoletion, but this changed provision relating to readline is the key difference between x86/ and x86_64/. I tried supplementing the resource under x86_64/release/readline with the "missing" *.tar.xz files and editing x86_64/setup.ini to include the paragraph for @ readline, but this broke setup.ini.sig. (I use a constantly updated mirror on a local drive. It takes 62G but it's worth it.) It is clear (well, given my limited understanding of the handling of obsoleted files) that in some way the provision under x86/release/readline and its referencing in x86/setup.ini remains critical to the successful build of the 32-bit executable, and the lack of provision under x86_64/release/readline and omission from x86_64/setup.ini is critical to the failed build. It seems to be located, picked up and used, despite its obsolete status? Can it be recovered into the x86_64 provision? Or can somebody who understands it better please explain the discrepancy in x86 and x86_64 provision that triggers the contrasting success and failure for 32-bit and 64-bit version build attempts. And, even better, how to achieve 64-bit success? Thank you! -- have you tried installing libreadline-devel ? It includes the header you are looking for $ cygcheck -p usr/include/readline/readline.h Found 3 matches for usr/include/readline/readline.h libreadline-devel-7.0.1-1 - libreadline-devel: GNU readline and history librarie s (development) (installed binaries and support files) libreadline-devel-7.0.1-2 - libreadline-devel: GNU readline and history librarie s (development) libreadline-devel-7.0.3-3 - libreadline-devel: GNU readline and history librarie s (development) Regards MArco -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: missing Python 3.7 for python3 package version
Hi Marco, Thank you for the information. It's my habit to use the 2nd last stable release to have a more stable environment. Also, I personally believe not all libraries out there support Python 3.8 yet, but a majority of them does support Python 3.7. As there is currently no option to set Python 3.7 as default for python3, then I will hard code my script with #!/bin/env python3.7 Really hope the option is there. Thank you. On Mon, Jul 27, 2020 at 2:03 PM Marco Atzeri via Cygwin wrote: > On 27.07.2020 06:47, Sharuzzaman Ahmat Raslan via Cygwin wrote: > > Hi, > > > > I'm trying to make my default Python 3 to Python 3.7, but when I open the > > version chooser, only Python 3.6 and 3.8 available. > > > > Can I get Python 3.7 in this version chooser? > > probably not, as by default the last one will be in any way proposed > the next time you will update python. > I still need to figure how to effectively manage the > 3 python3.x in parallel > > > > > Screenshot attached. > > > > Thank you. > > > > all the content of that package is link to the 3.6 or 3.8 binary > > $ ls -l $(cygcheck -l python3) > lrwxrwxrwx 1 Marco Kein 8 Jun 20 06:27 /usr/bin/pydoc3 -> pydoc3.8 > lrwxrwxrwx 1 Marco Kein 13 Jun 20 06:27 /usr/bin/python3 -> python3.8.exe > -rw-rw-r-- 1 Marco Kein 46 Jun 15 21:21 /usr/share/man/man1/python3.1.gz > > if you install python37 package and than modify the link > by yourself to point to pydoc3.7 and python3.7m.exe > than python3 will execute python3.7 > > > Question: any reason to not use python 3.8 ? > > Regards > Marco > > > -- > Problem reports: https://cygwin.com/problems.html > FAQ: https://cygwin.com/faq/ > Documentation:https://cygwin.com/docs.html > Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple > -- Sharuzzaman Ahmat Raslan -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
