[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

2010-01-25 Thread Sérgio
Sérgio added the comment: Hi, with python-2.6.2-2.fc12.i686 In: x ="http://www.somesite.com/images/rubricas/"; In: urlparse.urljoin(x, '07.11.2009-9:54:12-1.jpg') Out: '07.11.2009-9:54:12-1.jpg' !? In: urlparse.urljoin(x, './07.11.2009-9:54:12-1.jpg

[issue3932] HTMLParser cannot handle '&' and non-ascii characters in attribute names

2009-12-12 Thread Sérgio
Sérgio added the comment: the patch fix parsing in simple tag a with title with ?! and accents like this: -- nosy: +sergiomb2 ___ Python tracker <http://bugs.python.org/issue3

[issue9646] Mutable default function parameter warning

2010-08-19 Thread Sérgio Surkamp
New submission from Sérgio Surkamp : The documentation states that the default value of function parameter, if mutable, can change it's default value at runtime due to be evaluated only once on function object creation. I would like to suggest the inclusion of an default language warning

[issue7779] smtplib SASL PLAIN authentication error

2010-01-25 Thread Sérgio Surkamp
New submission from Sérgio Surkamp : There is bug in PLAIN mechanism's of smtplib. The generated base64 string fail when the password start with numbers. As long as I could find, the error occur in method encode_plain. Using the null character (\0) in hexadecimal representation (\x00)

[issue7779] smtplib SASL PLAIN authentication error

2010-01-25 Thread Sérgio Surkamp
Sérgio Surkamp added the comment: The SASL protocol says that the encoded base64 should be formed from: null + login + null + password The smtplib is not doing it, instead its "converting" the \012 (\0 + 2 first chars from password) in the char "\n", and it's right

[issue7779] smtplib SASL PLAIN authentication error

2010-01-25 Thread Sérgio Surkamp
Sérgio Surkamp added the comment: Got your point. Sorry. -- ___ Python tracker <http://bugs.python.org/issue7779> ___ ___ Python-bugs-list mailing list Unsub

[issue4177] Crash in MIMEText on FreeBSD

2008-10-22 Thread Sérgio Surkamp
New submission from Sérgio Surkamp <[EMAIL PROTECTED]>: If you try to create a MIMEText object from a very large string (test case include a 40Mbytes string), the program just eat all the CPU and with high memory usage or raise a MemoryError. Sometimes it just deadlocks when using _c

[issue4177] Crash in MIMEText on FreeBSD

2008-10-23 Thread Sérgio Surkamp
Sérgio Surkamp <[EMAIL PROTECTED]> added the comment: Testing on Linux: $ ulimit -m 128000 $ ulimit -v 196000 $ python test_MIMEText.py [...] Traceback (most recent call last): File "test_MIMEText.py", line 23, in txt = MIMEText(buffer, _subtype="plain", _ch

[issue4177] Crash in MIMEText on FreeBSD

2008-10-24 Thread Sérgio Surkamp
Sérgio Surkamp <[EMAIL PROTECTED]> added the comment: > Your text file is ~40 MB. Python may allocate mutiple objects bigger than 40 MB to create the email content. The algorithm should be changed to work on a stream (process small chunks, eg. 4 KB) instead of manipule the full text

[issue4177] Crash in MIMEText on FreeBSD

2008-10-24 Thread Sérgio Surkamp
Sérgio Surkamp <[EMAIL PROTECTED]> added the comment: - FreeBSD version? FreeBSD 7.0-RELEASE - CPU, memory? CPU: 2 x Pentium III 1.133 GHz Memory: 512 Mbytes - Full Python version? Python 2.5.2 (r252:60911, Oct 2 2008, 10:03:50) [GCC 4.2.1 20070719 [FreeBSD]] on freebsd7 > O

[issue4177] Crash in MIMEText on FreeBSD

2008-10-24 Thread Sérgio Surkamp
Sérgio Surkamp <[EMAIL PROTECTED]> added the comment: When I first saw the problem, the email system queue was stopped about 2 days (weekend) :-( The email system control the number of open threads, so I wasn't opening new threads too and issuing many warnings about it on logs Anyw

[issue4177] Crash in MIMEText on FreeBSD

2008-10-28 Thread Sérgio Surkamp
Sérgio Surkamp <[EMAIL PROTECTED]> added the comment: Ok. Something is very wrong with our code too. I have dumped the text that's cousing the "freeze" and run it using the test case scripts. It worked slow, but worked. It seems that our application is eating too many memo

[issue7390] inconsistent type return

2009-11-24 Thread Sérgio Surkamp
New submission from Sérgio Surkamp : The type function returns inconsistent value depending on class hierarchy. >>> class X: ... pass ... >>> x = X() >>> type(x) >>> class Y(object): ... pass ... >>> x = Y() >>> type(x) >>

[issue1628484] Python 2.5 64 bit compile fails on Solaris 10/gcc 4.1.1

2008-04-10 Thread Sérgio Durigan Júnior
Sérgio Durigan Júnior <[EMAIL PROTECTED]> added the comment: Hi, I'd like to know the status of this issue. I'm having the same problems here with PPC64, and the patch that Bob Atkins has sent works fine for me too. Would you intend to apply this patch in upstream? T

[issue1628484] Python 2.5 64 bit compile fails on Solaris 10/gcc 4.1.1

2008-04-10 Thread Sérgio Durigan Júnior
Sérgio Durigan Júnior <[EMAIL PROTECTED]> added the comment: Hi Martin, Thanks for your quick answer. I'd like to know what can we do to push this patch into upstream. Does the fact that the patch is posted in a bug report (and not in a developer's mailing list) is slowing do

[issue1628484] Python 2.5 64 bit compile fails on Solaris 10/gcc 4.1.1

2008-04-11 Thread Sérgio Durigan Júnior
Sérgio Durigan Júnior <[EMAIL PROTECTED]> added the comment: Hi Martin, Actually, I know that you can use CC to do it, but IMHO that's not the correct approach. I understand too you concern about adding @CFLAGS@, but I think the user should be able to define his/her own CFLAGS, and

[issue858809] Use directories from configure rather than hardcoded

2008-04-11 Thread Sérgio Durigan Júnior
Sérgio Durigan Júnior <[EMAIL PROTECTED]> added the comment: Hi, Continuing with my effort to improve Python's build system, I'd really like to know why this issue has not been solved yet. I mean, apparently this problem is still present in Python 2.5, since I can't chan

[issue1628484] Python 2.5 64 bit compile fails on Solaris 10/gcc 4.1.1

2008-04-14 Thread Sérgio Durigan Júnior
Sérgio Durigan Júnior <[EMAIL PROTECTED]> added the comment: Hi Martin, This is what you get when you try to build a 64-bit Python on a biarch machine (64-bit kernel, 32-bit userspace), using a gcc that generates natively 32-bit objects (therefore, you *must* pass the '-m64'

[issue1628484] Python 2.5 64 bit compile fails on Solaris 10/gcc 4.1.1

2008-04-15 Thread Sérgio Durigan Júnior
Sérgio Durigan Júnior <[EMAIL PROTECTED]> added the comment: Hi Martin, On Mon, 2008-04-14 at 20:04 +, Martin v. Löwis wrote: > Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > > > This is what you get when you try to build a 64-bit Python on a biarch > &

[issue1628484] Python 2.5 64 bit compile fails on Solaris 10/gcc 4.1.1

2008-04-15 Thread Sérgio Durigan Júnior
Sérgio Durigan Júnior <[EMAIL PROTECTED]> added the comment: On Tue, 2008-04-15 at 02:01 +, Bob Atkins wrote: > I don't know why you are resisting this change. I took the time to > report the bug, proposed a fix /_*and*_/ contributed the patch that > would make the