[issue1757057] IDLE + BeautifulSoup = Error

Mark Lawrence added the comment: Can we close this given "This is caused by a bug in BeautifulSoup which was fixed in version 3.0.5." from msg84412? -- nosy: +BreamoreBoy resolution: -> invalid status: open -> pending ___ Python tracker

[issue1757057] IDLE + BeautifulSoup = Error

Tal Einat added the comment: Sending a code object back to the parent process and having it deal with the situation sounds very unpleasant indeed! I think a completely different type of solution may be possible. In general, I can't think of any reason for IDLE to pickle "user objects" from the

[issue1757057] IDLE + BeautifulSoup = Error

Guilherme Polo added the comment: > IMO IDLE should check for any exception > (not just pickle.PicklingError) when trying to pickle an object for > sending to the parent process. If pickle doesn't work, for whatever > reason, IDLE can still try to work around it with str() and/or repr(). > Do y

[issue1757057] IDLE + BeautifulSoup = Error

Tal Einat added the comment: To recreate use BeautifulSoup 3.0.4 and run the following: >>> from BeautifulSoup import BeautifulSoup >>> soup = BeautifulSoup("aa>> x = soup.find('html').contents[0] >>> x u'aa' >>> print x Traceback (most recent call last): File "", line 1, in print x Run

[issue1757057] IDLE + BeautifulSoup = Error

Guilherme Polo added the comment: I can't seem to reproduce this here. I've tried both python 2.4.5 and 2.5.2 using beautifulsoup 3.0.7. I also used the sample html attached in that email as well part of the code that is supposed to cause the problem, and I can also run pickle on the body's cont