[issue34022] Python 3.7: 6 tests failed on OpenSUSE and Debian

Matej Cepl added the comment: Yes, it must be something in the chroot, because when run in the plain command line, all tests as well on openSUSE Tumbleweed (with the latest updates). 393 tests OK. 1 test failed: test_epoll 21 tests skipped: test_ctypes test_devpoll test_idle test_kq

[issue34027] python 3.7 openpty/forkpty build failure on macOS

Daiderd Jordan added the comment: Oh interesting, so it only used to worked by accident. I should have looked at the 3.6 log more closely. -- ___ Python tracker ___ _

[issue34019] webbrowser: wrong arguments for Opera browser.

Bumsik Kim added the comment: $opera --version 53.0.2907.68 $opera -remote "openURL(https://google.com,new-window)" would open a broken link: http://openurl%28https//google.com,new-window) I found that problem while answering a StackOverflow question: https://stackoverflow.com/questions/51

[issue34019] webbrowser: wrong arguments for Opera browser.

Pablo Galindo Salgado added the comment: Sorry, you are right! It seems that my Opera opened another tab with Google by default and I was confused by that. Thanks for the context. -- ___ Python tracker

[issue34019] webbrowser: wrong arguments for Opera browser.

Bumsik Kim added the comment: No problem :) To add more, the Opera's documentation (https://www.opera.com/docs/switches) says: "This document was last updated for Opera 11.61" This is the reason I guessed Opera changed its CLI format to Chrome's and forget to document it -- __

[issue33649] asyncio docs overhaul

Jim DeLaHunt added the comment: I'm a developer using Python in my application. I just spent the last couple of weeks learning about asyncio with the present documentation. I am very happy to see that work is underway for improved documentation. I would be glad to take on writing tasks or to

[issue34027] python 3.7 openpty/forkpty build failure on macOS

Orivej Desh added the comment: The explicit conditional on __APPLE__ can be avoided with the attached patch. (Tested on NixOS and macOS with Nixpkgs.) -- nosy: +orivej Added file: https://bugs.python.org/file47666/darwin-libutil.patch ___ Python tr

[issue34027] python 3.7 openpty/forkpty build failure using nix package manager macOS environment

Ned Deily added the comment: Thanks for the suggested patch but I am not persuaded that there is a problem needing fixing on the Python side. As I see it, Python's posixmodule builds fine in the environments we claim to support, including macOS, and has for a long time. It appears that the

[issue34011] Default preference not given to venv DLL's

Eryk Sun added the comment: Offhand I don't know why it copies PYD and DLL files from the DLLs directory. It's part of the standard library. The virtual environment should only need to copy or symlink the binaries in the application directory, such as python.exe, pythonw.exe, vcruntime<###>.

[issue34011] Default preference not given to venv DLL's

Change by Eryk Sun : -- versions: +Python 3.7, Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue34027] python 3.7 openpty/forkpty build failure using nix package manager macOS environment

Orivej Desh added the comment: I understand the desirability of avoiding potential problems on supported platforms (given that you can not test building Python on all of them) and recognize that both options you have given are reasonable, but as I see it posixmodule.c incorrectly uses autoco

[issue25345] Unable to install Python 3.5 on Windows 10

Change by INADA Naoki : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-

[issue34011] Default preference not given to venv DLL's

Vinay Sajip added the comment: The code that does the copy is the original PEP 405 implementation code (from 26 May 2012). I'm fairly sure that these files were copied over only because (at least prior to the Python 3.3 release in September 2012) they were needed to be in the venv for the ve

[issue34011] Default preference not given to venv DLL's

Vinay Sajip added the comment: Hmmm. I managed to find a machine to install Python3.3.0 on, and it appears that even with that copy suite removed, the tests still work. So possibly it's something that changed between 3.3.0 alpha and 3.3.0 final. I can try removing the copy code for 3.8 but I

[issue34027] python 3.7 openpty/forkpty build failure using nix package manager macOS environment

Daiderd Jordan added the comment: Even tho it's headers are not /usr/lib/libutil.dylib is available on every macOS system. Unlike on bsd this doesn't include the relevant symbols for openpty/forkpty, that's why I used an __APPLE__ condition but including both also works fine. Assuming it's h

<    1   2