[Python-Dev] Sourceforge Interface Concerns

[Fred L. Drake, Jr.]

Andy Robinson writes:
 > I find the web interface totally unusable from IE5 and Netscape 4.XX,
 > working over 64k lines or dialup lines.  Once one logs in via SSL, only
 > about one click in five ever returns a sensible page, and most just time out

  I've not been able to reproduce this behavior; the Web interface
seems to work well with IE5 and Netscape 4.XX for me; the only problem
I've had with IE5 is accessing a project's anonymous FTP area from the
project page (IE5 just froze completely).  Netscape didn't exhibit
that problem for me and allowed perfectly reasonable use.
  Sometimes it seems a little slow, but I attribute that to load and
the public-key crypto using SSH for CVS access; I understand that CVS
doesn't have the most efficient wire-protocol either.
  I should note that I've mostly used it over T1 and cable modem
links; I don't know that smaller pipes would make a huge difference
though.  I'd be more suspicious of trans-Atlantic linkage than
anything else without having more information.  Routing can do strange
things, so you may be getting the worst-possible link for SourceForge
while other things get better routes, but I wouldn't expect that to be
terribly consistent.

 > How many people here have actually created accounts for themselves on
 > SourceForge and tried to do stuff when logged in - raise bugs and so on?
 > Did it work for you?  We ought to get a few data points before making this
 > the way Python is managed.

  I've never had the kind of problems you describe.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at beopen.com>
BeOpen PythonLabs Team Member