Project

Profile

Help

Issue #2860

Python3 weakref tracebacks in the log

Added by amacdona@redhat.com over 4 years ago. Updated almost 3 years ago.

Status:
CLOSED - NOTABUG
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Traceback (most recent call last):
  File "/usr/lib64/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable

This is an upstream python 3 bug. https://bugs.python.org/issue29519.

History

#1 Updated by bmbouter over 4 years ago

We use Python3 from the python-35 scl (iirc). I think we need to wait for the SCL team to upgrade to an SCL version that doesn't have that Python bug.

After a newer SCL is available, do we need to take an action to consume that SCL for Pulp? I'm trying to figure out what we are waiting on, how we know that thing is done, and what action we need to take (if any) after that.

#2 Updated by amacdona@redhat.com over 4 years ago

Not sure. I filed this for 2 reasons. (1) in case we need to take action to upgrade Python. (2) So users/devs who see this won't take the time to look into it.

#3 Updated by ttereshc over 4 years ago

  • Status changed from NEW to CLOSED - NOTABUG
  • Triaged changed from No to Yes

Nothing to do on the Pulp side.
This bug is fixed in Python 3.5.4 and 3.6.1.

#4 Updated by bmbouter almost 3 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF