After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 316635 - Pyblosxom import error
Pyblosxom import error
Status: RESOLVED FIXED
Product: website
Classification: Infrastructure
Component: developer.gnome.org
current
Other All
: Normal normal
: ---
Assigned To: GNOME Web maintainers
GNOME Web maintainers
Depends on:
Blocks:
 
 
Reported: 2005-09-18 16:18 UTC by Brent Smith (smitten)
Modified: 2006-01-12 17:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Brent Smith (smitten) 2005-09-18 16:18:52 UTC
Please describe the problem:
The "Latest News" section of the page is not working.

Steps to reproduce:
1. navigate to http://developer.gnome.org/projects/gup/


Actual results:
The page comes up, but there is an error importing news

Expected results:


Does this happen every time?


Other information:
ImportError	Python 2.2.3: /usr/bin/python2.2
Sun Sep 18 12:15:57 2005

A problem occurred in a Python script. Here is the sequence of function calls
leading up to the error, in the order they occurred.

 /usr/local/www/developer.gnome.org/projects/gup/news/blog
   23 if __name__ == '__main__':
   24     from Pyblosxom.pyblosxom import PyBlosxom
   25     from Pyblosxom.Request import Request
   26     import os, cgi
   27 
Pyblosxom undefined, Request undefined

ImportError: No module named Request
      __doc__ = "Import can't find module, or can't find name in module."
      __getitem__ = <bound method ImportError.__getitem__ of
<exceptions.ImportError instance>>
      __init__ = <bound method ImportError.__init__ of <exceptions.ImportError
instance>>
      __module__ = 'exceptions'
      __str__ = <bound method ImportError.__str__ of <exceptions.ImportError
instance>>
      args = ('No module named Request',)
Comment 1 Quim Gil 2005-12-19 22:18:16 UTC
What if we simply take out this blog import code from the wiki page?

I know it's not the best solution but at least leaves the page in a more... usable level.
Comment 2 Quim Gil 2005-12-26 14:56:18 UTC
Moving to the "developer" component due to deletion of component gup.
Comment 3 Calum Benson 2006-01-12 17:21:54 UTC
I commented out the offending code yesterday-- it hasn't worked for months, nor has the blog it referred to been updated in at least a year. (In fact I thought I'd already got rid of this ages ago, but obviously not.)