[issue20863] IDLE not opening
New submission from Chester Burns: I installed python 3.3.3 and it was working fine for the moment, however the next day when I tried to open it, the idle app showed on the dock for a second and straight away quit. I am using a macbook pro on osx version 10.9.1 -- messages: 212863 nosy: chester.burns priority: normal severity: normal status: open title: IDLE not opening versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20863 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20863] IDLE not opening
Ned Deily added the comment: Try launching IDLE from a Terminal shell window by typing: /usr/local/bin/idle3.3 and see if it fails there and, if so, any messages shown. One possibility is the problem reported in http://bugs.python.org/issue18270 which was fixed in the IDLE shipped with Python 3.3.4. -- nosy: +ned.deily ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20863 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20761] os.path.join doesn't strip LF or CR
Georg Brandl added the comment: Agreed. -- nosy: +georg.brandl status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20761 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20863] IDLE not opening
Chester Burns added the comment:
I tried that and it came up with this:
Traceback (most recent call last):
File /usr/local/bin/idle3.3, line 5, in module
main()
File
/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/idlelib/PyShell.py,
line 1572, in main
shell.interp.runcommand(''.join((print(', tkversionwarning, '
AttributeError: 'NoneType' object has no attribute 'interp'
I also tried typing 'open /usr/local/bin/idle3.3' and it returned this:
No application knows how to open /usr/local/bin/idle3.3.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20863
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20863] IDLE not opening
Ned Deily added the comment: Thanks for the update. That is indeed the symptom of the problem documented in Issue18270. The best solution is to download and install Python 3.3.4 which has a fix for it. -- resolution: - duplicate stage: - committed/rejected superseder: - IDLE on OS X fails with Attribute Error if no initial shell and Tk out-of-date ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20863 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20788] distutils.msvccompiler - flags are hidden inside initialize()
Éric Araujo added the comment: It may be a good idea to make this information directly available in the sysconfig module, for example. Before working on a patch right away, I’d recommend getting in touch with build tools developers and ask them what other hidden information they are extracting from distutils internals, so that a clean, comprehensive proposal can be made for Python 3.5 (as a new feature, this cannot go into existing stable versions). -- nosy: +eric.araujo, mhammond, tim.golden type: - enhancement versions: +Python 3.5 -Python 2.7, Python 3.1, Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20788 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue809163] Can't add files with spaces
Éric Araujo added the comment: Yes, this issue is not addressed. A test is added by the latest patch and reproduces the issue; now bdist_rpm should be changed to make the test pass. See also my previous comment. -- components: -Distutils2 stage: patch review - needs patch versions: +Python 3.3, Python 3.4, Python 3.5 -3rd party, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue809163 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20744] shutil should not use distutils
Éric Araujo added the comment: Patch looks good to me. -- stage: needs patch - patch review versions: +Python 3.5 -Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20744 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
Nick Coghlan added the comment: More proposals from the thread (paraphrased): - make any aware time() object always True (leave naive midnight as False) - make any aware time() object with a non-zero UTC offset always True (leave naive midnight and UTC midnight as False) - deprecate aware time() entirely (raises the thorny question of what to return from .time() on an aware datetime() object) - add helpers to retrieve naivemidnight and utcmidnight constants, and calculate a localmidnight value (needs to be dynamic in case the local timezone is changed) Independent observation: - if time() objects are supposed to be interpreted as representing a time difference relative to midnight rather than a structured object, why is it so hard to actually convert them to an appropriate time delta? There's no method for it, you can't just subtract midnight, there's no constructor on time delta that accepts a time object, you can't easily attach a date to the time to calculate a time delta. Use case presented for the current behaviour: - a simulation that tracks the time and date of the simulation independently and relies on the implicit bool behaviour of time objects (not stated why this is considered more maintainable than explicit comparisons with appropriate midnight objects) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13936 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4508] distutils compiler not handling spaces in path to output/src files
Éric Araujo added the comment: Thanks Brian, let’s try and get this fixed. I've put together a patch adding the test requested. There is no problem on my Ubuntu machine with python 3.3. Are you saying the test does not reproduce the bug discussed here? There is a comment in the file saying Don't load the xx module more than once, I am unsure whether my patch (using a renamed c file) violates this? Hm I’m not quite sure if it’s enough that the extensions use different file names, or if they should also have different names inside the code. Existing tests already create and import xx multiple times though… One can create a python file my file.py and can import it with __import__(my file). I couldn't do the same for a C extension. One can’t do “import my file” though, so I would sweep this under the rug as an obscure corner case :‑) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4508 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16484] pydoc generates invalid docs.python.org link for xml.etree.ElementTree and other modules
Changes by Éric Araujo mer...@netwok.org: -- stage: needs patch - test needed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16484 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
Nick Coghlan added the comment: Current status of thread discussion (yes, I'm biased, and that shows in the phrasing below): Arguments raised for status quo: - the module is behaving exactly as described in the documentation - removing false time values will require affected users to update their code to instead explicitly compare with appropriate midnight values before migrating to Python 3.5 (or, since deprecation warnings are silent by default, except if a test framework enables them, Python 3.6) - it wasn't an accident, it was designed so modulo arithmetic could reasonably be implemented for time() objects (which hasn't been demanded or implemented since the datetime module was created) - changing behaviour so that a current subtle data driven bug instead becomes a harmless violation of recommended style for comparison against a sentinel value is encouraging bad programming practices Arguments in favour of changing the behaviour: - datetime.time() objects don't behave like a number in any other way (they don't support arithmetic and attempting to convert them with int, float, etc explicitly tells you they're not numbers), and don't even provide an easy way to convert them to a time delta relative to midnight (and hence to seconds since midnight via total_seconds), so it's surprising that they behave like a number in boolean context by having a concept of zero - the current behaviour takes something that would be a harmless style error for most structured data types (including datetime and date objects) and instead makes it a subtle data driven behavioural bug (but only if you're using naive times or a timezone with a non-negative UTC offset) - the current behaviour cannot even be accurately summarised as midnight evaluates as False, because it is actually naive midnight and UTC midnight with a non-negative UTC offset evaluate as false, while UTC midnight with a negative UTC offset evaluates as true. That's incoherent and really should be changed, and if we're going to change the behaviour anyway, we may as well change it to something less dangerous. - any affected code that relies on some variants of midnight being False is already hard to understand (since most readers won't be aware of this subtlety of the behaviour of time objects) and would be made clearer by explicitly comparing against appropriate midnight objects -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13936 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19021] AttributeError in Popen.__del__
Larry Hastings added the comment: Those six revisions have been cherry-picked into 3.4.0. -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19021 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20808] 3.4 cherry pick: 6a1711c96fa6 (Popen.__del__ traceback)
Larry Hastings added the comment: ok. -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20808 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19021] AttributeError in Popen.__del__
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- stage: needs patch - committed/rejected ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19021 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20864] getattr does not work well with descriptor
New submission from Martin Thurau: If you have a descriptor (in my case it was an SQLAlchemy column) on an instance and this descriptor returns None for a call to __get__ then getattr with a given default value, will not return the default, but None. I have no knowledge on the implementation details of getattr but I guess the logic is something like this: - getattr looks at the given object and sees that the attribute in question is not None (since it is the descriptor object) - getattr returns the descriptor - the descriptors __get__ method is called - __get__ return None Maybe it should be more like this: - getattr looks at the given object and sees that the attribute in question is not None (since it is the descriptor object) - getattr sees that the attribute has __get__ - getattr calls __get__ method and looks if the return value is None I'm not sure if this is really a bug but it's highly confusing and somewhat un-pythonic. I really should not care of an attribute of an object is a value or a descriptor. This is especially true since this problem also applies to @property. Effectively this means that if you call getattr you have *know* if the name in question is a property or not and one can't simply swap out an objects value for a property without risking to break calling code. If this is actually *not* a bug, we should at least update the documentation to getattr, to mention this fact. Because currently it states that getattr(x, 'foobar') is equivalent to x.foobar which is obviously not true. -- components: Interpreter Core files: python_descriptor_bug.py messages: 212876 nosy: Martin.Thurau priority: normal severity: normal status: open title: getattr does not work well with descriptor type: behavior versions: Python 2.7 Added file: http://bugs.python.org/file34299/python_descriptor_bug.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20864 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2818] pulldom cannot handle xml file with large external entity properly
Changes by M. Volz marie...@gmail.com: -- nosy: +mvolz ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2818 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
Skip Montanaro added the comment: the current behaviour takes something that would be a harmless style error for most structured data types ... I'm not sure what a structured data type is, but in my mind the original poster's construct is more than a style error. He was using None as a sentinel, but not explicitly testing for its presence. The same error would be present if he used None as a sentinel value where the range of possible values was the set of all integers. If there are problems with the definition of false time such that there are some combinations of time and timezone where UTC midnight is not zero, I would prefer to correct them. Further, playing the devil's advocate, if you dispense with any false elements of time objects, why not simply zero out the nb_nonzero slot in time_as_number? Once that's gone, the time_as_number structure is all zeros, so the tp_as_number slot in PyDateTime_TimeType can be cleared. -- nosy: +skip.montanaro ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13936 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17128] OS X system openssl deprecated - installer should build local libssl
Changes by Piotr Dobrogost p...@bugs.python.dobrogost.net: -- nosy: +piotr.dobrogost ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17128 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13968] Support recursive globs
Nick Coghlan added the comment: Oops, Python 3.4 has ** support in pathlib, but we missed Serhiy's patch for the glob module itself. We should resolve that discrepancy for 3.5 :) -- versions: +Python 3.5 -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13968 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
Nick Coghlan added the comment: Structured data is just a shorthand way of referring to any Python object which is neither a number or a container and exhibits the default boolean behaviour where all instances are true. The problem datetime.time is both that its current behaviour is internally incoherent (whether or not an aware time is false depends on the current timezone in unpredictable ways) and *also* inconsistent with its other behaviours that indicate it should be handled as a non-numeric value. Since it isn't a container either, standard conventions suggest that it should always be true. No *compelling* justifications for its atypical behaviour have been presented, just a case of Tim wanting to leave the door open to adding modular arithmetic directly on time instances. I suggest it makes far more sense to instead eliminate the quirky behaviour entirely and instead provide an easy way to convert a time to a timedelta relative to midnight. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13936 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
R. David Murray added the comment: it wasn't an accident, it was designed so modulo arithmetic could reasonably be implemented for time() objects (which hasn't been demanded or implemented since the datetime module was created) Ah, interesting. I just wrote a program last month where I was baffled that time didn't support arithmetic, and had to dodge painfully through datetime instances to do the arithmetic. I asked about it on IRC and someone said it was because arithmetic on times was ambiguous because of timezones, and I just accepted that rather than wonder why it hadn't been implemented. Otherwise I'm pretty sympathetic to the RFE, but I'd really like time arithmetic to work, so I guess I'd have to be -1 in that case, wouldn't I? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13936 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
Antoine Pitrou added the comment: Otherwise I'm pretty sympathetic to the RFE, but I'd really like time arithmetic to work, so I guess I'd have to be -1 in that case, wouldn't I? Adding times of the day sounds as well-defined to me as adding centigrade temperatures. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13936 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19915] int.bit_at(n) - Accessing a single bit in O(1)
HCT added the comment: then I guess it's either a new function to int or a new type of int for this type of operations. similar to bytearray/ctypes and memoryview -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19915 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
R. David Murray added the comment: As does adding dates. I'm talking about timedelta arithmetic, just like for datetimes. I believe that still requires modulo arithmetic :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13936 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
Alexander Belopolsky added the comment: On Mar 7, 2014, at 10:12 AM, R. David Murray rep...@bugs.python.org wrote: I asked about it on IRC and someone said it was because arithmetic on times was ambiguous because of timezones, and I just accepted that rather than wonder why it hadn't been implemented. Otherwise I'm pretty sympathetic to the RFE, but I'd really like time arithmetic to work, so I guess I'd have to be -1 in that case, wouldn't I? See http://bugs.python.org/issue17267 -- nosy: +Alexander.Belopolsky ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13936 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20865] A run has overwrite my code save
New submission from NexusRAwesome1995 .: I am making a text based aventure game for my assignment and a friends test run has somehow saved over the entire code file and now im using an earlier version of the code. I have 0 idea if there is anyway to look at the code using the IDLE and i need to do it to see how i fixed the fatal error left behind by a friend. My on computer backup has not worked and the backup on my memory stick also has the same problem. If anyone knows of a way to get my code back i will be grateful as this is my 1st project and i'm not that used to the syntax -- messages: 212885 nosy: NexusRAwesome1995.. priority: normal severity: normal status: open title: A run has overwrite my code save type: behavior versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20865 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
Alexander Belopolsky added the comment: On Mar 7, 2014, at 10:15 AM, Antoine Pitrou rep...@bugs.python.org wrote: Adding times of the day sounds as well-defined to me as adding centigrade temperatures. What is wrong with adding temperatures? Climate people do it all the time when computing the averages. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13936 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20865] A run has overwrite my code save
Zachary Ware added the comment: Sorry, the bug tracker is not the place to look for help like this. Please redirect your question to python-list[1], where several very knowledgeable people listen in and are ready to render assistance for any manner of problems using Python. [1] https://mail.python.org/mailman/listinfo/python-list -- nosy: +zach.ware resolution: - invalid stage: - committed/rejected status: open - closed type: behavior - ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20865 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17267] datetime.time support for '+' and '-'
Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17267 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8902] add datetime.time.now() for consistency
Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8902 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20271] urllib.parse.urlparse() accepts wrong URLs
STINNER Victor added the comment: Oh, by the way my patch fixes also #18191. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20271 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20271] urllib.parse.urlparse() accepts wrong URLs
STINNER Victor added the comment: Here is a patch for Python 3.5 which breaks backward compatibility: urlparse functions now raise a ValueError if the IPv6 address, port or host is invalid. Examples of invalid URLs: - HTTP://WWW.PYTHON.ORG:65536/doc/#frag: 65536 is invalid - http://www.example.net:foo; - http://::1/; - http://[127.0.0.1]/; - http://[host]/; According to unit tests, Python 3.4 is more tolerant: it only raises an error when the port number is read (obj.port) from an URL with an invalid port. There error is not raised when the whole URL is parsed. Is it ok to break backward compatibility? -- keywords: +patch nosy: +gvanrossum, haypo Added file: http://bugs.python.org/file34300/urlparse.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20271 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20271] urllib.parse.urlparse() accepts wrong URLs
STINNER Victor added the comment: My patch urlparse.patch may be modified to fix also #18191 in Python 2.7, 3.3 and 3.4: splitport() should handle IPv6 ([::1]:80) and auth (user:passowrd@host) but not raises an exception. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20271 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18191] urllib2/urllib.parse.splitport does not handle IPv6 correctly
STINNER Victor added the comment: I posted a patch to #20271 which should fix the issue. I wrote the patch for Python 3.5, but it can be adapted to be tolerant (don't make extensive tests on port number, host and IPv6) for older versions. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18191 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
Tim Peters added the comment: [Nick] - deprecate aware time() entirely (raises the thorny question of what to return from .time() on an aware datetime() object) aware_datetime_object.time() already returns a naive time object. The thorny question is what .timetz() should return - but if aware time objects _were_ deprecated, .timetz() itself would presumably be deprecated too. ... you can't easily attach a date to the time to calculate a time delta. The class constructor datetime.combine(date_object, time_object) makes it easy to combine any two date and time objects into a datetime object. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13936 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20812] Explicitly cover application migration in the 2-3 guide
Roundup Robot added the comment: New changeset 2a922153463e by Brett Cannon in branch 'default': Issue #20812: Add a short opener to the Python 2/3 porting HOWTO. http://hg.python.org/cpython/rev/2a922153463e -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20812 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20812] Explicitly cover application migration in the 2-3 guide
Changes by Brett Cannon br...@python.org: -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20812 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20813] Backport revised 2to3 guide to older branches
Roundup Robot added the comment: New changeset a24085e1b1f5 by Brett Cannon in branch '3.3': Issue #20813: Backport Python 2/3 HOWTO updates http://hg.python.org/cpython/rev/a24085e1b1f5 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20813 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20812] Explicitly cover application migration in the 2-3 guide
Roundup Robot added the comment: New changeset c83ce2a1841c by Brett Cannon in branch 'default': null merge for issue #20812 http://hg.python.org/cpython/rev/c83ce2a1841c -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20812 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20813] Backport revised 2to3 guide to older branches
Brett Cannon added the comment: Same version now in default, 3.3, and 2.7. -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20813 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
Changes by Mark Dickinson dicki...@gmail.com: -- nosy: +mark.dickinson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13936 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20866] segfailt with os.popen and SIGPIPE
New submission from Hanno Boeck: I experience a segmentation fault with python 2.7 (both 2.7.5 and 2.7.6 tested on Ubuntu and Gentoo) when a large file is piped, the pipe is passed to os.popen and the process sends a SIGPIPE signal. To create an easy to reproduce testcase grep can be used. See example attached. To test first create a dummy file containing zeros, around 1 megabyte is enough: for i in `seq 1 10`; do echo 0123456789 dummy.txt; done Then pipe it to the script attached like this: cat dummy.txt | python2 minimal.py Result is a Segmentation fault. The same code doesn't segfault with python 3. -- components: Interpreter Core files: sigpipe_crash.py messages: 212897 nosy: hanno priority: normal severity: normal status: open title: segfailt with os.popen and SIGPIPE type: crash versions: Python 2.7 Added file: http://bugs.python.org/file34301/sigpipe_crash.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20866 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20863] IDLE not opening
Changes by Ned Deily n...@acm.org: -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20863 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
Changes by Westley Martínez aniko...@gmail.com: -- nosy: +westley.martinez ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13936 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17267] datetime.time support for '+' and '-'
Alexander Belopolsky added the comment: I think the timezone related problems are a red herring. Aware datetime +/- timedelta arithmetics is naive - tzinfo is ignored in calculations and copied to the result: http://hg.python.org/cpython/file/c83ce2a1841c/Lib/datetime.py#l1711 The utcoffset only will only come into play if we want to implement time - time - timedelta, but this problem is already there in time comparisons: http://hg.python.org/cpython/file/c83ce2a1841c/Lib/datetime.py#l1091 It is up to tzinfo subclass implementation writers to handle inability to compute utcoffset without date fields by raising an exception if necessary. It is perfectly fine for time - time to fail with an error coming from .utcoffset(). I also don't think the fate of #13936 has any bearing on this issue. As long as we are not trying to implement time + time - time, we are not introducing any new notion of zero time. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17267 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20867] fix_import in 2to3 adds spurious relative import (windows)
New submission from Claudio Canepa: 0. windows specific i. In the pyglet library, written for py2 and officially running in 3 after the stock installation that does the 2to3 conversion ii. Omitting files which are unimportant for the issue, the package dir looks as pyglet image codecs pil.py (each package - subpackage has a proper __init__.py) iii. In the pyglet repository checkout, near the begining of pil.py theres the block try: import Image except ImportError: from PIL import Image That PIL refers to the pillow package (fork of PIL, and yes it its the recommended import line in pillow's doc) iv. after installing with cd working_copy py -3.3 setup.py install the same block looks as try: import Image except ImportError: from .PIL import Image which is wrong, and precludes pyglet to import Pillow. v. I tracked the problem to (CPython) LIB/lib2to3/fixes/fix_import.py In method FixImport.probably_a_local_import the heuristic is if 'import name' is seen, look if theres a sibling file with that name, and if exists assume it needs to be a relative import The problem is that the implementation uses os.path.exists to check sibling existence, but that has false positive cases due to Windows case-insensivity for filenames. Module names are case-sensitive. So, the import machinery would never match PIL to pil, but the code in fix_import.py will merrily match. vi. To verify the issue I patched fix_import.py, deleted the old pyglet install under 3, reinstalled: Now the block is unmolested. Attached the diff with the fixed code (diff obtained with the GNU C utils) vii. This was seen in python 3.3.1 , on Windows xp sp3. I see in the cpython repo the same issue will happen in the default branch (the offending lines in fix_import.py are unchanged, so I assume 3.4 will show the same defect) viii. as a reference, the original issue in pyglet can be found at http://code.google.com/p/pyglet/issues/detail?id=707 ix. Anyone can suggest a workaround, a change in the problematic block in pyglet that would tell 2to3 to not change the block ? -- components: 2to3 (2.x to 3.x conversion tool) files: fix_import.diff keywords: patch messages: 212899 nosy: ccanepa priority: normal severity: normal status: open title: fix_import in 2to3 adds spurious relative import (windows) type: behavior versions: Python 3.3 Added file: http://bugs.python.org/file34302/fix_import.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20867 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue809163] Can't add files with spaces
Matheus Vieira Portela added the comment: I tried to apply the last patch but it returned me and error of failing hunk. I think it was based on an old version of the test_bdist_rpm.py file. Hence, I made this updated version of the patch and could get the expected failure during the tests. I should try and solve this bug soon. -- Added file: http://bugs.python.org/file34303/test_bdist_rpm_filename_with_whitespaces.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue809163 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20867] fix_import in 2to3 adds spurious relative import (windows)
Changes by Ned Deily n...@acm.org: -- nosy: +benjamin.peterson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20867 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1580] Use shorter float repr when possible
Changes by Eric Snow ericsnowcurren...@gmail.com: -- nosy: +eric.snow ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1580 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20849] add exist_ok to shutil.copytree
Éric Araujo added the comment: Contrary to makedirs, there could be two interpretations for exist_ok in copytree: a) if a directory or file already exists in the destination, ignore it and go ahead b) only do that for directories. The proposed patch does b), but the cp tool does a). It’s not clear to me which is best. Can you start a discussion on the python-ideas mailing list? -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20849 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20851] Update devguide to cover testing from a tarball
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20851 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20847] asyncio docs should call out that network logging is a no-no
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20847 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20840] AttributeError: 'module' object has no attribute 'ArgumentParser'
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20840 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20819] reinitialize_command doesn't clear install_lib on install and install_lib commands
Éric Araujo added the comment: If there is indeed a bug, I fear this is one of these areas where a fix actually breaks other build tools reusing distutils internals. -- nosy: +eric.araujo versions: -Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20819 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20837] Ambiguity words in base64 documentation
Éric Araujo added the comment: Additional edit to make the patch crystal-clear: “using all three alphabets (normal, URL and Filesystem safe alphabet).” → “using all three alphabets defined in the RFC (normal, URL-safe and filesystem-safe)” -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20837 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
Ethan Furman added the comment: If no one else has gotten to this in the next six months or so, I will. :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13936 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18882] Add threading.main_thread() function
Andrew Svetlov added the comment: Implementation uses the first choice: main_thread() returns the original _MainThread instance, even if it's dead in the child process. I'm sorry, would you guess desired documentation change? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18882 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue694339] IDLE: Dedenting with Shift+Tab
Sean Wolfe added the comment: I did a couple tests and the shift-tab and tab work pretty much as expected. There's a small quirk for a single-line edit: * place cursor on beginning of line * tab forward -- the text indents as expected * shift-tab -- the entire line is highlighted -- the cursor now appears beneath the line -- subsequent typing however affects the highlighted line For the single-line case, it would be cleaner to have it stay on the same line without highlighting. This is OSX 10.9, python 2.7.6+ and 3.4.rc1+ -- nosy: +Sean.Wolfe ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue694339 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4931] distutils does not show any error msg when can't build C module extensions due to a missing C compiler
Thomas Kluyver added the comment: Any chance of getting this patch applied? It clearly makes the error message more useful, and we've run into another case where grok_environment_error gives the wrong result: when symlinking fails because the target exists, it now says File exists: source, because e.filename is the source and e.filename2 the target. It's also rather embarassing that a function in Python 3.4 still says Handles Python 1.5.1 and 1.5.2 styles... in the docstring. -- nosy: +takluyver ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4931 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19333] distutils.util.grok_environment_error loses the error message
Thomas Kluyver added the comment: Duplicate of issue 4931. This function should be entirely unnecessary now. -- nosy: +takluyver ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19333 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19333] distutils.util.grok_environment_error loses the error message
Changes by Éric Araujo mer...@netwok.org: -- resolution: - duplicate stage: - committed/rejected status: open - closed superseder: - distutils does not show any error msg when can't build C module extensions due to a missing C compiler ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19333 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4931] distutils does not show any error msg when can't build C module extensions due to a missing C compiler
Éric Araujo added the comment: I want to make time for Python bugs again, so I’ll try and finish this bug soon. See also msg200785 for a report from setuptools with an easy to reuse test case. -- versions: +Python 3.3, Python 3.4 -3rd party, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4931 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20868] Lib/test/test_socket.py: skip testGetServBy if /etc/services is not found
New submission from Steap: In Lib/test/test_socket.py, testGetServBy calls socket.getservbyname(), which needs /etc/services (see man getservbyname). If this file is not found, the test fails instead of being skipped. The attached patch was written against the latest revision of the Mercurial repository. It might be worth applying it for every currently supported version of Python. -- files: skip_testGetServBy.patch keywords: patch messages: 212910 nosy: Steap priority: normal severity: normal status: open title: Lib/test/test_socket.py: skip testGetServBy if /etc/services is not found Added file: http://bugs.python.org/file34304/skip_testGetServBy.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20868 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
Westley Martínez added the comment: So is the plan to deprecate this in 3.5 and remove in 3.6? If so, the question is where should the deprecation be thrown? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13936 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20868] Lib/test/test_socket.py: skip testGetServBy if /etc/services is not found
Ned Deily added the comment: Unfortunately, how getservbyname() and other similar network interface functions get their data is platform-dependent. /etc/services is a traditional file location but many modern systems use a database or shared database (e.g. NIS) and even allow the system administrator to dynamically change the source of the data. So, checking for /etc/services would cause the test to be skipped needlessly. I would think that most systems would not be very usable without a working getservbyname(). Under what circumstances is this causing a problem for you? -- nosy: +ned.deily ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20868 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20864] getattr does not work well with descriptor
Eric Snow added the comment: Returning None is the right thing here. The default for getattr() is returned only when it catches an AttributeError (hence the exception is the sentinel, so to speak, not None. Here's a rough equivalent: _notset = object() def getattr(obj, name, default=_notset): getter = type(obj).__getattribute__ try: getter(obj, name) # The normal object lookup machinery. except AttributeError: if default is _notset: raise return default The underlying lookup machinery isn't the simplest thing to grok. Here is the gist of what happens: 1. Try a data descriptor. 2. Try the object's __dict__. 3. Try a non-data descriptor. 4. Try __getattr__(). 5. raise AttributeError. Thus the descriptor's __get__() would have to raise AttributeError to trigger the default. If need be, it should turn None into AttributeError or you can use some other default than None in your getattr() call and turn None into an AttributeError yourself. What about getattr(x, 'foobar') is equivalent to x.foobar is not correct? It doesn't matter if the value came from a descriptor's __get__ or from the object's __dict__. -- nosy: +eric.snow ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20864 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20864] getattr does not work well with descriptor
Eric Snow added the comment: You may get unexpected behavior when you have a descriptor on a class that also has __getattr__ defined. See issue #1615. However, I don't think that applies here. As far as I can tell, everything is working the way it should. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20864 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
Mark Lawrence added the comment: There is no plan, other than the BDFL asking for a survey of what is happening with code that relies on this in the real world. FTR I'm completely against this change. I see no reason to change something that's been in use for maybe nine years and does what it's documented to do, based on somebody's expectations, failure to read the documents and buggy code. To me it would be a nail in the coffin of Python's very conservative, and to me extremely proper, view of maintaining backward compatibility. -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13936 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
Donald Stufft added the comment: To be specific, Guido said that if this 3.0 or 3.1 he'd be all for changing it, and the only question in his mind is how safe it is change. And that his intuition is that it's a nuisance feature and few people have actually relied on it and that he'd be OK with fixing (and breaking) it in 3.5, perhaps after a thorough search for how often the feature is actually relied on and how legitimate those uses are. (See the full response at https://mail.python.org/pipermail/python-ideas/2014-March/026785.html) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13936 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18678] Wrong struct members name for spwd module
R. David Murray added the comment: Revisiting this with fresh eyes, I no longer think this was a typo, and I think we shouldn't have changed it and should change it back (but keep the 'p' names as aliases for those who expect the man page names to be valid). My logic is: 'sp_namp' is so named because it is a C char *pointer* to the password. But Python doesn't have pointers in the C sense, so in the python object there is no pointer/non-pointer distinction between sp_namp, sp_pwdp, and all of the rest of the fields. Thus the original decision to drop the 'p', which makes the names easier to type and more consistent with the other field names, there being no pointer distinction in python. But I do like having the 'p' aliases, as I said above, because someone familiar with the C struct might use them automatically, and since this is a thin wrapper around the C API, we ought to support the C names, I think. And besides, its too late now to remove them ;) So, I'm reopening this because I'd like to revert the docs, remove the deprecation, and document the 'p' versions as aliases. -- stage: committed/rejected - needs patch status: closed - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18678 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10197] subprocess.getoutput fails on win32
Roundup Robot added the comment: New changeset 34df43c9c74a by R David Murray in branch '3.3': #10197: Update get[status]output versionchanged with actual version. http://hg.python.org/cpython/rev/34df43c9c74a New changeset ee277b383d33 by R David Murray in branch 'default': #10197: Update get[status]output versionchanged with actual version. http://hg.python.org/cpython/rev/ee277b383d33 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10197 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1097797] Encoding for Code Page 273 used by EBCDIC Germany Austria
R. David Murray added the comment: In changeset d843a1caba78 (I screwed up the issue number in the commit), I added aliases according to http://lists.w3.org/Archives/Public/ietf-charsets/2002JulSep/0153.html plus what appears to be the conventional alias of just the number, and added it to the codecs docs, making a wild guess based on the issue title that the Language is German. -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1097797 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7171] Add inet_ntop and inet_pton support for Windows
Roundup Robot added the comment: New changeset f82145a516f0 by R David Murray in branch 'default': whatsnew: inet_pton/inet_ntop support windows (#7171). http://hg.python.org/cpython/rev/f82145a516f0 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7171 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13936] RFE: change bool(datetime.time(0, 0, 0)) to evaluate as True
Nick Coghlan added the comment: Mark, we kinda proved we're willing to break backwards compatibility in the name of improving usability when we embarked down the path of creating Python 3 and an associated transition plan from Python 2, rather than just continuing to develop Python 2. Compared to some of the backwards compatibility breaks within the Python 2 series that were handled using the normal deprecating cycle (removing string exceptions, anyone?), this one would be truly trivial. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13936 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20864] getattr does not work well with descriptor
Nick Coghlan added the comment: Indeed, since None is a potentially valid attribute value, the required API for a descriptor to indicate no such attribute in __get__ is to throw AttributeError. -- nosy: +ncoghlan resolution: - invalid stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20864 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20145] unittest.assert*Regex functions should verify that expected_regex has a valid type
Kamilla added the comment: Just to be sure, the check must be implemented inside the assertRaisesRegex method, right? -- nosy: +kamie ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20145 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
