Re: The right way to 'call' a class attribute inside the same class

On Monday, December 12, 2016 at 4:31:00 PM UTC-5, Gregory Ewing wrote: > Ned Batchelder wrote: > > In C++, you don't have an object of type T until the > > constructor has finished. In Python, you have an object of type T before > > __init__ has been entered. > > That distinction seems a bit

[issue28091] Document PEP 525

Eric Appelt added the comment: Yes - I'll work on the patch tonight. -- ___ Python tracker ___ ___

[issue28923] Nonexisting encoding specified in Tix.py

Terry J. Reedy added the comment: I am a little puzzled as to how a file rename changed the content, but the annotation history seems to show that. Anyway, ... When I load the file in IDLE 2.7, I get a warning. I am a bit surprised as this is not a proper encoding declaration. IDLE's re

[issue28512] PyErr_SyntaxLocationEx() and PyErr_SyntaxLocationObject() always set the offset attribute to None

Berker Peksag added the comment: Hi Serhiy, there are two commented-out lines in https://hg.python.org/cpython/rev/ea1c49ea8136#l3.10 (only in 3.5) +#with self.assertRaises(AssertionError): +#support.check_syntax_error(self, "x=1") -- nosy: +berker.peksag

Re: The right way to 'call' a class attribute inside the same class

Ned Batchelder writes: > Claiming that __init__ isn't a constructor seems overly pedantic to > me. Whereas to me, claiming that ‘Foo.__init__’ is a constructor seems needlessly confusing. * Classes already have a constructor, ‘Foo.__new__’. If we call something else

Re: The right way to 'call' a class attribute inside the same class

On Tue, Dec 13, 2016 at 10:17 AM, Ben Finney wrote: > If the differences didn't matter I would agree that “overly pedantic” is > fair. But those differences trip up newcomers. Thinking of > ‘Foo.__init__’ leads people to wonder where the ‘self’ attribute came > from –

Re: The right way to 'call' a class attribute inside the same class

On Tue, 13 Dec 2016 03:17 am, Chris Angelico wrote: > You could check "foo" in self.__dict__, but I don't know of any > real-world situations where you need to. vars(self) is probably the better way to access self's namespace, rather than directly self.__dict__. Unfortunately vars() doesn't

[issue28933] AC: Accept None as a Py_ssize_t default value

Serhiy Storchaka added the comment: First, it looks weird if the default value affects accepted types. Second, how many use cases for your converter besides the bisect module? -- ___ Python tracker

[issue28933] AC: Accept None as a Py_ssize_t default value

Larry Hastings added the comment: I don't want this change committed to CPython, you can do what you need with a converter so do that. -- ___ Python tracker

[issue28949] Stdlib modules disappear from file system

Jason R. Coombs added the comment: I don't think hard links are involved. I see symlinks in the .tox/python virutalenv, and virtualenv defaults to creating symlinks (https://github.com/pypa/virtualenv/blob/master/virtualenv.py#L565-L570) and falls back to copying files rather than hard

[issue26876] Extend MSVCCompiler class to respect environment variables

Steve Dower added the comment: I'd rather only take the change to _msvccompiler and not the ones that are there for historical interest (a.k.a. backwards compatibility with people who never expect internal implementation details to change). If any tools break because they're using the wrong

Re: Python constructors have particular semantics, and ‘Foo.__init__’ doesn't qualify (was: The right way to 'call' a class attribute inside the same class)

I agree with you, I'll post here the same thing I said in there for another member: On Mon, Dec 12, 2016 at 6:59 PM, Thomas 'PointedEars' Lahn wrote: > > Using the Python official doc

[issue28954] Incorrect EBNF rule of keywords_arguments

New submission from woo yoo: This is the documented rule, which lacks a comma within the last line. keywords_arguments ::= (keyword_item | "**" expression) ("," keyword_item | "**" expression)* The correct form should be: keywords_arguments ::= (keyword_item |

Re: The right way to 'call' a class attribute inside the same class

On Mon, Dec 12, 2016 at 6:59 PM, Thomas 'PointedEars' Lahn wrote: > Using the Python official doc link you provided, it clearly states that `__new__` is the one called to "create a new

[issue28949] Unable to launch Python interpreter

Jason R. Coombs added the comment: Before disabling SIP, I found I could use fs_usage to get some visibility into fs changes: sudo fs_usage -w -f filesys | grep aliases.py To test my understanding of fs_usage, I deleted aliases.py (also confirming that triggers the error). When I did so, I

[issue28944] A lack of line 6

Josh Rosenberg added the comment: You're reusing the same issue for completely different things. Make a separate issue for separate docs issues. -- nosy: +josh.r ___ Python tracker

Re: The right way to 'call' a class attribute inside the same class

On Monday, December 12, 2016 at 6:17:43 PM UTC-5, Ben Finney wrote: > Ned Batchelder writes: > > > Claiming that __init__ isn't a constructor seems overly pedantic to > > me. > > Whereas to me, claiming that ‘Foo.__init__’ is a constructor seems > needlessly confusing. >

[issue28949] Stdlib modules disappear from file system

Ned Deily added the comment: That's sounding better, thanks. Out of curiosity, are there hard links involved? -- ___ Python tracker ___

Re: The right way to 'call' a class attribute inside the same class

On Tue, 13 Dec 2016 07:15 am, Ned Batchelder wrote: > Claiming that __init__ isn't a constructor seems overly pedantic to me. > What's true is that Python's constructors (__init__) are different than > C++ constructors. In C++, you don't have an object of type T until the > constructor has

[issue28949] Stdlib modules disappear from file system

Jason R. Coombs added the comment: I've just encountered what appears to be a different manifestation of the same issue. I unlinked the .tox directory and that rendered importlib broken. $ pwd /Users/jaraco/yg/queso $ rm -R .tox $ python Python 3.6.0rc1 (v3.6.0rc1:29a273eee9a5, Dec 6 2016,

[issue28949] Stdlib modules disappear from file system

Jason R. Coombs added the comment: I've reinstalled Dropbox, downgrading to 15.4.22. I'll see if that helps. -- ___ Python tracker ___

Python constructors have particular semantics, and ‘Foo.__init__’ doesn't qualify (was: The right way to 'call' a class attribute inside the same class)

Chris Angelico writes: > On Tue, Dec 13, 2016 at 10:17 AM, Ben Finney > wrote: > > If the differences didn't matter I would agree that “overly > > pedantic” is fair. But those differences trip up newcomers. Thinking > > of ‘Foo.__init__’ leads

[issue5322] Python 2.6 object.__new__ argument calling autodetection faulty

Matthias Klose added the comment: https://trac.sagemath.org/ticket/22037 reports about another regression. -- nosy: +doko ___ Python tracker ___

[issue28180] sys.getfilesystemencoding() should default to utf-8

Nick Coghlan added the comment: >From CPython's point of view, glibc behaves the same way (i.e. reporting >`ascii` as the preferred encoding for operating system interfaces) regardless >of whether the cause is the locale not being set at all, or due to it being >explicitly set to the legacy

[issue5322] Python 2.6 object.__new__ argument calling autodetection faulty

Changes by Serhiy Storchaka : -- versions: +Python 2.7 ___ Python tracker ___ ___

[issue5322] Python 2.6 object.__new__ argument calling autodetection faulty

Changes by Serhiy Storchaka : -- keywords: -patch stage: patch review -> ___ Python tracker ___

[issue26856] android does not have pwd.getpwall()

Xavier de Gaye added the comment: Patch updated to the current head of the default branch. -- stage: patch review -> commit review Added file: http://bugs.python.org/file45855/pwd_3.patch ___ Python tracker

[issue28180] sys.getfilesystemencoding() should default to utf-8

Jan Niklas Hasse added the comment: https://sourceware.org/glibc/wiki/Proposals/C.UTF-8#Defaults mentions that C.UTF-8 should be glibc's default. This bug report also mentions Python: https://sourceware.org/bugzilla/show_bug.cgi?id=17318 It hasn't been fixed yet, though :/ --

[issue28180] sys.getfilesystemencoding() should default to utf-8

Jan Niklas Hasse added the comment: Actually in a new Docker container, the LANG variable isn't set at all. Defaulting to UTF-8 in that case should be easier to reason about, shouldn't it? -- ___ Python tracker

[issue28764] test_mailbox fails when run as a non-root user on Android API 24

Roundup Robot added the comment: New changeset 51573ef25903 by Xavier de Gaye in branch '3.6': Issue #28764: Fix a test_mailbox failure on Android API 24 when run as a non-root user. https://hg.python.org/cpython/rev/51573ef25903 New changeset 3a451c67008d by Xavier de Gaye in branch

[issue28956] return minimum of modes for a multimodal distribution instead of raising a StatisticsError

New submission from Srikanth Anantharam: return minimum of modes for a multimodal distribution instead of raising a StatisticsError -- components: Library (Lib) messages: 283071 nosy: Srikanth Anantharam priority: normal pull_requests: 3 severity: normal status: open title: return

[issue28957] undefined symbol: PyUnicodeUCS2_FromUnicode when executing any command with pip2.7

New submission from Ramakrishna Kommineni: Hi, I have installed python from source in the directory /home/rkommine/software/python2.7. During installation there are no errors seen. I have added the below environment variables to my bashrc export

[issue26110] Speedup method calls 1.2x

Serhiy Storchaka added the comment: Technically the patch LGTM. But we should find the cause of the regression in some benchmarks. And would be nice to extend the optimization to C functions. In any case this optimization is worth mentioning in What's New. --

Re: The right way to 'call' a class attribute inside the same class

On Tue, Dec 13, 2016 at 4:45 PM, Steven D'Aprano wrote: > I don't understand the point of bringing up Javascript. Ben has already said > that we shouldn't feel the need to mindlessly copy C++ terminology. Is it your > position that we *should* copy Javascript

[issue28955] Not matched behavior of numeric comparison with the documentation

New submission from woo yoo: According to the documentation, which said "Additionally, comparing any number to a not-a-number value will return False. ",the comparison of `float('nan')!= 1`should yield False, while the result is True. Small errors like this in documentation should be

Re: The right way to 'call' a class attribute inside the same class

On Tuesday 13 December 2016 10:23, Chris Angelico wrote: > On Tue, Dec 13, 2016 at 10:17 AM, Ben Finney > wrote: >> If the differences didn't matter I would agree that “overly pedantic” is >> fair. But those differences trip up newcomers. Thinking of >> ‘Foo.__init__’

Re: Method to know if object support being weakreferenced ?

On Tuesday 13 December 2016 15:57, Matthias Bussonnier wrote: [...] > I could of course write a function that try/except and return False/True > depending on the result, but that seem suboptimal as how can I know that the > TypeError does come from not being able to take a weak reference ? And

[issue28091] Document PEP 525

Eric Appelt added the comment: I believe that I addressed all the comments in the previous review (although its always possible I missed something), and have a new patch with the improvements and fixes. I also noticed that in asyncio, loop.shutdown_asyncgens() is a coroutinemethod and fixed

Method to know if object support being weakreferenced ?

Hi all, I was recently had to use weakreferences, using the weakref module, and came across the fact that some object cannot be weakreferenced. If you try to do so you get greated by a TypeError, which is a totally expected and documented behavior. As I tend to prefer the "Look before you

[issue26110] Speedup method calls 1.2x

INADA Naoki added the comment: > Technically the patch LGTM. But we should find the cause of the regression in > some benchmarks. The benchmark is on Sandy Bridge (Core i5 2400) and I didn't use PGO build. perf_event reported branch-miss rate increase at cpickle's save function. I'll rerun

[issue28948] Facing issue while running Python 3.6.0rc1 windows x86-64 web based installer

arpit arora added the comment: Hi Steve, I only installed the mentioned version and if there is any update for the same then i may not be aware of that. Thanks & Regards Arpit Arora -- ___ Python tracker

Nested functions, how do they work (stack related)

I was reading the wiki on 'Call stack' because I wanted to understand what a traceback object was. My C/C++ isn't good enough to deal with raw python source since I have no background in CS. Also, you just can't dive into the python src - it takes a good deal of reading and background.. (the

Re: The right way to 'call' a class attribute inside the same class

On Tuesday 13 December 2016 12:12, Ned Batchelder wrote: > On Monday, December 12, 2016 at 6:17:43 PM UTC-5, Ben Finney wrote: >> Ned Batchelder writes: >> >> > Claiming that __init__ isn't a constructor seems overly pedantic to >> > me. >> >> Whereas to me, claiming

Re: The right way to 'call' a class attribute inside the same class

Ned Batchelder wrote: if a C++ constructor raises an exception, will the corresponding destructor be run, or not? (No, because it never finished making an object of type T.) So it just leaks any memory that's been allocated by the partially-run constructor? -- Greg --

[issue28512] PyErr_SyntaxLocationEx() and PyErr_SyntaxLocationObject() always set the offset attribute to None

Serhiy Storchaka added the comment: Ah, it was a remnants of backporting to 3.5. Commented-out lines are used in 3.6. The line above these lines was used in 3.5. Test is passed with both variants. I commented out the 3.6 variant, but forgot to remove it (or remove old 3.5 variant and keep 3.6

[issue26110] Speedup method calls 1.2x

Changes by INADA Naoki : Added file: http://bugs.python.org/file45866/call_method_5.patch ___ Python tracker ___

[issue20754] Distribution.parse_config_files uses interpolation since Python 3

Jason R. Coombs added the comment: I forget if there was a reason for choosing RawConfigParser over ConfigParaer with interpolation=None. I'd like to know that before choosing the latter. I'd also like to see if appropriate the implementation patched in Setuptools, providing compatibility for

[issue25458] ftplib: command response shift - mismatch

Ivan Pozdeev added the comment: I tried to fix `urllib' and ultimately failed. In a nutshell, handling of the aftermath of an `ntransfercmd' is broken. Since `ntransfercmd'/`transfercmd' returns a socket, handling of an end-of-transmission response is done in independently invoked code - upon

[issue28933] AC: Accept None as a Py_ssize_t default value

Julien Palard added the comment: Hi Larry, Do you mean a new converter in clinic.py like Nullable_Py_ssizze_t, or a converter that I copy/paste every time I need it like http://bugs.python.org/review/28754/patch/19417/76440 ? -- ___ Python tracker

[issue28950] regrtest: -j0 fails the check -j is not allowed together with -T/-l

Changes by Xiang Zhang : -- versions: +Python 2.7 Added file: http://bugs.python.org/file45867/test-command-line-j0-with-test.patch ___ Python tracker

Re: Method to know if object support being weakreferenced ?

Matthias Bussonnier wrote: I search for a method capable of telling me whether an object can be weakreferenced. Objects that can be weakly referenced have a __weakref__ attribute. So you could use hasattr(obj, '__weakref__'). -- Greg -- https://mail.python.org/mailman/listinfo/python-list

[issue28958] Python should return comperhansive error when SSLContext cannot be created

New submission from Ilya Kulakov: When SSLContext cannot be created, python raises an SSLError exception with "failed to allocate SSL context". https://hg.python.org/cpython/file/4def2a2901a5/Modules/_ssl.c#l2260 This is completely useless to debug the error. In fact many errors raised from

IndexError: list index out of range

hi i am begginer in python. I have written a code and given this error: IndexError: list index out of range In my program, I have h=32 bits input. i divide this 32 bits to 4*8 block and every 8-block is n. so n=0:7;(h=int(n/4)) I want to rotate 0 to 7 bits for 2 bits:

[issue28955] Not matched behavior of numeric comparison with the documentation

woo yoo added the comment: Maybe the description should be changed into "all order comparisons of not-a-number and any number will return False" -- ___ Python tracker

[issue5322] Python 2.6 object.__new__ argument calling autodetection faulty

Jeroen Demeyer added the comment: @serhiy.storchaka: yes, changing the order of the base classes fixes the issue with __new__. Also manually assigning __new__ works, like class C(A, B): __new__ = B.__new__ What is broken by this patch is only the auto-detection of which __new__ (really,

[issue28943] Use PyUnicode_MAX_CHAR_VALUE instead of PyUnicode_KIND in some API's short path

Serhiy Storchaka added the comment: PyUnicode_KIND() just extracts three bits from the state word. PyUnicode_MAX_CHAR_VALUE() extracts bits multiple times and does few conditional branching. I think it is much slower that PyUnicode_KIND(). In common case you search ASCII needle or the needle

[issue795081] email.Message param parsing problem II

bpoaugust added the comment: Rather that change unquote to deal with such malformed input, why not just enhance get/set boundary? That would reduce the impact of any changes. Also it should be easier to detect trailing rubbish in the value if you know it is a boundary value. -- nosy:

[issue28945] get_boundary invokes unquote twice

New submission from bpoaugust: get_boundary calls get_param('boundary') which unquotes the value. It then calls utils.collapse_rfc2231_value which also calls unquote. This causes problems for boundaries that have two sets of quotes. For example, I have seen the following in the wild:

[issue28935] distutils use ConfigParser in Python 3.x and fails to parse setup.cfg with percent sign

Berker Peksag added the comment: Thanks for the report! This looks similar to issue 20754. Disabling string interpolation would break existing code (but probably just Python 3 only code) Would using %% instead of % be possible for you? (3.3 and 3.4 are in security-fix-only mode so I removed

[issue28943] Use PyUnicode_MAX_CHAR_VALUE instead of PyUnicode_KIND in some API's short path

New submission from Xiang Zhang: Some unicode APIs like PyUnicode_Contains get a short path comparing kinds. But this get a problem cannot apply to ascii and latin1. PyUnicode_MAX_CHAR_VALUE could be used instead to make the short path also apply to ascii and latin1. This skill is already

[issue28942] await expressions in f-strings

Changes by Serhiy Storchaka : -- nosy: +eric.smith ___ Python tracker ___ ___

[issue28942] await expressions in f-strings

Adam Gregory added the comment: Replicated in CPython 3.6.0rc1 -- ___ Python tracker ___ ___ Python-bugs-list

[issue28180] sys.getfilesystemencoding() should default to utf-8

Nick Coghlan added the comment: The challenge that arises in being selective about this is that "sys.getfilesystemencoding()" is actually a misnomer, and some of the things we use it for (like decoding command line arguments and environment variables) necessarily happen *really* early in the

[issue28943] Use PyUnicode_MAX_CHAR_VALUE instead of PyUnicode_KIND in some API's short path

Changes by Xiang Zhang : -- resolution: -> rejected ___ Python tracker ___ ___

[issue5322] Python 2.6 object.__new__ argument calling autodetection faulty

Serhiy Storchaka added the comment: Thank you Jeroen. It looks to me that all problems can be resolved by reordering base classes and making Cython not generating trivial __new__. But that is possible only in new Python version. In maintained versions we should keep the old behavior for

[issue28180] sys.getfilesystemencoding() should default to utf-8

Marc-Andre Lemburg added the comment: If we just restrict this to the file system encoding (and not the whole LANG setting), how about: * default the file system encoding to 'utf-8' and use the surrogate escape handler as default error handler * add a PYTHONFSENCODING env var to set the

[issue21368] Check for systemd locale on startup if current locale is set to POSIX

Nick Coghlan added the comment: While this is still a problem I'm interested in solving, I no longer think reading the systemd locale config file would be a good way to address it. See issue 28180 for a more recent discussion of some other alternatives. -- resolution: -> rejected

[issue28944] A lack of comma within EBNF rule of keywords_arguments

New submission from woo yoo: This is the documented rule, which lacks a comma within the last line. keywords_arguments ::= (keyword_item | "**" expression) ("," keyword_item | "**" expression)* The correct form should be: keywords_arguments ::= (keyword_item |

[issue26683] Questionable terminology for describing what locals() does

Marco Buttu added the comment: Another point in the doc, where the meaning of "free variable" is inconsistent with the ``locals()`` and ``code.co_freevars`` meaning: https://docs.python.org/3/reference/executionmodel.html#interaction-with-dynamic-features --

[issue28874] test_logging fails and freezes

Whitequill Riclo added the comment: my OS is Ubuntu on Windows 10 . The new Linux subsystem for Windows 10 Linux version 3.4.0-Microsoft (micros...@microsoft.com) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Wed Dec 31 14:42:53 PST 2014

[issue28248] Upgrade installers to OpenSSL 1.0.2j

S Safihre added the comment: >From the changelog I interpreted this to mean that Python would now use >OpenSSL 1.0.2j on macOS for it's ssl module. But this is not the case? On a fresh macOS Sierra VM I get: Python 2.7.13rc1 (v2.7.13rc1:4d6fd49eeb14, Dec 3 2016, 13:01:23) [GCC 4.2.1 (Apple

[issue28935] distutils use ConfigParser in Python 3.x and fails to parse setup.cfg with percent sign

Jason R. Coombs added the comment: This looks to be another manifestation of issue20120 and is a duplicate of issue20754. -- resolution: -> duplicate status: open -> closed ___ Python tracker

[Release] Pyo 0.8.1 (Python DSP library)

Hello all, I'm glad to announce the release of pyo 0.8.1, available for python 2.7 and 3.5. Pyo is a Python module written in C to help real-time digital signal processing script creation. It is available for Windows, macOS and linux. It is released under the LGPL 3 license. For more info,

[issue28947] Facing issue while running Python 3.6.0rc1 windows x86-64 web based installer

New submission from arpit arora: Hi, Post installing 'Python 3.6.0rc1 windows x86-64 web based installer' on my Windows 7 64 bit system, i am not able to start python. Each time i start it, i get a pop up saying that "the program can't start because 'api-ms-win-crt-runtime-|1-1-0.dll' is

[issue28948] Facing issue while running Python 3.6.0rc1 windows x86-64 web based installer

New submission from arpit arora: Hi, Post installing 'Python 3.6.0rc1 windows x86-64 web based installer' on my Windows 7 64 bit system, i am not able to start python. Each time i start it, i get a pop up saying that "the program can't start because 'api-ms-win-crt-runtime-|1-1-0.dll' is

[issue28946] AttributeError: module 'signal' has no attribute 'SIGALRM'

Changes by Berker Peksag : -- stage: -> resolved ___ Python tracker ___ ___

[issue20754] Distribution.parse_config_files uses interpolation since Python 3

Jason R. Coombs added the comment: Looking more closely now and as a result of the report in issue28935, I see that this issue is another separate manifestation of the issue addressed in issue20120. -- resolution: out of date -> status: closed -> open title: distutils should use

[issue28949] Unable to launch Python interpreter

Jason R. Coombs added the comment: A simple re-install corrected the issue and survived a restart. I suspect one or more components weren't properly upgraded or were corrupted for unrelated reasons. I suspect that it was an environmental issue and not an issue with the package itself.

[issue28942] await expressions in f-strings

Guido van Rossum added the comment: I was going to say "no", but given that "yield" works, I think it is reasonable to allow "await" as well. (And what about "yield from"?) -- ___ Python tracker

[issue28935] distutils use ConfigParser in Python 3.x and fails to parse setup.cfg with percent sign

Axel Haustant added the comment: You're welcome. I understand the backward compatibility point. But I think that the current state is breaking existing code as it's not documented anywhere and it's a side-effect of another change, not something intentionnal. (this is why I submitted this

[issue5322] Python 2.6 object.__new__ argument calling autodetection faulty

Changes by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___

Eventlet 0.20.0 released

Eventlet is a concurrent networking library for Python that allows you to change how you run your code, not how you write it. https://pypi.python.org/pypi/eventlet/0.20.0 Important backward incompatible changes: - removed select.poll(). We never had green poll implementation. If you really

Sphinx 1.5 released

Hi all, I'm very happy to announce the release of Sphinx 1.5-final available on the Python package index at . Sphinx-1.5 includes many updates from 1.4.9 version: * 67 features * 38 incompatible changes * 3 deprecations * 52 fixes of bugs/buglets For the

[issue28946] AttributeError: module 'signal' has no attribute 'SIGALRM'

New submission from dd: When I try to run the example at the very end of the signal documentation page [https://docs.python.org/3/library/signal.html#example] I get the error from the title: AttributeError: module 'signal' has no attribute 'SIGALRM' The same thing happens for SIGINT, which

[ANN] jsonrpclib-pelix 0.2.9

== jsonrpclib-pelix 0.2.9 == jsonrpclib-pelix 0.2.9 has just been released ! What is it? --- This library is an implementation of the JSON-RPC specification, for Python 2.7 and 3.3+. It supports both the original 1.0 specification, as well as the

[issue28948] Facing issue while running Python 3.6.0rc1 windows x86-64 web based installer

Marc-Andre Lemburg added the comment: Please try to install this update from MS: https://support.microsoft.com/en-us/kb/2999226 it includes the missing DLL. -- nosy: +lemburg ___ Python tracker

[issue28946] AttributeError: module 'signal' has no attribute 'SIGALRM'

Chi Hsuan Yen added the comment: Can you import _signal? And what's the output of dir(_signal)? Another possibility is that there's another signal.py in the search path. Could you also paste the output of repr(signal)? By the way, here on Arch Linux, both signal.SIGINT and signal.SIGALRM are

[issue28948] Facing issue while running Python 3.6.0rc1 windows x86-64 web based installer

arpit arora added the comment: Hi Marc, It worked. Thanks a lot :) Regards Arpit Arora -- ___ Python tracker ___

[issue28948] Facing issue while running Python 3.6.0rc1 windows x86-64 web based installer

Steve Dower added the comment: Arpit, could you look in your %TEMP% directory for the Python logs when you originally installed it? There may be some information in those about why the update didn't install properly the first time, and I'd like to fix it. You can just zip up all the logs you

[issue5322] Python 2.6 object.__new__ argument calling autodetection faulty

Jeroen Demeyer added the comment: Wouldn't it be possible to fix assignment of __new__ without breaking backwards compatibility (and then apply the same patch for all Python versions)? I have a feeling that breaking the auto-detection of tp_new is a new bug introduced by this patch and not a

[issue28946] AttributeError: module 'signal' has no attribute 'SIGALRM'

dd added the comment: Yeah, I'm stupid. I named my file signal.py… Sorry for the trouble and thanks for your help! -- resolution: -> not a bug status: open -> closed ___ Python tracker

[issue28949] Unable to launch Python interpreter

New submission from Jason R. Coombs: I recently upgraded Python 3.6.0rc1 over 3.6.0b4. Python would invoke just fine after the update, but following a system restart, I'm experiencing crashes on any invocation of Python. I suspect it's just a bad/corrupted install. I will do more

[issue26936] android: test_socket fails

Xavier de Gaye added the comment: New patch using sys.getandroidapilevel(). getandroidapilevel() is only available in 3.7, so only 3.7 is being fixed. -- stage: commit review -> patch review versions: -Python 3.6 Added file: http://bugs.python.org/file45858/test_socket_3.patch

[issue28919] Simplify `_copy_func_details` in unittest.mock

New submission from Berker Peksag: Thanks for the patch. I only did a quick review, but it looks good to me. -- nosy: +berker.peksag, michael.foord stage: -> patch review ___ Python tracker

[issue28949] Unable to launch Python interpreter

Jason R. Coombs added the comment: I thought I was on to something when I found this technique for using dtrace to detect a file deletion: https://blogs.oracle.com/zoneszone/entry/who_keeps_removing_that_file However, I don't seem to have privilege to run it. $ cat trap-aliases-delete #!

[issue28949] Unable to launch Python interpreter

Jason R. Coombs added the comment: Looks like I can [disable SIP](http://internals.exposed/blog/dtrace-vs-sip.html) and dtrace will be viable. -- ___ Python tracker

[issue28923] Nonexisting encoding specified in Tix.py

Changes by Berker Peksag : -- nosy: +serhiy.storchaka, terry.reedy stage: -> patch review type: compile error -> behavior ___ Python tracker

[issue28933] AC: Accept None as a Py_ssize_t default value

Julien Palard added the comment: > for just one use case I don't think that using None in a default argument is "one use case", nor a "special case" it's more like a "widly used pattern" that I'd like to make simple to implement (also see http://bugs.python.org/issue28754#msg282891). I'm not

[issue28089] asyncio: Document that TCP_NODELAY is now used by default

Ned Deily added the comment: Yury, look good to you? -- stage: patch review -> commit review versions: +Python 3.7 ___ Python tracker ___

Re: The right way to 'call' a class attribute inside the same class

Ned Batchelder wrote: In C++, you don't have an object of type T until the constructor has finished. In Python, you have an object of type T before __init__ has been entered. That distinction seems a bit pedantic as well. Inside a C++ constructor you have access to something having all the

  1   2   >