[issue7358] cStringIO not 64-bit safe

Martin v. Löwis added the comment: Gilles: it's really puzzling that you run into the issue. This is an assert, so in a regular build of Python, it should never trigger. Instead, it should trigger only in a debug build. Why are you running a debug build? -- ___

[issue15915] array.array does not support the buffer interface

Benjamin Peterson added the comment: array.array supports the old buffer interface not the new one, which PyObject_CheckBuffer is part of. -- nosy: +benjamin.peterson resolution: -> invalid status: open -> closed ___ Python tracker

[issue15419] distutils: build should use a version-specific build directory

Arfrever Frehtes Taifersar Arahesis added the comment: Currently users can run e.g.: $ python2.7 setup.py build -b build-2.7 install $ python3.2 setup.py build -b build-3.2 install If default name of build directory had to be changed, then it would be useful to also include name of Python imple

[issue15906] argparse add_argument() confusing behavior when type=str, default=

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue7358] cStringIO not 64-bit safe

Martin v. Löwis added the comment: Antoine: if you look at http://svn.python.org/view/python/branches/ssize_t/Modules/cStringIO.c?revision=41731&view=markup&pathrev=42382 you'll notice that IOobject and Iobject have pos and stringsize as int, whereas Oobject has it as Py_ssize_t. This must hav

[issue15915] array.array does not support the buffer interface

Ellery Newcomer added the comment: relevant question, then, is why does array not support the new buffer interface while str and bytearray support both old and new? -- ___ Python tracker __

[issue15915] array.array does not support the buffer interface

Benjamin Peterson added the comment: It simply wasn't converted in time for the 2.7 release. The new buffer API is considered something of a technical preview in Python 2.x. -- ___ Python tracker _

[issue15390] PEP 3121, 384 refactoring applied to datetime module

Alexander Belopolsky added the comment: I would like to split this issue to separate PEP 3121 changes from PEP 384. PEP 3121 state cleanup implementation is clearly an improvement "from a resource management point of view." On the other hand, I don't see much benefit for the datetime module

[issue15887] urlencode should accept generators or two elements tuples

Changes by Berker Peksag : -- versions: +Python 3.4 -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15916] change doctest DocTestSuite not to raise ValueError if no docstrings

New submission from Chris Jerdonek: Currently, calling doctest.DocTestSuite() raises a ValueError if the module passed to it has no docstrings. This was the subject of issue 14649. This issue is to discuss and possibly change DocTestSuite's behavior not to raise an exception in that situation

[issue15896] Sporadic EINVAL in nonblocking pipe os.read when forked child fails on Mac OS

Changes by Vitaly : Added file: http://bugs.python.org/file27170/test_fork_pipe_error.py ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue15896] Sporadic EINVAL in nonblocking pipe os.read when forked child fails on Mac OS

Vitaly added the comment: os.read() must also be allocating the read buffer in addition to calling the system read() function. I just uploaded a new test script "test_fork_pipe_error.py" that iterates in increasing or decreasing order over initial pipe read sizes and accumulates failed size v

[issue15793] Stack corruption in ssl.RAND_egd()

Roundup Robot added the comment: New changeset 706115cb2cdb by Jesus Cea in branch '2.7': Closes #15793: Stack corruption in ssl.RAND_egd(). Python 2.7 hasn't any issue about this, but add a test just to be sure http://hg.python.org/cpython/rev/706115cb2cdb New changeset 827bb0554f1f by Jesus C

[issue15793] Stack corruption in ssl.RAND_egd()

Jesús Cea Avión added the comment: Thanks for the detection and patch. I added a test to 2.7, even knowing it doesn't need it (2.7 is a dead end), for consistence. -- ___ Python tracker ___

[issue15912] Intermittent import failure

Eric Snow added the comment: Thinking about it, it may be worth adding a note to the docs for sys.modules making it clear about importlib.invalidate_caches(). I'll see about writing up a patch when I get a chance. -- status: pending -> open ___ Pyt

[issue15629] Add to regrtest the ability to run Lib and Doc doctests

Chris Jerdonek added the comment: > You should also see if there are more doctest-safe or more doctest-unsafe > tests, and mark the ones in the smallest group. Running the doctests for all .rst files in the Doc/ directory using the latest patch gave me the following: 299 tests [files] OK. 126

[issue15886] os.stat() docs repeat "specifying a file descriptor" support

Roundup Robot added the comment: New changeset d7ea7ec671ba by R David Murray in branch 'default': #15886: remove redundant phrase http://hg.python.org/cpython/rev/d7ea7ec671ba -- nosy: +python-dev ___ Python tracker

[issue15886] os.stat() docs repeat "specifying a file descriptor" support

R. David Murray added the comment: Thanks Masato. -- nosy: +r.david.murray resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue15629] Add to regrtest the ability to run Lib and Doc doctests

Chris Jerdonek added the comment: > Integrating this with regrtest requires some work, for example you would have > to count successes/failures, add skips for certain tests and resources to > control what tests should be run (there's currently a turtle going around on > my screen when I run `m

[issue15629] Add to regrtest the ability to run Lib and Doc doctests

Chris Jerdonek added the comment: > Sphinx does have a way to mark doctest snippets as "run this", "don't run > this". I believe that requires using 'make doctest' as the runner, The doctest module supports this natively (i.e. without the need for Sphinx) via its "skip" directive ("#doctest:

[issue15629] Add to regrtest the ability to run Lib and Doc doctests

Chris Jerdonek added the comment: > The reason is that Sphinx has extra facilities that allow docttests to work > without having to have "boilerplate" code in places where doing so would > disrupt the narrative flow. Yes, this seems to be true. Sphinx has a "testsetup" directive which lets yo

[issue15898] OSX TTY bug

Andrew Moffat added the comment: Below I attached a script that reproduces the behavior of an assertion error on a specific fork condition for a process with a pty. Here are the results Xubuntu x64: Python 2.7, parent_close_slave_before_child_write = False: WORKS Python 2.7, parent_close

[issue15851] Lib/robotparser.py doesn't accept setting a user agent string, instead it uses the default.

Senthil Kumaran added the comment: Hello Eduardo, I fail to see the bug in here. Robotparser module is for reading and parsing the robot.txt file, the module responsible for fetching it could urllib. robots.txt is always available from web-server and you can download the robot.txt by any means,

[issue15917] hg hook to detect unmerged changesets

New submission from Ezio Melotti: The attached Mercurial hook checks that all the changesets in a 3.x branch are merged with either another cset in the same branch or a cset in the following 3.x branch. This is to detect and prevent situations where people commit something on e.g. 3.2 and pus

[issue15898] OSX TTY bug

Martin v. Löwis added the comment: To me, this still looks like an OS bug. The difference between 2.7 and 3.2 seems to be that 3.2 will call the _nocancel syscalls, which I guess results from using a different version of the C library, or OSX deployment target, or something. However, the syste

[issue15851] Lib/robotparser.py doesn't accept setting a user agent string, instead it uses the default.

Eduardo A. Bustamante López added the comment: Hi Senthil, > I fail to see the bug in here. Robotparser module is for reading and > parsing the robot.txt file, the module responsible for fetching it > could urllib. You're right, but robotparser's read() does a call to urllib.request.urlopen to

[issue15882] _decimal.Decimal constructed from tuple

Stefan Krah added the comment: Thanks for the report and the patch. I used another approach that still validates the digits in the coefficient tuple even if it is not used. decimal.py allows any coefficient: >>> Decimal((0, ('n', 'a', 'n'), 'F')) Decimal('Infinity') _decimal raises: >>> Decim

[issue15882] _decimal.Decimal constructed from tuple

Changes by Stefan Krah : -- resolution: -> fixed stage: -> committed/rejected ___ Python tracker ___ ___ Python-bugs-list mailing li

<    1   2