Bug 25554 - Warning issued from python 3.8 when mercurial is launched
Summary: Warning issued from python 3.8 when mercurial is launched
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Philippe Makowski
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-12 23:41 CEST by Frank Griffin
Modified: 2020-10-06 02:20 CEST (History)
1 user (show)

See Also:
Source RPM: mercurial
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Frank Griffin 2019-10-12 23:41:09 CEST 
All of a sudden any invocation of mercurial gives:

[ftg@ftgme2 ~/data/DPY.V311]$ hg status
/usr/lib64/python3.8/os.py:1021: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  return io.open(fd, *args, **kwargs)

I'm not sure whether this is due to a python specification in mercurial or a broken default in python itself.
Comment 1 Frank Griffin 2019-10-12 23:57:42 CEST 
This situation predated the following error from urpmi, but just in case:

Installation failed:    file /usr/lib/python3.8/site-packages/pyserial-3.4-py3.8.egg-info from install of python3-serial-3.4-3.mga8.noarch conflicts with file from package python3-serial-3.4-2.mga8.noarch
Comment 2 Lewis Smith 2019-10-14 11:31:18 CEST 
The error you report is a 'warning'; does Mercurial continue OK despite it? If so, please reduce the severity to minor. Benign warnings are so common...

Assigning to philippem for Mercurial, also as packager for python-serial.

Assignee: bugsquad => makowski.mageia
CC: (none) => python

Frank Griffin 2019-10-14 13:56:35 CEST

Severity: normal => minor

Comment 3 Frank Griffin 2020-10-06 02:20:18 CEST 
Appears to be working now...

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.