Bug 233321 - devel/py-pip: ModuleNotFoundError: no module named xml (py36-pip)
Summary: devel/py-pip: ModuleNotFoundError: no module named xml (py36-pip)
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Walter Schwarzenfeld
URL:
Keywords: needs-qa
Depends on:
Blocks:
 
Reported: 2018-11-19 14:27 UTC by Bogdan Artyushenko
Modified: 2020-01-31 19:53 UTC (History)
3 users (show)

See Also:

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

Note You need to log in before you can comment on or make changes to this bug.
Description Bogdan Artyushenko 2018-11-19 14:27:24 UTC 
Hi,
I've recently  installed:
pkg install pip-3.6
on FreeBDS 12.0-BETA4
when I run it I got:
  pip-3.6
Traceback
File "usr/local/bin/pip-3.6, line 6 in <module>
  from pkg_resources import load_entry_point
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.pu" line 35, in <module>
   import plistlib
  File "/usr/local/lib/python3.6/plitlib.py" line 65, in <module>
   from xml.parsers.expat import ParserCreate
ModuleNotFoundError: no module named xml
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2018-11-20 02:57:39 UTC 
Thank you for your report Bogdan

xml is a Python standard library module provided by lang/python* packages. The error appears to indicate a corrupt or modified system Python installation or environment.

Can you please provide, as attachments:

- pkg version -v output
- details of your package configuration (pkg/FreeBSD.conf)
- A full/recursive list (ls -Rla) of the contents of /usr/local/lib/python3.6

I would also try, to refresh the installation:

1) pkg delete -f python36 py36-pip
2) pkg update -f
3) pkg install python36 py36-pip

Note also that using pip (as root) to install, update or manage packages in the *system* Python environment is unsupported, which is described in the pip pkg-message upon installation.
Comment 2 Walter Schwarzenfeld 2019-08-08 01:40:00 UTC 
Is this still relevant?
Comment 3 Walter Schwarzenfeld 2020-01-31 19:53:17 UTC 
Feedback timeout! Please, reopen if there still problems.