[issue16607] Bad examples in documentation
Daniel Urban added the comment: As John Hampton have explained it, the documentation is actually correct. -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16607 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16671] logging.handlers.QueueListener sentinel should not be None
Andras Szalai added the comment:
What mislead me is:
The current code uses `is` and opposed to `==` which I assume is for the very
specific reason to match identity and not value.
The sentinel starts with a _, which to a casual reader (me) suggests that it's
a private implementation detail that I should not have to touch. (am I right on
this?)
http://plumberjack.blogspot.co.uk/2010/09/improved-queuehandler-queuelistener.html
In the introduction of this very same class you are also mentioning that:
... QueueListener is not even especially logging-specific: You can pass it as
a handler any object that has a handle method which takes a single argument,
and that method will be passed any non-sentinel object which appears on the
queue.
also
You should be able to paste QueueHandler and QueueListener into your own
code...
So suddenly logging in not the only documented use case.
And yes, I can override the sentinel in my subclass, yet it is named as
`_sentinel`, which again suggests do not touch to me.
It's a tiny inconsistency that may never come up again for anyone else, but I
just used a copy of the class and it came up for me. My tests caught it, I
fixed it up for my own use-case, case closed.
So honestly it's not the end of the world, but neither is changing it to a
safer default, like `{}` or even `self`.
I won't be bothering you with this issue anymore, so feel free to close it if
you want.
--
status: pending - open
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16671
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16671] logging.handlers.QueueListener sentinel should not be None
Vinay Sajip added the comment: The sentinel starts with a _, which to a casual reader (me) suggests that it's a private implementation detail that I should not have to touch. (am I right on this?) Python is a language for consenting adults, so nothing is off-limits, except that you need to know what you are doing when you make changes to internal attributes, and may not get support from the original author if something breaks. However, notice that I set it up as a class value which could be overridden at an instance level, rather than hard-coding None into the sentinel test. So, it *was* intended to be changed if needed, but it's more appropriate for a subclass to do that than a user of the class (not that a user is *forbidden* - that couldn't be enforced, anyway). -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16671 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16673] Corrections in the library OS (PEP8)
New submission from Raninho Fernandes: Community, I realized that there are libraries that do not follow the standard PEP8, in order to start to contribute, I am providing the OS patch. I do not know if has community interest in the corrections (PEP8). thank you -- files: os_pep8.patch keywords: patch messages: 177402 nosy: raninho priority: normal severity: normal status: open title: Corrections in the library OS (PEP8) Added file: http://bugs.python.org/file28300/os_pep8.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16673 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16673] Corrections in the library OS (PEP8)
Ezio Melotti added the comment: Thanks for your contribution, but we don't usually apply this kind of refactoring unless we are already making changes to the a specific part of the code. The reason is that even if they are trivial changes, there's an (admittedly small) chance of introducing bugs, and it makes the output of hg annotate more difficult to follow. Unless someone disagrees I think this can be closed as won't fix. -- components: +Library (Lib) nosy: +ezio.melotti resolution: - wont fix stage: - patch review status: open - pending type: - enhancement versions: +Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16673 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16607] Bad examples in documentation
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti stage: - committed/rejected ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16607 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5289] ctypes.util.find_library does not work under Solaris
Changes by Aaron Iles aaron.i...@gmail.com: -- nosy: +aliles ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5289 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16673] Corrections in the library OS (PEP8)
R. David Murray added the comment: That is indeed our standard policy. And yes, thank you for trying, Raninho. A good way to make an initial contribution is to look for modules that don't yet have full test coverage (there are a lot) and add tests. The devguide (http://docs.python.org/devguide) contains information about how to go about this task. -- nosy: +r.david.murray stage: patch review - committed/rejected status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16673 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16673] Corrections in the library OS (PEP8)
Raninho Fernandes added the comment: I will follow the suggestion of Murray. Thanks Ezio and Murray. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16673 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16049] Create abstract base classes by inheritance rather than a direct invocation of __metaclass__
Andrew Svetlov added the comment: LGTM -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16049 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16667] timezone docs need versionadded: 3.2
Changes by Berker Peksag berker.pek...@gmail.com: -- keywords: +patch Added file: http://bugs.python.org/file28301/issue16667.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16667 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16667] timezone docs need versionadded: 3.2
Changes by Berker Peksag berker.pek...@gmail.com: -- nosy: +berker.peksag ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16667 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16667] timezone docs need versionadded: 3.2
Andrew Svetlov added the comment: I've reworded patch a bit and made it based on 3.2 for easier merging. -- nosy: +asvetlov Added file: http://bugs.python.org/file28302/issue16667_v2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16667 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4955] xml.sax.expatreader.ExpatParser incorrectly silently skips external character entities in attribute values
Changes by Maximiliano Curia m...@debian.org: -- nosy: +m...@debian.org ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4955 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4955] xml.sax.expatreader.ExpatParser incorrectly silently skips external character entities in attribute values
Maximiliano Curia added the comment:
Hi,
There are two issues commented in this bug, both are part of libexpat.
The one related the code inconsistency is due the design of Xml_Parser.
Reading Modules/expat/xmlparse.c:5036
else if (!entity) {
/* Cannot report skipped entity here - see comments on
skippedEntityHandler.
if (skippedEntityHandler)
skippedEntityHandler(handlerArg, name, 0);
*/
/* Cannot call the default handler because this would be
out of sync with the call to the startElementHandler.
if ((pool == tempPool) defaultHandler)
reportDefault(parser, enc, ptr, next);
*/
break;
}
That's so because libexpat startElementHandler should be called before the
skippedEntityHandler, but this piece of code is processed before the call to
startElementHandler.
To fix this, it would require a change in the libexpat API, adding the concept
of futures to the attributes processing, and a way to obtain them with an
iterator.
In any case, I don't think this is a python issue, but a known libexpat
limitation. It might be forwarded to libexpat developers, but from the python
point of view, it should be closed.
The second issue, is not really an issue. It's the default behaviour if an
entity reference is found but there is no dtd specified (the entities
declaration is a xml extension). This part is working as intended.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4955
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16661] test_posix.test_getgrouplist fails on some systems - incorrectly comparing getgroups and getgrouplist results
Roundup Robot added the comment: New changeset ce85fe971e0a by Ross Lagerwall in branch '3.3': Issue #16661: Fix the os.getgrouplist() test by not assuming that it http://hg.python.org/cpython/rev/ce85fe971e0a New changeset 05a37954a30c by Ross Lagerwall in branch 'default': Merge with 3.3 for #16661 http://hg.python.org/cpython/rev/05a37954a30c -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16661 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16667] timezone docs need versionadded: 3.2
Nurhusien Hasen added the comment: On 12/14/12, Berker Peksag rep...@bugs.python.org wrote: Changes by Berker Peksag berker.pek...@gmail.com: -- keywords: +patch Added file: http://bugs.python.org/file28301/issue16667.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16667 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/nurhusien.hasen27%40gmail.com -- find signatures serves -- nosy: +Nurhusien2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16667 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16661] test_posix.test_getgrouplist fails on some systems - incorrectly comparing getgroups and getgrouplist results
Ross Lagerwall added the comment: Is that fixed now? I simplified the test to check for a non-empty list being returned. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16661 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16049] Create abstract base classes by inheritance rather than a direct invocation of __metaclass__
Éric Araujo added the comment: Feel free to commit the patch Andrew. You may want to document the new ABC class before the ABCMeta, as we expect that subclassing will become the preferred way. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16049 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16667] timezone docs need versionadded: 3.2
Changes by Éric Araujo mer...@netwok.org: -- Removed message: http://bugs.python.org/msg177410 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16667 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16667] timezone docs need versionadded: 3.2
Changes by Andrew Svetlov andrew.svet...@gmail.com: -- stage: needs patch - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16667 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16667] timezone docs need versionadded: 3.2
Éric Araujo added the comment: Second patch has a stray slash character, and the versionadded directive does not seem to be in the same place as the first patch. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16667 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16670] Point class may be not be a good example for namedtuple
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo title: [docs] class Point in collections.namedtuples may be not that good example - Point class may be not be a good example for namedtuple versions: +Python 3.4 -Python 2.6, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16670 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16607] Bad examples in documentation
myreallycoolname added the comment: Ok, but perhaps in order to aviod confusion the documentation could be changed so that the examples are complete or have an additional new line as needed. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16607 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16670] Point class may be not be a good example for namedtuple
Andrew Svetlov added the comment: +1 for leaving the doc as is -- nosy: +asvetlov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16670 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16665] doc for builtin hex() is poor
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16665 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16666] docs wrongly imply socket.getaddrinfo takes keyword arguments in 2.x
Changes by Andrew Svetlov andrew.svet...@gmail.com: -- nosy: +asvetlov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16656] os.walk ignores international dirs on Windows
Éric Araujo added the comment: Anatoly b'Русское имя' is not a valid syntax construct in Python 3 even though I have correct 'coding: utf-8' header and expect characters to be utf-8 bytes. David The byte string vs the coding cookie is an interesting observation, but is a separate issue and should probably be raised on python-ideas, since I'm guessing it the current behavior was a conscious design choice. Yes, it works as designed: the coding cookie is used to decode bytes to characters in unicode literals (e.g. if I have u'Éric' in my source file, not a \u escape); bytes literals are independent of the coding cookie and should always contain only bytes, not characters (including \u escapes), e.g. '\xc3\x89ric' for UTF-8 bytes. -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16656 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16607] Bad examples in documentation
John Hampton added the comment: Ok, but perhaps in order to aviod confusion the documentation could be changed so that the examples are complete or have an additional new line as needed. Well, they are complete. And it's only an issue with the interpreter. If you were to copy and paste the examples into a file, say example.py, and run that with python via: python example.py then they would work as they are supposed to. If you backup in the tutorial to: http://docs.python.org/3/tutorial/interpreter.html#interactive-mode You will read an explanation of the interpreter prompts. It may be that there is a way to make it clearer, but to update those examples would require similar adjustments all over the docs. It would also only benefit the case where one were trying to run the code in the interpreter, and would make it more annoying to copy and paste into a file. So, I don't think changing anything is worth it. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16607 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16669] Docstrings for namedtuple
Eric Snow added the comment:
What is wrong with the following?
class Point(namedtuple('Point', 'x y')):
A 2-dimensional coordinate
x - the abscissa
y - the ordinate
This seems more clear to me. namedtuple is in some ways a quick-and-dirty
type, essentially a more true implementation of the intended purpose of tuple.
The temptation is to keep adding on functionality but we should resist until
there is too much imperative. I don't see it here. While I don't have a gauge
of how often people use (or would use) docstrings with nametuple, I expect that
it's relatively low given the intended simplicity of namedtuple.
--
nosy: +eric.snow
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16669
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16651] Find out what stdlib modules lack a pure Python implementation
Éric Araujo added the comment: Should itertools be in the list, as its stated purpose is to provide highly efficient functions? -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16651 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16049] Create abstract base classes by inheritance rather than a direct invocation of __metaclass__
Roundup Robot added the comment: New changeset 9347869d1066 by Andrew Svetlov in branch 'default': Issue #16049: add abc.ABC helper class. http://hg.python.org/cpython/rev/9347869d1066 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16049 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16664] [PATCH] Test Glob: files starting with .
Éric Araujo added the comment: Hm, unix shells have different rules about matching a leading dot or not. Are the docs clear about Python's glob's rules? -- nosy: +eric.araujo versions: -Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16664 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16666] docs wrongly imply socket.getaddrinfo takes keyword arguments in 2.x
Éric Araujo added the comment: There are two or three issues on this tracker where we discuss the parameters notation conventions. I think I remember a proposal to add text explaining that the keyword notation does not imply that the function accepts keyword argument, only that there is a default value. Chris, does that ring a bell? -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16049] Create abstract base classes by inheritance rather than a direct invocation of __metaclass__
Andrew Svetlov added the comment: Done. I prefer to leave existing class order in documentation. In general I agree with Eric that ABC should be before ABCMeta in the doc but now it has formalized as helper for metaclass with very short documentation. To put ABC first we need to transplate almost all content of ABCMeta doc int ABC. If somebody want to do it — please create new issue and feel free to make a patch. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16049 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16049] Create abstract base classes by inheritance rather than a direct invocation of __metaclass__
Andrew Svetlov added the comment: Thanks, Bruno. -- resolution: - fixed stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16049 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14266] pyunit script as shorthand for python -m unittest
Éric Araujo added the comment: Yes, let’s keep the pydoc/pyvenv/etc convention for pyunit. The audience is developers, whom we expect to be able to set up their environment correctly, and the -m fallback still works. -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14266 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16666] docs wrongly imply socket.getaddrinfo takes keyword arguments in 2.x
Chris Jerdonek added the comment: Is issue 13386 one of the issues you had in mind, Éric? I don't know the current best practices for all of the signature edge cases, but Ezio might. Personally, I think explicitly stating in the text that the parameters are positional-only can't hurt, especially since that's the rarer case, no? -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16664] [PATCH] Test Glob: files starting with .
Sebastian Kreft added the comment: The docs don't say anything about it. However the code is there (docs bug probably). See the following lines in glob.py: 57 if pattern[0] != '.': 58 names = [x for x in names if x[0] != '.'] 59 return fnmatch.filter(names, pattern) The documentation is even harder to follow. The glob docs say: The pattern may contain simple shell-style wildcards a la fnmatch. but the fnmatch docs say: Similarly, filenames starting with a period are not special for this module, and are matched by the * and ? patterns. The posix standard states that if a filename begins with a period ( '.' ), the period shall be explicitly matched (http://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_13_03). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16664 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16665] doc for builtin hex() is poor
rurpy added the comment: An ammendment to my proposed doc change. Replace the text (which is unchanged from the current doc), ...the result is a valid Python expression with, ...the result is a valid Python hexinteger literal (see link:[Python Lang Ref, sec 2.4.4. Integer literals]) Python epression in the current doc is way more non-specific than it need be. The result is not any old python expression, it is a very specific type of python expression so the doc should say that. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16665 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16666] docs wrongly imply socket.getaddrinfo takes keyword arguments in 2.x
Ezio Melotti added the comment: Personally, I think explicitly stating in the text that the parameters are positional-only can't hurt, especially since that's the rarer case, no? OTOH it's an implementation detail that might be changed at some point. The other option is to use [] in the signature and document the default values in the text, and possibly fix it for 3.4 (or does it work there already?). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16651] Find out what stdlib modules lack a pure Python implementation
Brett Cannon added the comment: Eric, I know you didn't just mean to suggest Python != efficient. =) Yes, it should be in the list because other VMs might not want to re-implement that code in some native language to the VM. And I assume all code in the stdlib tries to be efficient, so that label holds no sway with me. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16651 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16659] Pure Python implementation of random
Changes by Serhiy Storchaka storch...@gmail.com: Removed file: http://bugs.python.org/file28296/random_pure_python_4.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16659 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16659] Pure Python implementation of random
Serhiy Storchaka added the comment: Patch updated. One bug fixed. Also I made some benchmarks. The pure Python random() about 100 times slower and getrandbits(32) about 13 times slower than the C implementation. -- Added file: http://bugs.python.org/file28303/random_pure_python_5.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16659 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16666] docs wrongly imply socket.getaddrinfo takes keyword arguments in 2.x
Chris Jerdonek added the comment: This issue only applies to 2.7. Keyword arguments are accepted in 3.x. See the interactive example here, for example: http://docs.python.org/3.2/library/socket.html#socket.getaddrinfo -- versions: -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16669] Docstrings for namedtuple
Serhiy Storchaka added the comment: Yes, we can use inheritance trick/idiom to specify a class docstring. But there are no way to specify attribute docstrings. I encountered this when rewriting some C implemented code to Python. PyStructSequence allows you to specify docstrings for a class and attributes, but namedtuple does not. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16669 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16666] docs wrongly imply socket.getaddrinfo takes keyword arguments in 2.x
Ezio Melotti added the comment: In that case I think it's OK to use the [] and mention the default values in the text. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16674] Faster getrandbits() for small integers
New submission from Serhiy Storchaka: The proposed patch adds a fast patch for generating small integers (the most common use case). Microbenchmark: $ ./python -m timeit -s import random; r=random.getrandbits; n=30 r(n);r(n);r(n);r(n);r(n);r(n);r(n);r(n);r(n);r(n) Non patched: 4.27 usec per loop Patched: 2.97 usec per loop -- components: Extension Modules files: random_getrandbits_fastpath.patch keywords: patch messages: 177436 nosy: mark.dickinson, rhettinger, serhiy.storchaka priority: normal severity: normal stage: patch review status: open title: Faster getrandbits() for small integers type: performance versions: Python 3.4 Added file: http://bugs.python.org/file28304/random_getrandbits_fastpath.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16674 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16674] Faster getrandbits() for small integers
Changes by Jesús Cea Avión j...@jcea.es: -- nosy: +jcea ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16674 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16675] Ship Python with a package manager
New submission from Matt Hickford: Python should ship with a full-featured package manager. Why? 1. Most programmers would rather use a reliable maintained library for a common task than roll their own code. Then the programmer can get on with solving their unique problems. This assumes the library is convenient to install (and licensed appropriately). 2. Other languages ship with package managers - Ruby with Gem, Nodejs with Npm. As a result, these languages have extremely successful open-source communities encouraging sharing. https://github.com/languages Yes, Python has a strong open-source community, but there's a real hurdle to publishing packages. Nodejs is still in short trousers, but https://npmjs.org/ will shortly outnumber Python's package index. If you believe sharing is worthwhile, then you should want to make it easy. Python has a decent package manager (distribute + pip) but it's ironically complicated to install. On Windows 64 bit (a very popular platform), this requires installing a package from source. You, dear Reader, surely find that easy, but it's still a big an ask for anyone new to programming. You perhaps recommend Python to friends wishing to learn programming. Could you explain over the phone how to install a package such as 'requests'? The Django homepage actually forsakes Python package management and encourages new users to build from source. You only have to write 'python install package' into Google or read http://stackoverflow.com/questions/4750806/how-to-install-pip-on-windows to see just how much *pain* new users have with package management. I humbly suggest pip (+ distribute), which happens to be the community's de facto standard. -- messages: 177437 nosy: Matt.Hickford priority: normal severity: normal status: open title: Ship Python with a package manager type: behavior versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16675 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16656] os.walk ignores international dirs on Windows
anatoly techtonik added the comment: There is one more problem - when I redirect the output with: py test_unicode_fname.py test.log 21 In Python 2.7 the traceback is at the end of file, in Python 3.3 it is at the beginning. Therefore I just copied data from the screen, where it appears in correct order. (current mood: Python debugging is a mess) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16656 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16656] os.walk ignores international dirs on Windows
Changes by anatoly techtonik techto...@gmail.com: Added file: http://bugs.python.org/file28305/py27fname.log ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16656 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16656] os.walk ignores international dirs on Windows
Changes by anatoly techtonik techto...@gmail.com: Added file: http://bugs.python.org/file28306/py33fname.log ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16656 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16656] os.walk ignores international dirs on Windows
Amaury Forgeot d'Arc added the comment: Anatoly, please file another issue for the 21 mess. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16656 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16675] Ship Python with a package manager
Eric V. Smith added the comment: Because this is a new feature, it could only be added to Python 3.4. Changing versions. -- components: +Installation nosy: +eric.smith type: behavior - enhancement versions: -Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16675 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16357] SSLSocket created from SSLContext.wrap_socket doesn't include cert/keyfile
Changes by Jesús Cea Avión j...@jcea.es: -- nosy: +jcea ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16357 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16651] Find out what stdlib modules lack a pure Python implementation
Changes by Zachary Ware zachary.w...@gmail.com: -- nosy: +zach.ware ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16651 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16676] Segfault under Python 3.3 after PyType_GenericNew
New submission from Tres Seaver:
A test of the 'persistent' package C extension segfaults under 3.3,
but completes successfully under 3.2. The C function being tested
is a wrapper around PyType_GenericNew:
static PyObject *
simple_new(PyObject *self, PyObject *type_object)
{
if (!PyType_Check(type_object))
{
PyErr_SetString(PyExc_TypeError,
simple_new argument must be a type object.);
return NULL;
}
return PyType_GenericNew((PyTypeObject *)type_object, NULL, NULL);
}
The unit test which segfaults just iterates over basic types:
def test_w_type(self):
for typ in (type, list, dict, tuple, object):
self.assertTrue(isinstance(self._callFUT(typ), typ))
Some digging shows that the segfault comes while deallocating the
newly-made 'dict' object.
#0 dict_dealloc (mp=0x73f9d248) at Objects/dictobject.c:1392
#1 0x004261cb in tupledealloc (op=0x73d90ab8)
at Objects/tupleobject.c:238
#2 0x0048065d in call_function (oparg=optimized out,
pp_stack=0x7fffa6e0) at Python/ceval.c:4064
#3 PyEval_EvalFrameEx (f=optimized out, throwflag=optimized out)
at Python/ceval.c:2679
#4 0x00480b23 in fast_function (nk=optimized out, na=1,
n=optimized out, pp_stack=0x7fffa850, func=0x742284d0)
at Python/ceval.c:4150
#5 call_function (oparg=optimized out, pp_stack=0x7fffa850)
at Python/ceval.c:4083
--
components: Extension Modules, Interpreter Core
messages: 177441
nosy: tseaver
priority: normal
severity: normal
status: open
title: Segfault under Python 3.3 after PyType_GenericNew
versions: Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16676
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16478] Fix division in tabnanny
Changes by Jesús Cea Avión j...@jcea.es: -- nosy: +jcea ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16478 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16675] Ship Python with a package manager
R. David Murray added the comment: Matt, thanks for your interest. This possibility has been discussed, so you aren't the only one who thinks it should happen. However, I don't think this is an appropriate issue for the tracker. This is part of an ongoing discussion and process on distutils-sig and python-dev. It is also a PEP level feature, which pretty much means there should be an approved PEP before there is an open issue for implementing/integrating it. I would recommend you check out the past discussions and join in on the efforts to improve the current situation. If other devs disagree with me the issue can be reopened. -- nosy: +r.david.murray resolution: - later stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16675 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1818] Add named tuple reader to CSV module
Changes by Andrew Svetlov andrew.svet...@gmail.com: -- nosy: +asvetlov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1818 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15963] Improve ./configure's support for 32/64-bit debug|release|profiled builds w/ vendor (non-gcc) compilers on proprietary UNIX systems (Solaris/HP-UX/AIX et al).
Trent Nelson added the comment: I spent a little time on this yesterday. Here's what I came up with. The idea is to have a standalone block in configure.ac that kicks in when --without-gcc is specified (or if $CC != gcc) *IFF* CFLAGS/CPPFLAGS haven't been provided by the user. If they have, we warn, and skip the block. Rationale is wanting to cover two cases: a) experienced user consciously overriding our attempts at sensible defaults in that block, b) inexperienced user who has no clue what the sensible defaults are but has otherwise inadvertently set CFLAGS/CPPFLAGS (or perhaps just inherited such settings from their existing environment). So, here's what the block looks like currently, albeit just for IRIX at the moment (and this was against 2.7). I'll eventually expand it to cover Solaris/SPARC|AMD64, AIX, HP-UX (PA-RISC/IA64) and Tru64. (Also note the new `--enable-64bit` arg, which is intended to be used on these platforms as a way to coerce easy 64-bit builds. The functionality doesn't apply on x86/x64 free *nix platforms that use clang/gcc -- those will default to using whatever memory architecture is being used by the underlying system -- if you want something else, that's the job of cross-compilation, which is a different problem this particular issue is attempting to address.) +AC_MSG_CHECKING(for --enable-64bit) +AC_ARG_ENABLE( +64bit, +AS_HELP_STRING( +[--enable-64bit], +[attempt 64-bit build (use with --without-gcc)] +) +) +if test -z $enable_64bit; then +AC_MSG_RESULT(no) +else +AC_MSG_RESULT(yes) +fi +if test -n $enable_64bit test $without_gcc != yes; then +AC_MSG_WARN([ +--enable-64bit has no effect unless --without-gcc is also specified +]) +fi + +# If we're not using GCC, we're probably on a proprietary UNIX, relying +# on a proprietary compiler, running on non-x86/x64 hardware. Autoconf +# is pretty bad at picking sensible defaults for compiler flags in this +# situation, so, let's try and do as much as we can ourselves. The aim +# is to pick the optimal settings for each of the following permutations: +# +# Debug builds, 32-bit and 64-bit: +# ./configure --without-gcc --with-pydebug +# ./configure --without-gcc --with-pydebug --enable-64bit +# +# Optimized release builds, 32-bit and 64-bit: +# ./configure --without-gcc +# ./configure --without-gcc --enable-64bit +# +if test $without_gcc = yes || test $CC != gcc; then +# This whole block assumes we know more than a) the user, and b) autoconf. +# If we detect CFLAGS/CPPFLAGS, then we can't safely assume a) anymore, +# so print a message instead of doing any customisation. +if test -n $CFLAGS || test -n $CPPFLAGS; then +AC_MSG_WARN([ +You have defined CFLAGS and/or CPPFLAGS in conjunction with +--with-gcc; skipping attempt at setting flags to sensible +defaults -- make sure you know what you are doing. +]) +else +case $MACHDEP in +irix6) +# Trying to separate IRIX from C99 and still end up with a +# working executable is an exercise in futility; it has a +# much greater link between `cc -c99` and available system +# facilities/headers than other OSes (which primarily rely +# on the usual XPG4/XOPEN_SOURCE etc defines). Using the +# c99 compiler is the lesser of two evils. +CC=c99 +CXX=CC +# `-diag_error 1035` makes the compiler treat #error defines +# as actual errors (and abort compilation), and not warnings. +CFLAGS=-diag_error 1035 +# Try to target the underlying host hardware. +_platform=`hinv -c processor | + head -n 1 | + cut -f 4 -d ' '` +_processor=`hinv -c processor | +head -n 2 | +tail -n 1 | +cut -f 3 -d ' '` +CFLAGS=$CFLAGS -TARG:platform=$_platform +CFLAGS=$CFLAGS -TARG:processor=$_processor + +if test $with_pydebug = yes; then +OPT=-O -g2 +else +OPT=-g3 -Ofast=$_platform -OPT:Olimit=5500 +fi + +if test -n $enable_64bit; then +CFLAGS=-64 $CFLAGS +LDFLAGS=-64 +else +CFLAGS=-n32 $CFLAGS +LDFLAGS=-n32 +fi +;; +*) ;; +esac fi fi -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15963 ___ ___ Python-bugs-list mailing list Unsubscribe:
[issue16677] Hard to find operator precedence in Lang Ref.
New submission from rurpy: Python Language Reference, chapter 6 Expressions. The last section (6.15) of this is titled, Summary. That title is misleading -- it is not really a summary of the Expressions chapter but rather, as the first sentence makes clear, a table of operator precedences. It is not really even a summary of operator precedences since some of the preceeding operator sections don't mention their precedence. And adding to the confusion, none of preceding sections even use the word precedence, referring instead to binding or priority. Operator precedences are something many users frequently look for frequently in a language reference and the lack of an Operator Precedence entry in the ToC makes this section hard to find. There are no index entries for operators/precedence or expressions/order of evaluation. There is an index entry for evaluation order but that points to a different section. At a minimum, this section should have its title changed from Summary to Operator Precedence and get one or more index entries. In other languages operator precedence is often described and indexed under order of evaluation, often as a subindex of expressions. In the Python reference, there is a very short section called, 6.14, Evaluation Order that immediately preceeds the Operator Precedence section. That section and the Operator Precedence section could be effectively combined into a single section. -- assignee: docs@python components: Documentation messages: 177444 nosy: docs@python, rurpy2 priority: normal severity: normal status: open title: Hard to find operator precedence in Lang Ref. type: enhancement versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16677 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15963] Improve ./configure's support for 32/64-bit debug|release|profiled builds w/ vendor (non-gcc) compilers on proprietary UNIX systems (Solaris/HP-UX/AIX et al).
Ned Deily added the comment: Without having reviewed the proposed change in detail, a couple of comments. On current OS X systems and others, the compiler could be clang which perhaps should be treated as gcc for most autoconf purposes. Also, why are we putting any effort into supporting IRIX anymore? Both IRIX and the MIPS processor lines it runs on was retired by SGI in 2007. That's why support for IRIX was pulled from Python 3. It's a dead end. -- nosy: +ned.deily ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15963 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16612] Integrate Argument Clinic specialized preprocessor into CPython trunk
Larry Hastings added the comment: I don't think we can solve the problem of the output being too long for your liking. Personally I like the output; I find it eminently readable, and making it shorter would impair that. I think in the majority of uses Clinic will be a win for readability. I do have one suggestion that might mitigate the problem for you. What if you put all the argument processing in a separate file (with .c or .h extension) and #include that in _decimal.c? You don't *have* to have the body for the impl function immediately after the DSL block; you could just have a semicolon there after the block and the C compiler would interpret it as a (redundant) declaration. You'd have to maintain declaring the impl yourself in _decimal.c, but I'm guessing you'd rather do that than have all the Clinic stuff blowing up _decimal.c. Finally, since you have not addressed it directly, let me ask you: are you interested in Clinic having a more boilerplate-friendly macro processing mode, with templates or recycling old entries or something? Or do you not care? If it doesn't help you then I may as well not bother. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16612 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
