Custom Query (1174 matches)
Results (184 - 186 of 1174)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5373 | fixed | Latest flup removes Python 2 compatibility | ||
| Description |
We recommend installing flup [1] for fcgi deployments. The latest version of flup on PyPI [2] claims to be a "Python 3.x-only version." Two people have reported issues with this version of flup in a Python 2 installation. One person shared the following log on IRC. File "build/bdist.linux-x86_64/egg/flup/server/paste_factory.py", line 125, in run_fcgi_fork File "build/bdist.linux-x86_64/egg/flup/server/fcgi_fork.py", line 60, in <module> File "build/bdist.linux-x86_64/egg/flup/server/fcgi_base.py", line 45, in <module> ImportError: No module named _dummy_thread I don't know if flup has abandoned Python 2 or if this is just a mistake, but it causes issues for people deploying fresh MediaGoblin installs. We could amend the documentation to suggest installing a specific version of flup, or perhaps we could just go ahead and add flup to setup.py, pinned to a specific version. [1] https://mediagoblin.readthedocs.org/en/latest/siteadmin/deploying.html?highlight=flup#install-mediagoblin-and-virtualenv [2] https://pypi.python.org/pypi/flup/1.0.3.dev20151210 |
|||
| #5372 | fixed | test_comment_notification fails with werkzeug 0.11 or newer | ||
| Description |
It seems any Werkzeug version 0.11 or higher breaks out test_comment_notification test, it seems the port number is dropped from the URL in the email body: I've converted the "\n" to newlines to make it more readable. Werkzeug 0.10.4 or below:
Werkzeug 0.11.0 and above:
We could just change it to have the port number in the test and it would pass however that means pinning werkzeug at 0.11 or higher, this may or may not be a problem I don't know, we already pin it at 0.7.0 or higher. |
|||
| #5371 | fixed | Collection atom feeds throw server error | ||
| Description |
On latest master, I get the following error when trying to view the atom feed of a collection. Atom feed of a user still works fine. Error - <type 'exceptions.TypeError'>: 'LocalUser' object is not callable URL: https://goblinrefuge.com/mediagoblin/u/andrew/collection/concerts/atom/ File '/path/to/mediagoblin/lib/python2.7/site-packages/paste/exceptions/errormiddleware.py', line 144 in __call__ app_iter = self.application(environ, sr_checker) File '/path/to/mediagoblin/mediagoblin/app.py', line 342 in __call__ return self.call_backend(environ, start_response) File '/path/to/mediagoblin/lib/python2.7/site-packages/Werkzeug-0.10.1-py2.7.egg/werkzeug/wsgi.py', line 591 in __call__ return self.app(environ, start_response) File '/path/to/mediagoblin/mediagoblin/app.py', line 276 in call_backend return self._finish_call_backend(request, environ, start_response) File '/path/to/mediagoblin/mediagoblin/app.py', line 318 in _finish_call_backend response = controller(request) File '/path/to/mediagoblin/mediagoblin/user_pages/views.py', line 626 in collection_atom_feed 'name': obj.get_actor().username, TypeError: 'LocalUser' object is not callable |
|||
