Bug 1721328 - ImportError: cannot import name 'wsgi' from 'gevent'
Summary: ImportError: cannot import name 'wsgi' from 'gevent'
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: python-bottle
Version: 30
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-17 23:23 UTC by Cesar Eduardo Barros
Modified: 2020-05-26 15:45 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-26 15:45:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github bottlepy bottle issues 1065 0 None closed gevent-1.3.0 and bottle 0.12.13 2020-05-21 20:46:26 UTC

Description Cesar Eduardo Barros 2019-06-17 23:23:56 UTC
Description of problem:

Attempting to use python3-bottle with gevent fails with an ImportError.


Version-Release number of selected component (if applicable):

python3-bottle-0.12.13-7.fc30.noarch
python3-gevent-1.3.6-2.fc30.x86_64


How reproducible:

Always.


Steps to Reproduce:
1. Install python3-bottle and python3-gevent
2. Run: python3 -c "from bottle import run; run(host='localhost', port='12345', server='gevent')"


Actual results:

Bottle v0.12.13 server starting up (using GeventServer())...
Listening on http://localhost:12345/
Hit Ctrl-C to quit.

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python3.7/site-packages/bottle.py", line 3126, in run
    server.run(app)
  File "/usr/lib/python3.7/site-packages/bottle.py", line 2906, in run
    from gevent import wsgi, pywsgi, local
ImportError: cannot import name 'wsgi' from 'gevent' (/usr/lib64/python3.7/site-packages/gevent/__init__.py)


Expected results:

Working without an ImportError.


Additional info:

According to https://github.com/bottlepy/bottle/issues/1065 this bug should be fixed by version 0.12.14 of bottle, so just packaging that newer minor release should be enough to fix this issue.

Comment 1 Ben Cotton 2020-04-30 21:46:54 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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 '30'.

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 30 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.

Comment 2 Ben Cotton 2020-05-26 15:45:10 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.


Note You need to log in before you can comment on or make changes to this bug.