| 763a61ca954a1c5a1b56411dd5e57a7d58afff75 |
|
10-Apr-2016 |
Serhiy Storchaka <storchaka@gmail.com> |
Issue #26200: Added Py_SETREF and replaced Py_XSETREF with Py_SETREF
in places where Py_DECREF was used.
/external/python/cpython2/Python/_warnings.c
|
| bc62af1bbe118aa678cb6fa4ecad40f7250b56de |
|
06-Apr-2016 |
Serhiy Storchaka <storchaka@gmail.com> |
Issue #22570: Renamed Py_SETREF to Py_XSETREF.
/external/python/cpython2/Python/_warnings.c
|
| 5951f2300f43d75d344d542e171daed47a0382a6 |
|
24-Dec-2015 |
Serhiy Storchaka <storchaka@gmail.com> |
Issue #20440: Massive replacing unsafe attribute setting code with special
macro Py_SETREF.
/external/python/cpython2/Python/_warnings.c
|
| 0fb88f7c51cca016e6210e8058b5d5d271f79989 |
|
20-Jul-2014 |
Benjamin Peterson <benjamin@python.org> |
correct ref counting of default_action (closes #22017)
/external/python/cpython2/Python/_warnings.c
|
| 4833c98f85c1ec06a7451f56e1bf3b1f9951da0b |
|
05-Jul-2011 |
Benjamin Peterson <benjamin@python.org> |
start out this branch always with filename NULL
/external/python/cpython2/Python/_warnings.c
|
| 9b6c60530b1f6c86f9c3e509a5ccebb2496f0c89 |
|
04-Jul-2011 |
Benjamin Peterson <benjamin@python.org> |
plug refleak
/external/python/cpython2/Python/_warnings.c
|
| 65c153547ba6a41d11d3d04f84bacb5645a54e5e |
|
04-Jul-2011 |
Victor Stinner <victor.stinner@haypocalc.com> |
Issue #12467: warnings: fix a race condition if a warning is emitted at
shutdown, if globals()['__file__'] is None.
/external/python/cpython2/Python/_warnings.c
|
| 24b07bcba350bb86c4d6ca446e1564647a199868 |
|
15-Mar-2011 |
Ezio Melotti <ezio.melotti@gmail.com> |
#11515: fix several typos. Patch by Piotr Kasprzyk.
/external/python/cpython2/Python/_warnings.c
|
| 1994969c15a055d2f9479d3bc10fb6304b2979ed |
|
26-Apr-2010 |
Brett Cannon <bcannon@gmail.com> |
When DeprecationWarning was silenced by default, it also silenced any use of -Q
by default as well. This change fixes that by treating -Q like -3 when it comes
to DeprecationWarning; using it causes the silencing to not occur.
Fixes issue #7319.
/external/python/cpython2/Python/_warnings.c
|
| 0bc77474aa37b1275c06fa806a59c68acc0eabc7 |
|
15-Jan-2010 |
Brett Cannon <bcannon@gmail.com> |
Remove C++/C99-style comments.
/external/python/cpython2/Python/_warnings.c
|
| 3ffa43db4892d3a836c63911c5a13a8be5670fa5 |
|
14-Jan-2010 |
Brett Cannon <bcannon@gmail.com> |
The silencing of DeprecationWarning was not taking -3 into consideration. Since
Py3K warnings are DeprecationWarning by default this was causing -3 to
essentially be a no-op. Now DeprecationWarning is only silenced if -3 is not
used.
Closes issue #7700. Thanks Ezio Melotti and Florent Xicluna for patch help.
/external/python/cpython2/Python/_warnings.c
|
| 6fdd3dcb6a9998dbe7b707d7a3726733cc03681a |
|
10-Jan-2010 |
Brett Cannon <bcannon@gmail.com> |
DeprecationWarning is now silent by default.
This was originally suggested by Guido, discussed on the stdlib-sig mailing
list, and given the OK by Guido directly to me. What this change essentially
means is that Python has taken a policy of silencing warnings that are only
of interest to developers by default. This should prevent users from seeing
warnings which are triggered by an application being run against a new
interpreter before the app developer has a chance to update their code.
Closes issue #7319. Thanks to Antoine Pitrou, Ezio Melotti, and Brian Curtin
for helping with the issue.
/external/python/cpython2/Python/_warnings.c
|
| e78e5d2e515167df8fdf0a551e8333c31c6a1ba3 |
|
17-Jul-2009 |
Hirokazu Yamamoto <ocean-city@m2.ccsnet.ne.jp> |
Issue #6415: Fixed warnings.warn sagfault on bad formatted string.
/external/python/cpython2/Python/_warnings.c
|
| f7f858d1415514cb9a76a5b7da8ee6ccb774e6f4 |
|
09-May-2009 |
Jeffrey Yasskin <jyasskin@gmail.com> |
Issue 5954, PyFrame_GetLineNumber:
Most uses of PyCode_Addr2Line
(http://www.google.com/codesearch?q=PyCode_Addr2Line) are just trying to get
the line number of a specified frame, but there's no way to do that directly.
Forcing people to go through the code object makes them know more about the
guts of the interpreter than they should need.
The remaining uses of PyCode_Addr2Line seem to be getting the line from a
traceback (for example,
http://www.google.com/codesearch/p?hl=en#u_9_nDrchrw/pygame-1.7.1release/src/base.c&q=PyCode_Addr2Line),
which is replaced by the tb_lineno field. So we may be able to deprecate
PyCode_Addr2Line entirely for external use.
/external/python/cpython2/Python/_warnings.c
|
| 15ba4dae5a2b0bd2f06dff586cb469e7b5325209 |
|
01-Apr-2009 |
Brett Cannon <bcannon@gmail.com> |
_warnings was importing itself to get an attribute. That's bad if warnings gets
called in a thread that was spawned by an import itself.
Last part to close #1665206.
/external/python/cpython2/Python/_warnings.c
|
| 6c4cff0f32c574454114d4cff6bd5f6d2870c04d |
|
11-Mar-2009 |
Brett Cannon <bcannon@gmail.com> |
Require implementations for warnings.showwarning() support the 'line' argument.
Was a DeprecationWarning for not supporting it since Python 2.6.
Closes issue #3652.
/external/python/cpython2/Python/_warnings.c
|
| 32a66a0410674c23f00937b6bd5a0c9ea17d7e6b |
|
02-Oct-2008 |
Christian Heimes <christian@cheimes.de> |
Fixed a couple more C99 comments and one occurence of inline.
/external/python/cpython2/Python/_warnings.c
|
| 1eaf0742d877fd9d84d6ed82a04bc33b027e9ad0 |
|
02-Sep-2008 |
Brett Cannon <bcannon@gmail.com> |
Move test.test_support.catch_warning() to the warnings module, rename it
catch_warnings(), and clean up the API.
While expanding the test suite, a bug was found where a warning about the
'line' argument to showwarning() was not letting functions with '*args' go
without a warning.
Closes issue 3602.
Code review by Benjamin Peterson.
/external/python/cpython2/Python/_warnings.c
|
| 2252d11c08643279ffe58e99f6c8d04014079a7f |
|
11-Jul-2008 |
Amaury Forgeot d'Arc <amauryfa@gmail.com> |
#3342: In tracebacks, printed source lines were not indented since r62555.
#3343: Py_DisplaySourceLine should be a private function. Rename it to _Py_DisplaySourceLine.
/external/python/cpython2/Python/_warnings.c
|
| dea1b5653ffd2183c7a4d577a2ca08644dd51248 |
|
27-Jun-2008 |
Brett Cannon <bcannon@gmail.com> |
warnings.warn_explicit() did not have the proper TypeErrors in place to prevent
bus errors or SystemError being raised. As a side effect of fixing this, a bad
DECREF that could be triggered when 'message' and 'category' were both None was
fixed.
Closes issue 3211. Thanks JP Calderone for the bug report.
/external/python/cpython2/Python/_warnings.c
|
| dd96db63f689e2f0d8ae5a1436b3b3395eec7de5 |
|
09-Jun-2008 |
Gregory P. Smith <greg@mad-scientist.com> |
This reverts r63675 based on the discussion in this thread:
http://mail.python.org/pipermail/python-dev/2008-June/079988.html
Python 2.6 should stick with PyString_* in its codebase. The PyBytes_* names
in the spirit of 3.0 are available via a #define only. See the email thread.
/external/python/cpython2/Python/_warnings.c
|
| dacde0d6ae72451ef102aa98ca36b733277d15bb |
|
26-May-2008 |
Benjamin Peterson <benjamin@python.org> |
turn PyErr_WarnPy3k into a macro
/external/python/cpython2/Python/_warnings.c
|
| 593daf545bd9b7e7bcb27b498ecc6f36db9ae395 |
|
26-May-2008 |
Christian Heimes <christian@cheimes.de> |
Renamed PyString to PyBytes
/external/python/cpython2/Python/_warnings.c
|
| 9c5b51541cff55dacb899fb0711e675063ad0e96 |
|
13-May-2008 |
Georg Brandl <georg@python.org> |
Fix a refleak in the _warnings module.
/external/python/cpython2/Python/_warnings.c
|
| d29503291013b7dfd70522e776b0c244aff0a264 |
|
07-May-2008 |
Benjamin Peterson <benjamin@python.org> |
Fix logic error in Python/_warnings.c and add a test to verify
/external/python/cpython2/Python/_warnings.c
|
| e3dcb01bfc6bd14da865b0f28c3c9ad8181ab212 |
|
06-May-2008 |
Brett Cannon <bcannon@gmail.com> |
Fix a bug in the handling of the stacklevel argument in warnings.warn() where
the stack was being unwound by two levels instead of one each time.
/external/python/cpython2/Python/_warnings.c
|
| 8a232cc385343c17d9f615f0aff49fc378bdebae |
|
05-May-2008 |
Brett Cannon <bcannon@gmail.com> |
Add a DeprecationWarning for when warnings.showwarning() is set to a function
that lacks support for the new 'line' argument.
/external/python/cpython2/Python/_warnings.c
|
| 64a4bbeb259026e6bb3e4a8864870b1ed35ffab2 |
|
03-May-2008 |
Brett Cannon <bcannon@gmail.com> |
Fix the C implementation of 'warnings' to infer the filename of the module that
raised an exception properly when __file__ is not set, __name__ == '__main__',
and sys.argv[0] is a false value.
Closes issue2743.
/external/python/cpython2/Python/_warnings.c
|
| ab9cc1b7ad87f4f6d921ce9599aaeb6a1839fe3b |
|
03-May-2008 |
Brett Cannon <bcannon@gmail.com> |
Fix some indentation errors.
/external/python/cpython2/Python/_warnings.c
|
| b457ddaff2094a0ec02176184beb74f600178ed4 |
|
02-May-2008 |
Brett Cannon <bcannon@gmail.com> |
Fix a backwards-compatibility mistake where a new optional argument for
warnings.showwarning() was being used. This broke pre-existing replacements for
the function since they didn't support the extra argument.
Closes issue 2705.
/external/python/cpython2/Python/_warnings.c
|
| a692c4df63a41c42f2ce10a4521136d1440a712d |
|
27-Apr-2008 |
Benjamin Peterson <benjamin@python.org> |
Added PyErr_WarnPy3k function. (issue 2671) I will be converting current Py3k warnings to the use of this function soon.
/external/python/cpython2/Python/_warnings.c
|
| f9e7ebe165215c8eadd16c7988c5d20c0d114cf5 |
|
14-Apr-2008 |
Amaury Forgeot d'Arc <amauryfa@gmail.com> |
Correct a refleak found by "regrtest.py -R:: test_structmembers"
Some other minor updates in _warnings.c:
- make a function static
- rename a shadowing local variable
/external/python/cpython2/Python/_warnings.c
|
| 67153528489efaab1ef1d7bb2a067147c60d3713 |
|
13-Apr-2008 |
Christian Heimes <christian@cheimes.de> |
Use PyString_InternFromString instead of PyString_FromString for static vars
/external/python/cpython2/Python/_warnings.c
|
| e9746890388178bb1e4cdad3c0586bf1862c3727 |
|
13-Apr-2008 |
Brett Cannon <bcannon@gmail.com> |
Re-implement the 'warnings' module in C. This allows for usage of the
'warnings' code in places where it was previously not possible (e.g., the
parser). It could also potentially lead to a speed-up in interpreter start-up
if the C version of the code (_warnings) is imported over the use of the
Python version in key places.
Closes issue #1631171.
/external/python/cpython2/Python/_warnings.c
|