New submission from Devyn Johnson:
I have a suggestion. When Python code is byte-compiled to *.pyo files, what if
byte-compiler were to be made to enhance some of the code. For instance, "if
type(OBJECT) == int:" would be changed to "if isinstance(OBJECT, int):". Python
New submission from Devyn Johnson:
As we all know, Python is sometimes used to computer large numbers and precise
numbers (i.e. doubles) with the help of third-party modules. In my opinion, it
seems that Python may benefit from gaining new data-types such as "longint" (a
"long
New submission from Devyn Johnson:
When creating Python modules via th C-API, it would be wonderful if there were
an easier and more efficient way of creating an "__all__" for the module. In my
opinion, an API function should be made; i.e., something like PyALL("
Devyn Johnson added the comment:
Thanks, @skrah and @haypo . I never thought of it that way. I made "__all__" in
my extensions because "__all__" was used in many Python scripts. Thanks for the
alternative perspective.
--
st
New submission from Devyn Johnson:
When compiling Python C-API extensions with "-Wextra", warnings like
warning: unused parameter ‘self’ [-Wunused-parameter]
appear for code (like below). It seems like a minor issue for a warning to
appear when "PyObject *self, PyObject *ar
Devyn Johnson added the comment:
Thank you and sorry.
--
___
Python tracker
<http://bugs.python.org/issue26179>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Devyn Johnson:
When compiling Python3.5.1 on Ubuntu 15.10 (64-bit), I see three "incompatible
pointer type" warnings (copy-pasted below). I understand that they can be
ignored. However, from my experience with programming (in C STD-2011), "weird
bugs
New submission from Devyn Johnson:
I understand that compile-time warnings can typically be ignored. However, from
my experience with programming (C STD-2011, for instance), "weird bugs",
non-easily-replicable bugs, and odd behaviors disappear when warnings like this
are fix
New submission from Devyn Johnson:
Would it be a good idea to add macros to Python? This would allow developers to
test a condition (such as, "is this code running on Linux?" or "is this Python
version 3.6?"). Then, the compiled bytecode will already contain the needed
