Description of problem: I was trying to create a virtualenv using python 3 when this happened. Version-Release number of selected component: python2-virtualenv-16.0.0-4.fc28 Additional info: reporter: libreport-2.9.5 cmdline: /usr/bin/python3 /usr/lib/python2.7/site-packages/virtualenv.py -p python3 env crash_function: copyfile exception_type: shutil.SameFileError executable: /usr/lib/python2.7/site-packages/virtualenv.py interpreter: python3-3.6.6-1.fc28.x86_64 kernel: 4.18.7-200.fc28.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: shutil.py:104:copyfile:shutil.SameFileError: '/usr/bin/python3' and '/home/kelynpaul/Desktop/DevChallenge/FlaskProjects/TerminalBlog/env/bin/python3' are the same file Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/virtualenv.py", line 2358, in <module> main() File "/usr/lib/python2.7/site-packages/virtualenv.py", line 712, in main symlink=options.symlink) File "/usr/lib/python2.7/site-packages/virtualenv.py", line 932, in create_environment site_packages=site_packages, clear=clear, symlink=symlink)) File "/usr/lib/python2.7/site-packages/virtualenv.py", line 1248, in install_python shutil.copyfile(executable, py_executable) File "/usr/lib64/python3.6/shutil.py", line 104, in copyfile raise SameFileError("{!r} and {!r} are the same file".format(src, dst)) shutil.SameFileError: '/usr/bin/python3' and '/home/kelynpaul/Desktop/DevChallenge/FlaskProjects/TerminalBlog/env/bin/python3' are the same file Local variables in innermost frame: follow_symlinks: True dst: '/home/kelynpaul/Desktop/DevChallenge/FlaskProjects/TerminalBlog/env/bin/python3' src: '/usr/bin/python3'
Created attachment 1488020 [details] File: backtrace
Created attachment 1488021 [details] File: cgroup
Created attachment 1488022 [details] File: cpuinfo
Created attachment 1488023 [details] File: environ
Created attachment 1488024 [details] File: mountinfo
Created attachment 1488025 [details] File: namespaces
Created attachment 1488026 [details] File: open_fds
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.