google-code-export / gdata-python-client

Automatically exported from code.google.com/p/gdata-python-client
1 stars 0 forks source link

testToAndFromStringWithData test fails #484

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. run the tests
2.
3.

What is the expected output? What do you see instead?

FAIL: testToAndFromStringWithData (gdata_tests.docs_test.DocumentListEntryTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/ports/pobj/py-gdata-2.0.13/gdata-2.0.13/tests/gdata_tests/docs_test.py", line 39, in testToAndFromStringWithData
    'spreadsheet%3Asupercalifragilisticexpealidocious')
AssertionError: 
'https://docs.google.com/feeds/documents/private/full/spreadsheet%3Asupercalifra
gilisticexpealidocious' != 
'http://docs.google.com/feeds/documents/private/full/spreadsheet%3Asupercalifrag
ilisticexpealidocious'

What version of the product are you using?
2.0.13

Please provide any additional information below.
Python 2.6.6

As the assertion is about https != http perhaps this is connected
to issue 371?

Original issue reported on code.google.com by minusf on 6 Jan 2011 at 11:01

GoogleCodeExporter commented 9 years ago
I encountered this fail with gdata-2.0.13. But it disappeared with lastest 
codes:

Result from "$ hg summary"
changeset:   921:075dae7f62a2
tag:         tip
date:        Mon Dec 20 02:07:45 2010 -0500
summary:     Fixing tests/gdata_tests/docs/service_test.py, quite drastically.

I investigated for a while. I found it might have something to do with ssl of 
client:

client = gdata.docs.service.DocsService()
print `client.ssl` # True in lastest codes, False in gdata-2.0.13

Original comment by im.wilso...@gmail.com on 12 Jan 2011 at 3:25

GoogleCodeExporter commented 9 years ago
Updated my environment:
python: 2.6.6
OS: ubuntu 10.10

Original comment by im.wilso...@gmail.com on 12 Jan 2011 at 3:29

GoogleCodeExporter commented 9 years ago
Yep, I fixed this in head.  When we cut a new release, all should be well.

Original comment by vicfry...@google.com on 12 Jan 2011 at 7:02