Bug#1070206: python3-pip: The options --log and --log-file have no effect on the install command
Hi Manny (2024.05.03_09:01:10_+) > I would report upstream if the bug tracker were hosted in a more open > and neutral place. Microsoft venues are places I will not go to > interact, apart from searching to see if a report already exists. > Github in particular has access problems. I can understand and respect that. But at the same time, I am not your bug proxy. So this bug will just sit here, and not be much use to anyone. BTW, there is a #pip on the PyPA discord, if you want to interact with Pip upstream, off GitHub. > Debian shelters users with this bug reporting policy¹: > > “Don't file bugs upstream > >If you file a bug in Debian, don't send a copy to the upstream >software maintainers yourself, as it is possible that the bug >exists only in Debian. If necessary, the maintainer of the package >will forward the bug upstream.” I generally think that's a bad policy. There are situations where that makes sense. But in most cases, filing the bug upstream is the best way to get it fixed. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1070206: python3-pip: The options --log and --log-file have no effect on the install command
> Please report this upstream to https://github.com/pypa/pip > This does not sound Debian-specific at all. > > I can't reproduce the bug, without writing a proxy that causes a failure > like you had, which is far beyond the effort I'm willing to put in here. > You're in a much better position to advocate for this bug upstream than > I am. I agree with all of that. I would report upstream if the bug tracker were hosted in a more open and neutral place. Microsoft venues are places I will not go to interact, apart from searching to see if a report already exists. Github in particular has access problems. Debian shelters users with this bug reporting policy¹: “Don't file bugs upstream If you file a bug in Debian, don't send a copy to the upstream software maintainers yourself, as it is possible that the bug exists only in Debian. If necessary, the maintainer of the package will forward the bug upstream.” I don’t expect anyone to mirror it upstream because I think everyone should equally have the option to avoid Microsoft’s platform, and also I agree with the Debian project principle to not impose work on others. This report has the upstream tag so upstream developers can filter on that tag and so downstream devs can filter it out. I just noticed the --log and --log-file options function correctly in one case. Part of the problem might be interplay with a bug² where pip continues even if there is a problem with the log file location for the user running it. Reproducing it myself might be non-trivial since I would need an unlimited internet connection to test more installations (which do not indicate their size prior to action). So perhaps the report could be closed on that basis anyway. There are several more upstream bugs to report against pip*. I intend to report them in Debian’s BTS using the upstream tag, unless no one wants them. I realise that they may never be seen by someone who would work them. ¹ https://www.debian.org/Bugs/Reporting ² https://github.com/pypa/pip/issues/114
Bug#1070206: python3-pip: The options --log and --log-file have no effect on the install command
Hi Manny (2024.05.01_19:47:09_+) Please report this upstream to https://github.com/pypa/pip This does not sound Debian-specific at all. I can't reproduce the bug, without writing a proxy that causes a failure like you had, which is far beyond the effort I'm willing to put in here. You're in a much better position to advocate for this bug upstream than I am. Stefano -- Stefano Rivera http://tumbleweed.org.za/
Bug#1070206: python3-pip: The options --log and --log-file have no effect on the install command
Package: python3-pip Version: 23.0.1+dfsg-1 Severity: normal Tags: upstream X-Debbugs-Cc: debbug.python3-...@sideload.33mail.com This command was executed inside a venv: ===8< $ pip install --proxy 127.0.0.1:8118 --log-file "$log_dir"/pip-argostranslate_install_"$(date +%F)".err --log "$log_dir"/pip-argostranslate_install_"$(date +%F)".log -e . ===8< The operation failed about 150 megs into the download and dumped a stack trace to the terminal. The "$log_dir" contained no log files. I also used a similar command on Bullseye likely version 20.3.4-4+deb11u1 of python3-pip, without using a venv. The operation succeeded, but the logfile was not produced. I cannot say that with certainty though. My notes indicate that I used the --log* options, but today the old log files are not there; and nor are the new ones. I doubt I would have deleted the old logs, but it’s remotely possible. In any case, certainly the bug is present in today’s version. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-28-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-pip depends on: ii ca-certificates 20230311 ii python3 3.11.2-1+b1 ii python3-distutils 3.11.2-3 ii python3-setuptools 66.1.1-1 ii python3-wheel 0.38.4-2 Versions of packages python3-pip recommends: ii build-essential 12.9 ii python3-dev 3.11.2-1+b1 python3-pip suggests no packages. -- no debconf information
