[issue16662] load_tests not invoked in package/__init__.py
Michael Foord added the comment: I'm happy with the check being removed. The old behaviour was documented I believe - so there'd need to be documentation changes to go with it. As the old behaviour is so un-useful I don't think there are backward compatibility issues with changing it. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16662 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17998] internal error in regular expression engine
Changes by Cédric Krier cedric.kr...@b2ck.com: -- nosy: +ced ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17998 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16245] Update html.entities.html5 dictionary and parseentities.py
Larry Hastings added the comment: I'm downgrading this to deferred blocker. We'll make sure it happens before Python 3.4.0, but there's no need to hold up Python 3.4a1 for this. -- priority: release blocker - deferred blocker ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16245 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18257] Two copies of python-config
Larry Hastings added the comment: Okay, downgrading to deferred blocker. -- priority: release blocker - deferred blocker ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18257 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5302] Allow package_data specs/globs to match directories
Larry Hastings added the comment: And this will hold up Python 3.4a1, as I can't close #13463 until this is closed first. So I'm closing this as wontfix. -- nosy: +larry resolution: - wont fix status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5302 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13463] Fix parsing of package_data
Larry Hastings added the comment: This was held up by #5302, so I just closed that one too as the same rule applies. -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13463 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17998] internal error in regular expression engine
Larry Hastings added the comment: Can I downgrade this to deferred blocker? That means we still need to deal with it before the release, but we don't have to hold up Python 3.4a1 for it. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17998 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18181] PEP447: Add type.__locallookup__
Ronald Oussoren added the comment: Updated the patch for PEP 442. -- Added file: http://bugs.python.org/file31107/issue-18181-full-v4.txt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18181 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5262] PythonLauncher considered harmfull
Ronald Oussoren added the comment: The attached patch removes the code that checks if Python Launcher is the default application for opening python files. -- Added file: http://bugs.python.org/file31108/issue-5262.txt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5262 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18214] Stop purging modules which are garbage collected before shutdown
Antoine Pitrou added the comment:
It appears that a few (1-3) module dicts are not being purged because they
have been orphaned. (i.e. the module object was garbaged collected before
we check the weakref, but the module dict survived.)
Module globals can be kept alive by any function defined in that module. So if
that function is registered eternally in a C static variable, the globals dict
will never get collected.
./python -v -Xshowrefcount check_purging.py
I always get either:
# remaining {'encodings', '__main__'}
[...]
[24834 refs, 7249 blocks]
or
# remaining {'__main__', 'encodings'}
[...]
[24834 refs, 7249 blocks]
... which seems to hint that it is quite stable actually.
The encodings globals are kept alive because of the codecs registration, I
believe.
As for the __main__ dict, perhaps we're missing a decref somewhere.
Maybe 8 out of 50+ module dicts actually die a natural death by being
garbage collected before they are purged.
I get different numbers from you. If I run ./python -v -c pass, most modules
in the wiping phase are C extension modules, which is expected. Pretty much
every pure Python module ends up garbage collected before that.
By the way, please also try issue18608 which will bring an other improvement.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18214
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18611] Mac: Some Python Launcher issues
New submission from Ronald Oussoren: There are some issues with the Python Launcher application: 1) There is a useless 'Help' menu, the application does not include help (removal is trivial and doesn't affect functionality) 2) The list of interpreters does not include the framework locations, only /usr/local, /usr and /sw (Fink). IMHO the factory default should only include the framework and system pythons. 3) Python Launcher should probably sniff the script for a '#!', if only to detect if the script is python 2 or 3. This may need to be an option, an the algoritm needs to be specified. Probably something like: - No #!: use app setting - #!/usr/bin/env ...: use '...' to determine python version, use app setting to find that. Rationale: /usr/bin/env uses $PATH to find a binary, the value of $PATH for GUI apps cannot easily be changed by users (if at all, there used to be an environment.plist file but I haven't checked if thats still used by the system). Therefore it is better to use an application setting for this. - #!/path/to/python: use that interpreter if it exists (not sure yet what should happen if that interpreter does not exist) This has several advantages over the current behavior: - Can use a single Python Launcher for python2 and python3 scripts - Works with virtualenv/pyvenv environments (assuming that the right path is used in the #! line) See also the pep397 specification for the py launcher on windows, but I don't propose to add such a command-line tool to Mac installations, the normal Unix conventions work just fine for command-line use. See als #5262 -- assignee: ronaldoussoren components: Macintosh messages: 194041 nosy: ned.deily, ronaldoussoren priority: normal severity: normal stage: needs patch status: open title: Mac: Some Python Launcher issues type: behavior versions: Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18611 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18608] Avoid keeping a strong reference to locale in the _io module
Changes by Christian Heimes li...@cheimes.de: -- nosy: +christian.heimes ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18608 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18214] Stop purging modules which are garbage collected before shutdown
Changes by Christian Heimes li...@cheimes.de: -- nosy: +christian.heimes ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18214 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18214] Stop purging modules which are garbage collected before shutdown
Antoine Pitrou added the comment: As for the __main__ dict, perhaps we're missing a decref somewhere. Actually, it's not surprising. Blob's methods hold a reference to the __main__ globals, and there's still a Blob object alive in encodings. If you replace the end of your script with the following: for name, mod in sys.modules.items(): if name != 'encodings': mod.__dict__[__blob__] = Blob(name) del name, mod, Blob then at the end of the shutdown phase, remaining is empty. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18214 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18214] Stop purging modules which are garbage collected before shutdown
Richard Oudkerk added the comment:
On 01/08/2013 10:59am, Antoine Pitrou wrote:
If you replace the end of your script with the following:
for name, mod in sys.modules.items():
if name != 'encodings':
mod.__dict__[__blob__] = Blob(name)
del name, mod, Blob
then at the end of the shutdown phase, remaining is empty.
On Windows, even with this change, I get for example:
# remaining {'encodings.mbcs', '__main__', 'encodings.cp1252'}
...
[22081 refs, 6742 blocks]
or
# remaining {'__main__', 'encodings'}
...
[23538 refs, 7136 blocks]
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18214
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18214] Stop purging modules which are garbage collected before shutdown
Antoine Pitrou added the comment: You might want to open a prompt and look at gc.get_referrers() for encodings.mbcs.__dict__ (or another of those modules). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18214 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18214] Stop purging modules which are garbage collected before shutdown
Richard Oudkerk added the comment: You might want to open a prompt and look at gc.get_referrers() for encodings.mbcs.__dict__ (or another of those modules). gc.get_referrers(sys.modules['encodings.mbcs'].__dict__) [module 'encodings.mbcs' from 'C:\\Repos\\cpython-dirty\\lib\\encodings\\mbcs.py', function decode at 0x01DEEF38, function getregentry at 0x01DFA038, function IncrementalEncoder.encode at 0x01DFA098] gc.get_referrers(sys.modules['encodings.cp1252'].__dict__) [module 'encodings.cp1252' from 'C:\\Repos\\cpython-dirty\\lib\\encodings\\cp1252.py', function getregentry at 0x02802578, function Codec.encode at 0x02802518, function Codec.decode at 0x028025D8, function IncrementalEncoder.encode at 0x02802638, function IncrementalDecoder.decode at 0x02802698] gc.get_referrers(sys.modules['__main__'].__dict__) [function Blob.__init__ at 0x0057ABD8, function Blob.__del__ at 0x02AD36F8, frame object at 0x027DFA80, function listcomp at 0x02AD3DB8, frame object at 0x02A38038, module '__main__' (_frozen_importlib.SourceFileLoader object at 0x0271EAB8)] -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18214 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18306] os.stat gives exception for Windows junctions in v3.3
Tim Golden added the comment: I propose to close this one: using Python 3.3 on Win7 I can successfully stat NTFS Junctions. Is there any remaining issue? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18306 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18214] Stop purging modules which are garbage collected before shutdown
Richard Oudkerk added the comment: I get different numbers from you. If I run ./python -v -c pass, most modules in the wiping phase are C extension modules, which is expected. Pretty much every pure Python module ends up garbage collected before that. The *module* gets gc'ed, sure. But you can't tell from ./python -v -c pass when the *module dict* get gc'ed. Using ./python -v check_purging.py, before the purging stage (# cleanup [3]) I only get # purge/gc operator 54 # purge/gc io 53 # purge/gc keyword 52 # purge/gc types 51 # purge/gc sysconfig 50 That leaves lots of pure python module dicts to be purged later on. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18214 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18612] More elaborate documentation on how list comprehensions and generator expressions relate to each other
New submission from uglemat: Today there are list comprehensions, set comprehensions, dict comprehensions and then... there are generator expressions, which apparently was called 'generator comprehensions' in the original PEP, don't know why that was changed. Some questions arises: * Are generator expressions a type of list comprehension, or are generator expressions to be considered their own thing. * Does 'list comprehension' mean a type of comprehension that happens to return a list, or is it to be considered more of a general concept. I usually talk about 'list comprehension' as a type of comprehension, and 'generator expression' as another type of comprehension, and after investigating whether or not that is correct I couldn't find an answer. On the wikipedia article on list comprension (http://en.wikipedia.org/wiki/List_comprehension#Python) they list generator expressions as well, indicating that it's a type of list comprehension. I think there's a lot of confusion to be had here, and that the documentation should clarify what exactly is meant by 'list comprehensions', regardless of what happens to be the case. I haven't really a bug report before, so forgive me if I'm doing something wrong. :) -- assignee: docs@python components: Documentation messages: 194048 nosy: docs@python, uglemat priority: normal severity: normal status: open title: More elaborate documentation on how list comprehensions and generator expressions relate to each other versions: Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18612 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9035] os.path.ismount on windows doesn't support windows mount points
Roundup Robot added the comment: New changeset f283589cb71e by Tim Golden in branch 'default': Issue #9035: os.path.ismount now recognises volumes mounted below http://hg.python.org/cpython/rev/f283589cb71e -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9035 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18613] wrong float minus op result
New submission from Laurent Fournier: Python 3.3.1 (with GCC 4.7.3) on Linux print (.3-.1) 0.18 -- messages: 194050 nosy: Laurent.Fournier priority: normal severity: normal status: open title: wrong float minus op result type: behavior versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18613 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18517] xxlimited extension declared incorrectly in setup.py
Martin v. Löwis added the comment: I would be fine with it being build only in a debug build. The rationale for the module is that it should test whether the header files actually compile under the limited API (or whether e.g. some functions are exposed that rely on unexposed structures). So the main test is really whether it compiles. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18521] [cppcheck] Full report
Martin v. Löwis added the comment: Julien: I propose to resolve this issue in the same way as we have done previously with analysis tools (with some unfortunate exceptions). Somebody motivated enough (hopefully you) agrees to initially study the tool output, and ideally also then agrees to run the tool on a regular basis (but this is really not mandatory - the help with the initial run is already appreciated). You would then filter out the reports, and see which of them are useful. If you can, have the tool silence the bogus reports (e.g. with a configuration file). For the issues that you consider valid, please file individual bug reports (possibly combining related reports, e.g. by module or by error kind, but only if they can all be reasonably fixed in a single commit). The key concern of the developers here is probably this: a) there is no doubt that getting issues detected and fixed would be a helpful contribution, but b) the amount of false positives makes it unattractive to actually run the tool yourself. If you do not want to volunteer, this is fine as well. Just don't feel sad if the issue gets closed with no action. -- nosy: +loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18521 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18613] wrong float plus/minus op result
Laurent Fournier added the comment: also with addition ! print (.05+.01) 0.065 -- title: wrong float minus op result - wrong float plus/minus op result ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18613 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18472] Update PEP 8 to encourage modern conventions
Nick Coghlan added the comment: Changes in version 5: - added a new reference pointing back to this tracker issue. I figure that's a good precedent to set for future updates. - I liked Barry's point about Don't break backwards compatility enough that I moved it into its own paragraph ahead of the bulleted list and changed the heading to Some other good... - changed a few more cases of rule to guideline - tabs vs spaces section now strongly prefers spaces, saying tabs should be used only for legacy compatibility reasons - changed the line length recommendation to allow up to 99 characters when it improves readability (I kept 79 as the default recommendation, and 72 for reflowing long blocks of text) - rewrapped my additions to the PEP at 72 chars ;) - encodings section no longer mentions Latin-1, referring only to UTF-8, ASCII and non-ASCII. - class based exception note changed to a recommendation to inherit from Exception (this ended up leading quite well into the comment about inheritance heirarchy design) - we already had an admonition to avoid bare except clauses (as well as except BaseException:) - dropped the highly from the annotation decorator recommendation - added a note that the public/internal API guideline still applies when using a wildcard import to republish APIs, as well as noting you should only use them when you don't know the list of republished names in advance I *didn't* make any changes in relation to Barry's comment about having the commentary intermixed with the guidelines. I quite like the notion of stripping PEP 8 down to just the essentials and having PEP 108 as The annotated PEP 8, but that's a bigger project than I'm prepared to tackle (heck, even the *current* patch turned out to be a far more substantial update than I expected!). I'll commit this version - feel free to tweak further in the PEP repo if you spot any mistakes :) I deliberately left the following point out since Guido said out of scope above (I wrote it before noticing that): - Use an iterator or a loop-and-a-half construct rather than repeating loop setup code in the body of the loop. Yes:: def itervalues(x): yield x.getvalue() for value in itervalues(obj): process(value) Yes:: while True: value = obj.getvalue() if not value: break process(value) No:: value = obj.getvalue() while value: process(value) value = obj.getvalue() -- Added file: http://bugs.python.org/file31109/issue18472_pep_8_update5.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18472 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18214] Stop purging modules which are garbage collected before shutdown
Antoine Pitrou added the comment: Here (Linux) I get the following: # purge/gc os.path 12 # purge/gc operator 50 # purge/gc io 49 # purge/gc _sysconfigdata 48 # purge/gc sysconfig 47 # purge/gc keyword 46 # purge/gc site 45 # purge/gc types 44 Also, do note that purge/gc after wiping can still be a regular gc pass unless the module has been wiped. The gc could be triggered by another module being wiped. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18214 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18472] Update PEP 8 to encourage modern conventions
Nick Coghlan added the comment: For the record, the thread where Thomas Wouters provided the feedback that led to the current wording regarding imports: http://mail.python.org/pipermail/python-dev/2013-July/127373.html -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18472 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18612] More elaborate documentation on how list comprehensions and generator expressions relate to each other
R. David Murray added the comment: Well, you haven't done anything wrong, but I'm not sure what we can do in response to the report. What how will the answer to the question serve you? What will you know after getting the answer that you didn't know before getting the answer? I'm trying here to understand what it is that is missing from your mental model of Python that needs to be filled in, because the syntax and behavior of these constructs is documented, and it has never occurred to me to wonder whether or not a generator expression is a comprehension or not. I'm making things up here, but I suspect we call generator expressions that because while they share the base syntax and much of the same semantics as the things we call comprehensions, (a) they produce an iterable (a generator object) instead instead of a fully realized object and (b) you can specify a generator expression without explicit surrounding punctuation (eg: myfunc(x for x in range(7))). That is, the 'comprehensions' are conceptually a notation for specifying a collection object using a compact notation, while a generator expression is a way of creating a generator-iterable *function* that must then be iterated to produce the collection object implicitly specified by the expression. I'm not sure I'm being clear, because the distinction is subtle and perhaps not meaningful...the difference in naming might just be an historical accident :) And, because it is not entirely clear, I'm not sure it is a good idea to try to document it. Again, what enlightenment would derive from a clear explanation? -- nosy: +r.david.murray versions: +Python 2.7, Python 3.3, Python 3.4 -Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18612 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12645] test.support. import_fresh_module - incorrect doc
Eli Bendersky added the comment: Ben, would you like to provide an updated patch? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12645 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3591] elementtree tests do not include bytes handling
Eli Bendersky added the comment: Quite a bit of encoding-related tests were added recently (by Serhiy, IIRC). Unless there are objections or more specific test suggestions, I will close this issue in a few days. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3591 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13612] xml.etree.ElementTree says unknown encoding of a regular encoding
Eli Bendersky added the comment: Serhiy, do you want to backport the buffer overflow fix to 2.7? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13612 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18613] wrong float plus/minus op result
Brett Cannon added the comment:
This is actually expected because that is just how floating point works in
programming (see http://en.wikipedia.org/wiki/Floating_point for all the gnarly
details).
If you want exact decimal arithmetic, use the decimal module (which got
significantly faster in Python 3.3)::
import decimal
decimal.Decimal('.3') - decimal.Decimal('.1')
Decimal('0.2')
decimal.Decimal('.05') + decimal.Decimal('.01')
Decimal('0.06')
--
nosy: +brett.cannon
resolution: - invalid
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18613
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18472] Update PEP 8 to encourage modern conventions
Changes by Nick Coghlan ncogh...@gmail.com: -- resolution: - fixed stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18472 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17372] provide pretty printer for xml.etree.ElementTree
Eli Bendersky added the comment: Thanks for the report (Eric) and the patch (Alex). There are currently some open bugs we need to handle first, so this is somewhat lower priority. I hope to get to it before the 3.4 release. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17372 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18472] Update PEP 8 to encourage modern conventions
Nick Coghlan added the comment: Heh, I just realised a correct generator definition would have needed the loop-and-a-half internally anyway: def itervalues(x): while True: value = x.getvalue() if not value: break yield value -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18472 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18612] More elaborate documentation on how list comprehensions and generator expressions relate to each other
uglemat added the comment: Yeah I think the differences are pretty easy to comprehend. To be honest the reason I came here is that I had an argument where someone commented on my code (where I used a generator expression) saying something akin to list comprehensions are nice, so I replied actually, that's a generator expression, which are very similar but behave differently. The response was that the two concepts are one and the same. I couldn't really say that that's incorrect, but I think it's very confusing for beginners if people are talking about generator expressions like they are list expressions because they behave so differently and the documentation for list comprehensions doesn't mention generator expressions. I was kind of longing for a definite answer so I could say Nay, thou shall differentiate between list comprehensions and generator expressions. Is it right to correct someone and say that generator expressions are in fact *not* generator expressions? Maybe I'm blowing this out of proport ions. :) -- versions: +Python 3.5 -Python 2.7, Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18612 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18214] Stop purging modules which are garbage collected before shutdown
Richard Oudkerk added the comment: Also, do note that purge/gc after wiping can still be a regular gc pass unless the module has been wiped. The gc could be triggered by another module being wiped. For me, the modules which die naturally after purging begins are # purge/gc encodings.aliases 34 # purge/gc _io 14 # purge/gc collections.abc 13 # purge/gc sre_compile 12 # purge/gc heapq 11 # purge/gc sre_constants 10 # purge/gc _weakrefset 9 # purge/gc reprlib 8 # purge/gc weakref 7 # purge/gc site 6 # purge/gc abc 5 # purge/gc encodings.latin_1 4 # purge/gc encodings.utf_8 3 # purge/gc genericpath 2 Of these, all but the first appear to happen during the final cyclic garbage collection. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18214 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9035] os.path.ismount on windows doesn't support windows mount points
Roundup Robot added the comment: New changeset 5258c4399f2e by Tim Golden in branch 'default': issue9035: Prevent Windows-specific tests from running on non-Windows platforms http://hg.python.org/cpython/rev/5258c4399f2e -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9035 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10434] Document the rules for public names
Nick Coghlan added the comment: PEP 8 now covers the developer side of things: http://www.python.org/dev/peps/pep-0008/#public-and-internal-interfaces A user facing counterpart describing our backwards compatibility policy is still desirable. Updating PEP 5 wouldn't go astray, since that's *supposed* to serve that purpose :) -- nosy: +ncoghlan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10434 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18612] More elaborate documentation on how list comprehensions and generator expressions relate to each other
uglemat added the comment: Is it right to correct someone and say that generator expressions are in fact *not* generator expressions? Ups, I meant Is it right to correct someone and say that generator expressions are in fact *not* list comprehensions? All these expressions and comprehensions are making me dissy :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18612 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18214] Stop purging modules which are garbage collected before shutdown
Antoine Pitrou added the comment: Also, do note that purge/gc after wiping can still be a regular gc pass unless the module has been wiped. The gc could be triggered by another module being wiped. That said, I welcome any suggestions to improve things. The ultimate reasons we need to purge some modules are the same two reasons I indicated on python-dev: C extension modules are almost immortal; and some C code keeps references alive too long. Do you agree that this patch is ok and we should address those two problems in separate new issues? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18214 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18472] Update PEP 8 to encourage modern conventions
Barry A. Warsaw added the comment: On Aug 01, 2013, at 12:19 PM, Nick Coghlan wrote: I *didn't* make any changes in relation to Barry's comment about having the commentary intermixed with the guidelines. I quite like the notion of stripping PEP 8 down to just the essentials and having PEP 108 as The annotated PEP 8, but that's a bigger project than I'm prepared to tackle (heck, even the *current* patch turned out to be a far more substantial update than I expected!). You've done great work on a substantial undertaking! Thanks. :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18472 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18612] More elaborate documentation on how list comprehensions and generator expressions relate to each other
R. David Murray added the comment: Well, it is the case that if you substitute a list comprehension for a generator expression in arbitrary code, most of the time it would work but occasionally it wouldn't, because the runtime behavior is different (lazy production versus all-at-once production). So yes, the two are not the same thing, and it is important to understand the differences in behavior between them. Calling a generator expression a list comprehension indicates someone's mental model of how Python works has a couple holes in it, IMO :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18612 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14130] memoryview: add multi-dimensional indexing and slicing
DLowell added the comment: Is this issue still being worked on? -- nosy: +DLowell ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14130 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18257] Two copies of python-config
Roundup Robot added the comment: New changeset 7b165c7ab7ef by doko in branch 'default': - Issue #18257: Fix readlink usage in python-config. Install the python http://hg.python.org/cpython/rev/7b165c7ab7ef -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18257 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18257] Two copies of python-config
Matthias Klose added the comment: checked in a fix for the readlink issue, and Ronald's proposed solution for Darwin. And documented for now, that we do have two versions of this script. This works as long as you don't cross-build for Darwin or on Darwin. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18257 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18614] Enhanced \N{} escapes for Unicode strings
New submission from Steven D'Aprano:
As per the discussion here:
http://mail.python.org/pipermail/python-ideas/2013-July/022419.html
\N{} escapes should support the Unicode code point notation U+ (where there
are four, five or six hex digits after the U+).
E.g. '\N{U+03BB}' = 'λ'
unicodedata.lookup should also support such numeric names, e.g.:
unicodedata.lookup('U+03BB') = 'λ'
As '+' is otherwise prohibited in Unicode character names, there should never
be ambiguity between 'U+' as a code point and an actual name, and a single
lookup function can handle both.
(See http://www.unicode.org/versions/Unicode6.2.0/ch04.pdf#G39 for details on
characters allowed in names.)
Also add a function for the reverse
unicodedata.codepoint('λ') = 'U+03BB'
def codepoint(c):
return 'U+{:04X}'.format(ord(c))
--
components: Unicode
messages: 194075
nosy: ezio.melotti, stevenjd
priority: normal
severity: normal
status: open
title: Enhanced \N{} escapes for Unicode strings
type: enhancement
versions: Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18614
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18214] Stop purging modules which are garbage collected before shutdown
Richard Oudkerk added the comment: Yes, I agree the patch is ok. It would be would be much simpler to keep track of the module dicts if they were weakrefable. Alternatively, at shutdown a weakrefable object with a reference to the module dict could be inserted in to each module dict. We could then use those to find orphaned module dicts. But I doubt it is worth the extra effort. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18214 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9035] os.path.ismount on windows doesn't support windows mount points
Tim Golden added the comment: Fixed. Thanks for the patch -- resolution: - fixed stage: needs patch - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9035 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18472] Update PEP 8 to encourage modern conventions
Guido van Rossum added the comment: Thanks a bundle, Nick! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18472 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18214] Stop purging modules which are garbage collected before shutdown
Antoine Pitrou added the comment: Ok, let's attack the rest separately then :) And thanks a lot for testing! -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18214 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18615] sndhdr.whathdr could return a namedtuple
New submission from Claudiu.Popa: Both sndhdr.whathdr an sndhdr.what returns a tuple with various information, while it could return a namedtuple. I attached a patched for this, with tests as well. -- components: Library (Lib) files: sndhdr.patch keywords: patch messages: 194080 nosy: Claudiu.Popa priority: normal severity: normal status: open title: sndhdr.whathdr could return a namedtuple type: enhancement versions: Python 3.4 Added file: http://bugs.python.org/file31110/sndhdr.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18615 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16111] Python 2.7.3 Windows MSI installer installs the VC++ 9 dlls directly to WinSxS folder
Martin v. Löwis added the comment: This is not true. Installing the modules into the SxS folder using the Merge Module (msm) is also a recommended way of installing the DLLs. I fail to see a problem in this report. -- nosy: +loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16111 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3778] python uninstaller leave registry entries
Martin v. Löwis added the comment: Nobody has contributed a patch in five years, so it apparently is pretty hard. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3778 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18616] enable more ssl socket options with get_server_certificate
New submission from Derek Wilson: ssl.get_server_certificate does not allow advanced options like what ciphers to use (for ssl2 for instance) or SNI for virtual hosts with multiple ssl sites on one IP address. Adding **kwargs enables any current and future SSLSocket options to be passed along to the underlying connection. wrap_socket doesn't include all the options (npn and sni for instance), so I use SSLSocket instead. -- components: Extension Modules files: ssl_get_server_certificate_kwargs.patch keywords: patch messages: 194083 nosy: underrun priority: normal severity: normal status: open title: enable more ssl socket options with get_server_certificate type: enhancement versions: Python 3.4 Added file: http://bugs.python.org/file3/ssl_get_server_certificate_kwargs.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18616 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18569] Set PATHEXT in the Windows installer
Roundup Robot added the comment: New changeset 2a38e4da6ce8 by Martin v. Löwis in branch 'default': Issue #18569: The installer now adds .py to the PATHEXT variable http://hg.python.org/cpython/rev/2a38e4da6ce8 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18569 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18569] Set PATHEXT in the Windows installer
Martin v. Löwis added the comment: Thanks for the patch. It works fine (with the expected limitation that you need to restart running shells for this to take effect). -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18569 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18472] Update PEP 8 to encourage modern conventions
Guido van Rossum added the comment: I think the current wording about line length makes it too easy to adopt 99 instead of 79. I propose to go back to 79 only, and add this before the paragraph starting with The preferred way of wrapping long lines ... Some teams strongly prefer a longer line length. For code maintained exclusively or primarily by a team that can reach agreement on this issue, it is okay to increase the line nominal line length from 80 to 100 characters (effectively increasing the maximum length to 99 characters), provided that comments and docstrings are still wrapped at 72 characters. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18472 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18614] Enhanced \N{} escapes for Unicode strings
Matthew Barnett added the comment: I've attached a patch for this. -- keywords: +patch nosy: +mrabarnett Added file: http://bugs.python.org/file31112/issue18614.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18614 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18617] TLS and Intermediate Certificates
New submission from Donald Stufft: Currently the Python SSL module requires the full chain, including all intermediaries, to be served in order to validate a TLS connection. This isn't *wrong* however a number of folks have had issues trying to setup a custom PyPI index in pip due to missing them. The believed the problem with validation to be in pip/Python because it works in their browser. Essentially browsers have the ability to download missing intermediate certs using an url found inside the AIA data. This is slow and isn't generally recommended that you rely on it for any particular site. However it does mean that TLS connections work in more situations. At the least this should probably be documented, and possibly the Python library be enhanced to be more browser like in this regard. -- components: Library (Lib) messages: 194088 nosy: dstufft priority: normal severity: normal status: open title: TLS and Intermediate Certificates type: enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18617 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18472] Update PEP 8 to encourage modern conventions
Guido van Rossum added the comment: See proposed patch at https://codereview.appspot.com/12269044/ . -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18472 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18617] TLS and Intermediate Certificates
Christian Heimes added the comment: Thx! Let's update the docs for 2.7 to 3.4 first. For AIA intermediate cert retrieval we have to use OpenSSL's verify hook. It's a pain to implement all necessary bits and hard to use, though. :( -- nosy: +christian.heimes versions: +Python 2.7, Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18617 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16248] Security bug in tkinter allows for untrusted, arbitrary code execution.
Arfrever Frehtes Taifersar Arahesis added the comment: The fix in 2.6, 2.7, 3.1 and 3.2 branches introduced UnboundLocalError occurring when a non-None baseName parameter is passed. At least a part of fa82071bb7e1 should be backported to 2.6, 2.7, 3.1 and 3.2 branches. $ python2.7 -c 'import Tkinter; print(repr(Tkinter.Tk(baseName=some_name)))' Traceback (most recent call last): File string, line 1, in module File /usr/lib64/python2.7/lib-tk/Tkinter.py, line 1748, in __init__ if not sys.flags.ignore_environment: UnboundLocalError: local variable 'sys' referenced before assignment $ python3.2 -c 'import tkinter; print(repr(tkinter.Tk(baseName=some_name)))' Traceback (most recent call last): File string, line 1, in module File /usr/lib64/python3.2/tkinter/__init__.py, line 1734, in __init__ if not sys.flags.ignore_environment: UnboundLocalError: local variable 'sys' referenced before assignment -- resolution: fixed - stage: committed/rejected - status: closed - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16248 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18517] xxlimited extension declared incorrectly in setup.py
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18618] Need an atexit.register equivalent that also works in subinterps
Changes by Antoine Pitrou pit...@free.fr: -- components: +Interpreter Core, Library (Lib) priority: normal - low type: - enhancement versions: +Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18618 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18618] Need an atexit.register equivalent that also works in subinterps
New submission from Antoine Pitrou: Callbacks registered with atexit.register() are only called at shutdown of the main interpreter. For some purposes (perhaps most of them, arguably), you actually want to execute the callbacks at subinterpreter shutdown too. -- messages: 194092 nosy: pitrou, sbt priority: normal severity: normal status: open title: Need an atexit.register equivalent that also works in subinterps ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18618 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18618] Need an atexit.register equivalent that also works in subinterps
Antoine Pitrou added the comment: (note that weakref.finalize indirectly suffers from this problem) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18618 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16248] Security bug in tkinter allows for untrusted, arbitrary code execution.
Larry Hastings added the comment: You're talking about a new bug. Please open a new issue. I'm closing this issue right now because I want to cut a Python 3.4 alpha release tomorrow, and this bug is marked Python 3.4 and release blocker. -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16248 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17998] internal error in regular expression engine
Larry Hastings added the comment: I'm downgrading this to deferred blocker. I'm sure we'll get it fixed for Python 3.4 final, but in the meantime there's no sense in holding up Python 3.4a1 for it. -- priority: release blocker - deferred blocker ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17998 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16248] Security bug in tkinter allows for untrusted, arbitrary code execution.
Arfrever Frehtes Taifersar Arahesis added the comment: UnboundLocalError is effect of partially incorrect fix for this bug. It is better to update Versions field. -- resolution: fixed - status: closed - open versions: +Python 3.1 -Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16248 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18257] Two copies of python-config
Larry Hastings added the comment: Thanks, Matthias! Now I can cut 3.4a1 on time. :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18257 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18619] atexit leaks callbacks in subinterpreters
New submission from Antoine Pitrou: atexit uses PEP 3121 module initialization, and by this scheme each subinterpreter gets a separate module state. However, atexit's m_free doesn't actually decref the callbacks: it only frees the callbacks array, thinking the callbacks were already decref'ed when run. This is ok at main interpreter shutdown, but not at subinterpreter shutdown (see issue 18618). -- components: Interpreter Core, Library (Lib) messages: 194098 nosy: Robin.Schreiber, pitrou, sbt priority: normal severity: normal stage: needs patch status: open title: atexit leaks callbacks in subinterpreters type: resource usage versions: Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18619 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18472] Update PEP 8 to encourage modern conventions
Changes by Tshepang Lekhonkhobe tshep...@gmail.com: -- nosy: +tshepang ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18472 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18472] Update PEP 8 to encourage modern conventions
Tshepang Lekhonkhobe added the comment: @Guido am glad for the patch; it's a nice compromise -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18472 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18619] atexit leaks callbacks in subinterpreters
Antoine Pitrou added the comment: Here is a patch. It also enables GC on the atexit module. -- keywords: +patch Added file: http://bugs.python.org/file31113/atexit_leaks.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18619 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18619] atexit leaks callbacks in subinterpreters
Roundup Robot added the comment: New changeset 71b63a32b1e3 by Antoine Pitrou in branch 'default': Issue #18619: Fix atexit leaking callbacks registered from sub-interpreters, and make it GC-aware. http://hg.python.org/cpython/rev/71b63a32b1e3 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18619 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18619] atexit leaks callbacks in subinterpreters
Antoine Pitrou added the comment: The patch was simple enough that I decided to push it as-is :) Don't hesitate to make comments if you want, though. -- resolution: - fixed stage: needs patch - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18619 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18558] Iterable glossary entry needs clarification
Stephen Paul Chappell added the comment: If my program needed to know if an object is iterable, it would be tempting to define and call the following function instead of using collections.abc.Iterable: def iterable(obj): try: iter(obj) except TypeError: return False return True Something tells me that is not what the author of collections.abc.Iterable intended. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18558 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18608] Avoid keeping a strong reference to locale in the _io module
Roundup Robot added the comment: New changeset 1c9aa4f68f2b by Antoine Pitrou in branch 'default': Issue #18608: Avoid keeping a strong reference to the locale module inside the _io module. http://hg.python.org/cpython/rev/1c9aa4f68f2b -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18608 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18608] Avoid keeping a strong reference to locale in the _io module
Antoine Pitrou added the comment: Thanks Brett for reviewing. This is now pushed. -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18608 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18589] cross-referencing doesn't work between the extending guide and c-api
Roundup Robot added the comment: New changeset a381721299a3 by Antoine Pitrou in branch '3.3': Issue #18589: fix hyperlinking of type slots (tp_*) http://hg.python.org/cpython/rev/a381721299a3 New changeset 36ff479e429c by Antoine Pitrou in branch 'default': Issue #18589: fix hyperlinking of type slots (tp_*) http://hg.python.org/cpython/rev/36ff479e429c -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18589 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18589] cross-referencing doesn't work between the extending guide and c-api
Roundup Robot added the comment: New changeset bb546f6d8ab4 by Antoine Pitrou in branch '2.7': Issue #18589: fix hyperlinking of type slots (tp_*) http://hg.python.org/cpython/rev/bb546f6d8ab4 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18589 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18589] cross-referencing doesn't work between the extending guide and c-api
Changes by Antoine Pitrou pit...@free.fr: -- resolution: - fixed stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18589 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10241] gc fixes for module m_copy attribute
Antoine Pitrou added the comment: Ok, the patch doesn't apply cleanly but looks good regardless. (although I wonder whether you really reclaim significant stuff here: most C extension dicts should be mostly references to C methods and types) -- assignee: loewis - nosy: +pitrou type: behavior - resource usage versions: +Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10241 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10241] gc fixes for module m_copy attribute
Antoine Pitrou added the comment: I will still empty modules_by_index rather than Py_CLEAR it, though. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10241 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10241] gc fixes for module m_copy attribute
Changes by Antoine Pitrou pit...@free.fr: -- resolution: - fixed stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10241 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10241] gc fixes for module m_copy attribute
Roundup Robot added the comment: New changeset 62658d9d8926 by Antoine Pitrou in branch 'default': Issue #10241: Clear extension module dict copies at interpreter shutdown. http://hg.python.org/cpython/rev/62658d9d8926 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10241 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18214] Stop purging modules which are garbage collected before shutdown
Antoine Pitrou added the comment: By the way, you may be interested to learn that the patch in issue10241 has made things quite a bit better now: C extension modules can be collected much earlier. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18214 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16248] Security bug in tkinter allows for untrusted, arbitrary code execution.
Roundup Robot added the comment: New changeset 0f17aed78168 by Antoine Pitrou in branch '2.7': Fix tkinter regression introduced by the security fix in #16248. http://hg.python.org/cpython/rev/0f17aed78168 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16248 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18558] Iterable glossary entry needs clarification
R. David Murray added the comment: That would give you a false positive, though. It would return True for the 'y' in my example, which is not iterable. So Iterable's behavior here is an example of the Python design rule resist the temptation to guess. As Terry said, new classes should implement an __iter__ method. The __getitem__ iteration support is for backward compatibility. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18558 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16248] Security bug in tkinter allows for untrusted, arbitrary code execution.
Antoine Pitrou added the comment: I've committed a fix to 2.7 (I hope it's really a fix, since I don't know how to test it). I'll let Benjamin and Barry decide whether to backport to 2.6 and 3.2. As for 3.1, it's pretty much dead. -- priority: release blocker - deferred blocker stage: - committed/rejected versions: -Python 2.7, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16248 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18620] multiprocessing page leaves out important part of Pool example
New submission from Chris Curvey: on http://docs.python.org/2/library/multiprocessing.html, there is a bit about how to use a Pool properly, which looks like this pool = Pool(processes=4) # start 4 worker processes result = pool.apply_async(f, [10]) What this neglects to mention is that only one process will get any of the work. If you really want four processes in the pool to work, you have to call apply_async four times. For example: results = [] pool = Pool(processes=4) for i in xrange(4): results.append(pool.apply_async(f, [10])) hat tip to http://stackoverflow.com/questions/12483512/python-multiprocessing-apply-async-only-uses-one-process -- assignee: docs@python components: Documentation messages: 194115 nosy: Chris.Curvey, docs@python priority: normal severity: normal status: open title: multiprocessing page leaves out important part of Pool example type: enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18620 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1294959] Problems with /usr/lib64 builds.
Changes by Catalin Iacob iacobcata...@gmail.com: -- nosy: +catalin.iacob ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1294959 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18306] os.stat gives exception for Windows junctions in v3.3
John Jefferies added the comment: On 01/08/2013 12:09, Tim Golden wrote: Tim Golden added the comment: I propose to close this one: using Python 3.3 on Win7 I can successfully stat NTFS Junctions. Is there any remaining issue? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18306 ___ The original issue remains for me on v3.3.2. I can stat junctions in my user directory, but not in system directories. In v3.2 I can do that provided I am running with elevated privilege. If it's fixed in the next version that's great. Python 3.3.2 (v3.3.2:d047928ae3f6, May 16 2013, 00:03:43) [MSC v.1600 32 bit (Intel)] on win32 Type help, copyright, credits or license for more information. import os os.stat(r'C:\Windows\System32\config\systemprofile\SendTo') Traceback (most recent call last): File stdin, line 1, in module FileNotFoundError: [WinError 2] The system cannot find the file specified: 'C:\\Windows\\System32\\config\\systemprofile\\SendTo' Regards John -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18306 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18621] site.py keeps too much stuff alive when it patches builtins
New submission from Antoine Pitrou: The site module patches the builtins module unless Python is run with -S. Unfortunately, this means the builtins dict then keeps the site module globals alive until the end of interpreter shutdown, preventing the garbage collection of many other objects or modules. Attached patch isolates those patched builtins inside a separate module _sitebuiltins. -- components: Library (Lib) files: sitebuiltins.patch keywords: patch messages: 194117 nosy: pitrou, sbt priority: normal severity: normal stage: patch review status: open title: site.py keeps too much stuff alive when it patches builtins type: resource usage versions: Python 3.4 Added file: http://bugs.python.org/file31114/sitebuiltins.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18621 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15631] Python 3.3/3.4 installation issue on OpenSUSE lib/lib64 folders
Catalin Iacob added the comment:
In reply to msg168184, LIBDIR is set to include lib64 instead of lib because
openSUSE explicitly does it that way in their multilib implementation.
More specifically, the CONFIG_SITE environment variable is set to
/usr/share/site/x86_64-unknown-linux-gnu which contains, among more stuff:
catalin@opensuse:~/hacking/cpython cat $CONFIG_SITE | grep libdir
# If user did not specify libdir, guess the correct target:
if test $libdir = '${exec_prefix}/lib' ; then
libdir='${exec_prefix}/lib64'
/usr/share/site/x86_64-unknown-linux-gnu is owned by package site-config whose
README says:
site-config: Site Paths Configuration for autoconf Based configure Scripts
==
Site configuration for autoconf based configure scripts provides smart
defaults for paths that are not specified.
All autoconf based configure scripts will automatically resource site
script using CONFIG_SITE environment variable. It works without any
explicit user interaction.
Currently implemented features:
Automatic libdir setup to $exec_prefix/lib or $exec_prefix/lib64
Depending on architecture, site script should correctly and
automatically switch between lib and lib64 libdir.
libexecdir setup to $exec_prefix/lib
Upstream libexecdir defaults to $exec_prefix/libexec. This directory is
not part of FHS 2.2, so we change it to $exec_prefix/lib (yes, it is
correct to set it to $exec_prefix/lib even for bi-arch platforms). Most
projects add package name to this path, so you most probably get what
FHS 2.2 expects.
--
nosy: +catalin.iacob
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15631
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18622] reset_mock on mock created by mock_open causes infinite recursion
New submission from Michael Foord: As reported at: http://code.google.com/p/mock/issues/detail?id=209 from unittest import mock [107971 refs] mock.mock_open function mock_open at 0x10cff9d20 [107974 refs] a = mock.mock_open() [109965 refs] a.reset_mock() ... -- assignee: michael.foord components: Library (Lib) keywords: easy messages: 194119 nosy: michael.foord priority: normal severity: normal stage: needs patch status: open title: reset_mock on mock created by mock_open causes infinite recursion type: behavior versions: Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18622 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10241] gc fixes for module m_copy attribute
Antoine Pitrou added the comment: Reopening. This seems to produce segfaults on several of the buildbots, e.g.: http://buildbot.python.org/all/builders/x86%20XP-4%203.x/builds/8947 http://buildbot.python.org/all/builders/x86%20Windows%20Server%202003%20%5BSB%5D%203.x/builds/1257 http://buildbot.python.org/all/builders/x86%20Gentoo%203.x/builds/4671 -- resolution: fixed - status: closed - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10241 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18605] 2.7: test_threading hangs on Solaris 9
Maciej Bliziński added the comment: Here's the output. After that output -- it hangs. == CPython 2.7.5 (default, Jul 30 2013, 01:41:03) [GCC 4.6.3] == Solaris-2.9-sun4u-sparc-32bit-ELF big-endian == /home/maciej/src/opencsw/pkg/lang-python/python/branches/python-2.7/work/solaris9-sparc/build-isa-sparcv8/Python-2.7.5/build/test_python_28299 Testing with flags: sys.flags(debug=0, py3k_warning=0, division_warning=0, division_new=0, inspect=0, interactive=0, optimize=0, dont_write_bytecode=0, no_user_site=0, no_site=0, ignore_environment=0, tabcheck=0, verbose=0, unicode=0, bytes_warning=0, hash_randomization=0) test_threading test_acquire_contended (test.test_threading.LockTests) ... ok test_acquire_destroy (test.test_threading.LockTests) ... ok test_acquire_release (test.test_threading.LockTests) ... ok test_constructor (test.test_threading.LockTests) ... ok test_different_thread (test.test_threading.LockTests) ... ok test_reacquire (test.test_threading.LockTests) ... ok test_thread_leak (test.test_threading.LockTests) ... ok test_try_acquire (test.test_threading.LockTests) ... ok test_try_acquire_contended (test.test_threading.LockTests) ... ok test_with (test.test_threading.LockTests) ... ok test__is_owned (test.test_threading.RLockTests) ... ok test_acquire_contended (test.test_threading.RLockTests) ... ok test_acquire_destroy (test.test_threading.RLockTests) ... ok test_acquire_release (test.test_threading.RLockTests) ... ok test_constructor (test.test_threading.RLockTests) ... ok test_different_thread (test.test_threading.RLockTests) ... ok test_reacquire (test.test_threading.RLockTests) ... ok test_release_unacquired (test.test_threading.RLockTests) ... ok test_thread_leak (test.test_threading.RLockTests) ... ok test_try_acquire (test.test_threading.RLockTests) ... ok test_try_acquire_contended (test.test_threading.RLockTests) ... ok test_with (test.test_threading.RLockTests) ... ok test_is_set (test.test_threading.EventTests) ... ok test_notify (test.test_threading.EventTests) ... ok test_timeout (test.test_threading.EventTests) ... ok test__is_owned (test.test_threading.ConditionAsRLockTests) ... ok test_acquire_contended (test.test_threading.ConditionAsRLockTests) ... ok test_acquire_destroy (test.test_threading.ConditionAsRLockTests) ... ok test_acquire_release (test.test_threading.ConditionAsRLockTests) ... ok test_constructor (test.test_threading.ConditionAsRLockTests) ... ok test_different_thread (test.test_threading.ConditionAsRLockTests) ... ok test_reacquire (test.test_threading.ConditionAsRLockTests) ... ok test_release_unacquired (test.test_threading.ConditionAsRLockTests) ... ok test_thread_leak (test.test_threading.ConditionAsRLockTests) ... ok test_try_acquire (test.test_threading.ConditionAsRLockTests) ... ok test_try_acquire_contended (test.test_threading.ConditionAsRLockTests) ... ok test_with (test.test_threading.ConditionAsRLockTests) ... ok test_acquire (test.test_threading.ConditionTests) ... ok test_notify (test.test_threading.ConditionTests) ... ok test_timeout (test.test_threading.ConditionTests) ... ok test_unacquired_notify (test.test_threading.ConditionTests) ... ok test_unacquired_wait (test.test_threading.ConditionTests) ... ok test_acquire (test.test_threading.SemaphoreTests) ... ok test_acquire_contended (test.test_threading.SemaphoreTests) ... ok test_acquire_destroy (test.test_threading.SemaphoreTests) ... ok test_constructor (test.test_threading.SemaphoreTests) ... ok test_default_value (test.test_threading.SemaphoreTests) ... ok test_release_unacquired (test.test_threading.SemaphoreTests) ... ok test_try_acquire (test.test_threading.SemaphoreTests) ... ok test_try_acquire_contended (test.test_threading.SemaphoreTests) ... ok test_with (test.test_threading.SemaphoreTests) ... ok test_acquire (test.test_threading.BoundedSemaphoreTests) ... ok test_acquire_contended (test.test_threading.BoundedSemaphoreTests) ... ok test_acquire_destroy (test.test_threading.BoundedSemaphoreTests) ... ok test_constructor (test.test_threading.BoundedSemaphoreTests) ... ok test_default_value (test.test_threading.BoundedSemaphoreTests) ... ok test_recursion_limit (test.test_threading.BoundedSemaphoreTests) ... skipped 'test macosx problem' test_release_unacquired (test.test_threading.BoundedSemaphoreTests) ... ok test_try_acquire (test.test_threading.BoundedSemaphoreTests) ... ok test_try_acquire_contended (test.test_threading.BoundedSemaphoreTests) ... ok test_with (test.test_threading.BoundedSemaphoreTests) ... ok test_PyThreadState_SetAsyncExc (test.test_threading.ThreadTests) ... started worker thread trying nonsensical thread id waiting for worker thread to get started verifying worker hasn't exited attempting to raise asynch exception in worker waiting for worker to say it caught the exception all OK -- joining worker ok test_dummy_thread_after_fork (test.test_threading.ThreadTests) ... ok test_enumerate_after_join
