[issue20136] Logging: StreamHandler does not use OS line separator.

2014-01-06 Thread A. Libotean
New submission from A. Libotean: The StreamHandler implementation uses hardcoded Unix/Linux line separators. This generates inconveniences when running on Windows as the file viewers expect DOS line terminators. I've attached a fix that will use os.linesep as the line terminator thus making

[issue20137] Logging: RotatingFileHandler computes string length instead of byte representation length.

2014-01-06 Thread A. Libotean
New submission from A. Libotean: Current implementation of RotatingFileHandler ignores the encoding when computing the entry byte length. I've attached a modified version that will compute the entry lenght in bytes. -- components: Library (Lib) files: rotatingfilehandler.py messages

[issue20137] Logging: RotatingFileHandler computes string length instead of byte representation length.

2014-01-13 Thread A. Libotean
A. Libotean added the comment: Sure, will come back shortly with a patch. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20137 ___ ___ Python

[issue20136] Logging: StreamHandler does not use OS line separator.

2014-01-13 Thread A. Libotean
A. Libotean added the comment: Let me write also a test for this and come back with a reply. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20136

[issue20136] Logging: StreamHandler does not use OS line separator.

2014-02-05 Thread A. Libotean
A. Libotean added the comment: You can go ahead and close this. I ran some tests and concluded that indeed the IO system will take care of the line separators. Sorry to have wasted your time. -- ___ Python tracker rep...@bugs.python.org http

[issue20137] Logging: RotatingFileHandler computes string length instead of byte representation length.

2014-02-05 Thread A. Libotean
A. Libotean added the comment: Which encoding are you using, such that the difference in length between encoded and decoded messages is significant? I agree right off the bat that the error in size is not significant. Only the length of the last appended line is computed erroneously. I'm

[issue22272] sqlite3 memory leaks in cursor.execute

2014-08-25 Thread A. Libotean
New submission from A. Libotean: There are significant memory leaks when multiple insert statements are executed with distinct values. sqlite3 version is 2.6.0 The attached file contains two variants: * one which uses string interpolation to build the query: this generates severe leakeage

[issue22272] sqlite3 memory leaks in cursor.execute

2014-08-26 Thread A. Libotean
A. Libotean added the comment: I'm not sure that it's a leak because it doesn't depend on the number of queries nor the number of run of the test. It's maybe an internal sqlite cache. You're right, the leak does not increase past ~300 queries executed

[issue22272] sqlite3 memory leaks in cursor.execute

2014-08-27 Thread A. Libotean
A. Libotean added the comment: Can we close this issue then? Yes, please. Sorry for the false alarm. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22272