← Back
Editing: test_failure.cpython-38.pyc
U ��W[ ~ � @ sv d Z ddlmZmZ ddlZddlZddlZddlZddlZddl m Z m Z ddl m Z ddl mZ ddlmZmZ zddlmZ W n ek r� dZY nX d d � ZG d d � d e�ZG d d� de�ZG dd� de�ZG dd� dee�Z G dd� de�Z G dd� de�Z ej dk �r dd� Z nddlm!Z! dd� Z G d d � d e�Z"G d d � d e�Z#G d d!� d!e�Z$G d"d#� d#e�Z%dS )$z6 Test cases for the L{twisted.python.failure} module. � )�division�absolute_importN)�_PY3�NativeStringIO)�reflect)�failure)�SkipTest�SynchronousTestCase)�raiserc O s* z dd W n t j| |�}Y nX |S )z� Make a C{Failure} of a divide-by-zero error. @param args: Any C{*args} are passed to Failure's constructor. @param kwargs: Any C{**kwargs} are passed to Failure's constructor. � r )r �Failure)�args�kwargs�f� r �;/usr/lib/python3/dist-packages/twisted/test/test_failure.py�getDivisionFailure s r c @ s4 e Zd ZdZdd� Zdd� Zdd� Zdd � Zd d � Zd d � Z dd� Z dd� Z dFdd�Z dGdd�Z dHdd�Zdd� Zdd � Zd d � Zd d � Zd!d"� Zd#d$� Zd%d&� Zd'd(� Zd)d*� Zd+d,� Zd-d.� Zd/d0� Zd1d2� Zd3d4� Z d5d6� Z d7d8� Z d9d:� Z d;d<� Z d=d>� Z!d?d@� Z"e#e$dAdB�dBk�r(dCe!_%dCe"_%dDdE� Z&dBS )I� FailureTestsz' Tests for L{failure.Failure}. c C sL z t d��W n t�� }Y nX |�tt�}| �|t� | �|jt � dS )z( Trapping a L{Failure}. ZtestN)�NotImplementedErrorr r �trap� SystemExit� RuntimeError� assertEqual�type)�selfr �errorr r r �test_failAndTrap1 s z FailureTests.test_failAndTrapc C sP t s td��t� }z|�W n t�� }Y nX | �t|jt�}| �||� dS )z� If the wrapped C{Exception} is not a subclass of one of the expected types, L{failure.Failure.trap} raises the wrapped C{Exception}. z� Only expected behaviour on Python 3. @see U{http://twisted.readthedocs.io/en/latest/core/howto/python3.html#twisted-python-failure} N� r r � ValueErrorr r � assertRaisesr � OverflowError�assertIs�r � exceptionr Z untrappedr r r � test_trapRaisesWrappedException> s �z,FailureTests.test_trapRaisesWrappedExceptionc C sR t r td��t� }z|�W n t�� }Y nX | �tj|jt�}| �||� dS )z� If the wrapped C{Exception} is not a subclass of one of the expected types, L{failure.Failure.trap} raises itself. z� Only expected behaviour on Python 2. @see U{http://twisted.readthedocs.io/en/latest/core/howto/python3.html#twisted-python-failure} Nr r" r r r �test_trapRaisesSelfV s �z FailureTests.test_trapRaisesSelfc C s, t � }t�|�}t�|�}| �|j|� dS )z� A L{failure.Failure} constructed from another L{failure.Failure} instance, has its C{value} property set to the value of that L{failure.Failure} instance. N)r r r r! �value�r r# �f1�f2r r r � test_failureValueFromFailurem s z)FailureTests.test_failureValueFromFailurec C sF t � }t�|�}z|�t� W n t�� }Y nX | �|j|� dS )z� A L{failure.Failure} constructed without a C{exc_value} argument, will search for an "original" C{Failure}, and if found, its value will be used as the value for the new C{Failure}. N)r r r r r r! r& r' r r r �!test_failureValueFromFoundFailurey s z.FailureTests.test_failureValueFromFoundFailurec C s | � |�|�d||f � dS )z� Assert that C{s} starts with a particular C{prefix}. @param s: The input string. @type s: C{str} @param prefix: The string that C{s} should start with. @type prefix: C{str} z%r is not the start of %rN)� assertTrue� startswith)r �s�prefixr r r �assertStartsWith� s �z FailureTests.assertStartsWithc C s | � |�|�d||f � dS )z� Assert that C{s} end with a particular C{suffix}. @param s: The input string. @type s: C{str} @param suffix: The string that C{s} should end with. @type suffix: C{str} z%r is not the end of %rN)r, �endswith)r r. �suffixr r r �assertEndsWith� s �zFailureTests.assertEndsWithc C s | � ||� | �||� dS )ac Assert that the C{tb} traceback contains a particular C{prefix} and C{suffix}. @param tb: The traceback string. @type tb: C{str} @param prefix: The string that C{tb} should start with. @type prefix: C{str} @param suffix: The string that C{tb} should end with. @type suffix: C{str} N)r0 r3 )r �tbr/ r2 r r r �assertTracebackFormat� s z"FailureTests.assertTracebackFormatFc C s� |r d}| t |d�}t� }|r(|�� |�|� |�� }d|j|jrJdpLdf }dt�|j �t� |j �|jf }| � |||� dd� |� � D �} |r�| �g | � |r�d } nd } | �| | � n| �g | � | �d |� d S ) a� Assert that L{printDetailedTraceback} produces and prints a detailed traceback. The detailed traceback consists of a header:: *--- Failure #20 --- The body contains the stacktrace:: /twisted/trial/_synctest.py:1180: _run(...) /twisted/python/util.py:1076: runWithWarningsSuppressed(...) --- <exception caught here> --- /twisted/test/test_failure.py:39: getDivisionFailure(...) If C{captureVars} is enabled the body also includes a list of globals and locals:: [ Locals ] exampleLocalVar : 'xyz' ... ( Globals ) ... Or when C{captureVars} is disabled:: [Capture of Locals and Globals disabled (use captureVars=True)] When C{cleanFailure} is enabled references to other objects are removed and replaced with strings. And finally the footer with the L{Failure}'s value:: exceptions.ZeroDivisionError: float division *--- End of Failure #20 --- @param captureVars: Enables L{Failure.captureVars}. @type captureVars: C{bool} @param cleanFailure: Enables L{Failure.cleanFailure}. @type cleanFailure: C{bool} Zxyz�� captureVarsz*--- Failure #%d%s--- z (pickled) � z#%s: %s *--- End of Failure #%s --- c S s g | ]}|� d �r|�qS )z )r- )�.0�liner r r � <listcomp>� s �z8FailureTests.assertDetailedTraceback.<locals>.<listcomp>z exampleLocalVar : "'xyz'"z exampleLocalVar : 'xyz'zA [Capture of Locals and Globals disabled (use captureVars=True)] N)r r � cleanFailureZprintDetailedTraceback�getvalue�countZpickledr �qualr �safe_strr& r5 � splitlines�assertNotEqual�assertInr ) r r7 r< �exampleLocalVarr �outr4 �start�endZ linesWithVarsr: r r r �assertDetailedTraceback� s8 * � � �z$FailureTests.assertDetailedTracebackc C s� |r d}| t � }t� }|�|� |�� }d}|jD ] \}}} } } |d|| |f 7 }q4tt�} | �|d| f dtj |f � |r�| � t � d|�� dS )a` Assert that L{printBriefTraceback} produces and prints a brief traceback. The brief traceback consists of a header:: Traceback: <type 'exceptions.ZeroDivisionError'>: float division The body with the stacktrace:: /twisted/trial/_synctest.py:1180:_run /twisted/python/util.py:1076:runWithWarningsSuppressed And the footer:: --- <exception caught here> --- /twisted/test/test_failure.py:39:getDivisionFailure @param captureVars: Enables L{Failure.captureVars}. @type captureVars: C{bool} Zabcde� z %s:%s:%s zTraceback: %s: z%s %szexampleLocalVar.*abcdeN) r r ZprintBriefTracebackr= �frames�repr�ZeroDivisionErrorr5 r �EXCEPTION_CAUGHT_HERE� assertIsNone�re�search) r r7 rD r rE r4 �stack�method�filename�lineno� localVars� globalVarsZzder r r �assertBriefTraceback s" �z!FailureTests.assertBriefTracebackc C s� |r d}| t |d�}t� }|�|� |�� }d}|jD ]:\}}} } } |d|| |f 7 }|dt�|| ��� f 7 }q8| �|ddt j |t � |j �t �|j�f � |r�| �t�d|�� d S ) a� Assert that L{printTraceback} produces and prints a default traceback. The default traceback consists of a header:: Traceback (most recent call last): The body with traceback:: File "/twisted/trial/_synctest.py", line 1180, in _run runWithWarningsSuppressed(suppress, method) And the footer:: --- <exception caught here> --- File "twisted/test/test_failure.py", line 39, in getDivisionFailure 1/0 exceptions.ZeroDivisionError: float division @param captureVars: Enables L{Failure.captureVars}. @type captureVars: C{bool} Zxyzzyr6 rI z File "%s", line %s, in %s z %s z"Traceback (most recent call last):z %s %s%s: %s zexampleLocalVar.*xyzzyN)r r ZprintTracebackr= rJ � linecache�getline�stripr5 r rM r r? r r@ r& rN rO rP ) r r7 rD r rE r4 rQ rR rS rT rU rV r r r �assertDefaultTraceback/ s2 � � ��z#FailureTests.assertDefaultTracebackc C s | � � dS )zr L{printDetailedTraceback} returns a detailed traceback including the L{Failure}'s count. N�rH �r r r r �test_printDetailedTraceback` s z(FailureTests.test_printDetailedTracebackc C s | � � dS )zC L{printBriefTraceback} returns a brief traceback. N�rW r] r r r �test_printBriefTracebackh s z%FailureTests.test_printBriefTracebackc C s | � � dS )z8 L{printTraceback} returns a traceback. N�r[ r] r r r �test_printTracebacko s z FailureTests.test_printTracebackc C s | j dd� dS )z� L{printDetailedTraceback} captures the locals and globals for its stack frames and adds them to the traceback, when called on a L{Failure} constructed with C{captureVars=True}. Tr6 Nr\ r] r r r �'test_printDetailedTracebackCapturedVarsv s z4FailureTests.test_printDetailedTracebackCapturedVarsc C s | j dd� dS )z� L{printBriefTraceback} returns a brief traceback when called on a L{Failure} constructed with C{captureVars=True}. Local variables on the stack can not be seen in the resulting traceback. Tr6 Nr_ r] r r r �$test_printBriefTracebackCapturedVars s z1FailureTests.test_printBriefTracebackCapturedVarsc C s | j dd� dS )z� L{printTraceback} returns a traceback when called on a L{Failure} constructed with C{captureVars=True}. Local variables on the stack can not be seen in the resulting traceback. Tr6 Nra r] r r r � test_printTracebackCapturedVars� s z,FailureTests.test_printTracebackCapturedVarsc C s | j ddd� dS )z� C{printDetailedTraceback} includes information about local variables on the stack after C{cleanFailure} has been called. T)r7 r< Nr\ r] r r r �.test_printDetailedTracebackCapturedVarsCleaned� s z;FailureTests.test_printDetailedTracebackCapturedVarsCleanedc C s | j ttjdddd� dS )zu L{failure.format_frames} raises a L{ValueError} if the supplied C{detail} level is unknown. NZnoisia��detail)r r r Z format_framesr] r r r � test_invalidFormatFramesDetail� s �z+FailureTests.test_invalidFormatFramesDetailc C s, t � }t�|�}|�t � | �|j|� d S �N)r r r r r r& )r �er r r r �test_ExplictPass� s z FailureTests.test_ExplictPassc C sL z |� � W n2 tk r> t�t�� d �}|d d Y S X td��d S )N� ���z3f.raiseException() didn't raise ZeroDivisionError!?)�raiseExceptionrL � traceback� extract_tb�sys�exc_info� Exception)r r r4 r r r �_getInnermostFrameLine� s �z#FailureTests._getInnermostFrameLinec C s t � }| �|�}| �|d� d S )N�1/0)r ru r )r r Z innerliner r r �test_RaiseExceptionWithTB� s z&FailureTests.test_RaiseExceptionWithTBc C s$ | � ttjd�}| �dt|�� dS )z� Constructing a C{Failure} with a string as its exception value raises a C{TypeError}, as this is no longer supported as of Python 2.6. zono!z$Strings are not supported by FailureN)r � TypeErrorr r rC �str)r �excr r r � test_stringExceptionConstruction� s z-FailureTests.test_stringExceptionConstructionc C s& t jdk rt �� | �tjtj� dS )z� Creating a Failure with no arguments causes it to try to discover the current interpreter exception state. If no such state exists, creating the Failure should raise a synchronous exception. �� r N)rr � version_info� exc_clearr r ZNoCurrentExceptionErrorr r] r r r �test_ConstructionFails� s z#FailureTests.test_ConstructionFailsc C s t � }| �|�� |j� dS )z� If the C{Failure} has not been cleaned, then C{getTracebackObject} returns the traceback object that captured in its constructor. N)r r �getTracebackObjectr4 �r r r r r �test_getTracebackObject� s z$FailureTests.test_getTracebackObjectc C sL z dd W n( t k r4 t�� }tjdd�}Y nX | �|�� |j� dS )zc C{captureVars=True} has no effect on the result of C{getTracebackObject}. r r Tr6 N)rL r r r r� r4 )r Z noVarsFailureZ varsFailurer r r �&test_getTracebackObjectFromCaptureVars� s z3FailureTests.test_getTracebackObjectFromCaptureVarsc C sD t � }t�|�� �}|�� t�|�� �}| �|� | �||� dS )z� If the Failure has been cleaned, then C{getTracebackObject} returns an object that looks the same to L{traceback.extract_tb}. N)r rp rq r� r< �assertIsNotNoner �r r ZexpectedZobservedr r r � test_getTracebackObjectFromClean� s z-FailureTests.test_getTracebackObjectFromCleanc C s> t dd�}t�|�� �}|�� t�|�� �}| �||� dS )z� If the Failure was created with captureVars, then C{getTracebackObject} returns an object that looks the same to L{traceback.extract_tb}. Tr6 N)r rp rq r� r< r r� r r r �.test_getTracebackObjectFromCaptureVarsAndClean� s z;FailureTests.test_getTracebackObjectFromCaptureVarsAndCleanc C s t �td��}| �|�� � dS )a L{failure.Failure}s need not be constructed with traceback objects. If a C{Failure} has no traceback information at all, C{getTracebackObject} just returns None. None is a good value, because traceback.extract_tb(None) -> []. z some errorN)r r rt rN r� r� r r r �'test_getTracebackObjectWithoutTraceback s z4FailureTests.test_getTracebackObjectWithoutTracebackc C sD z dd W n t �� \}}}Y nX t�|�}| �|j|� dS )z� If a L{failure.Failure} is constructed with an exception but no traceback in Python 3, the traceback will be extracted from the exception's C{__traceback__} attribute. r r N)rr rs r r r! r4 )r �klassr# r4 r r r r �$test_tracebackFromExceptionInPython3 s z1FailureTests.test_tracebackFromExceptionInPython3c C s> t � }| �|j� | �|jj|j� |�� | �|jj� dS )z� L{failure.Failure.cleanFailure} sets the C{__traceback__} attribute of the exception to L{None} in Python 3. N)r r� r4 r! r& � __traceback__r< rN r� r r r �*test_cleanFailureRemovesTracebackInPython3 s z7FailureTests.test_cleanFailureRemovesTracebackInPython3r� NzPython 3 only.c C s* t � }t�t�}| �t|�d|f � dS )z� The C{repr} of a L{failure.Failure} shows the type and string representation of the underlying exception. z5<twisted.python.failure.Failure %s: division by zero>N)r r ZfullyQualifiedNamerL r rK )r r ZtypeNamer r r � test_repr+ s ��zFailureTests.test_repr)FF)F)F)'�__name__� __module__� __qualname__�__doc__r r$ r% r* r+ r0 r3 r5 rH rW r[ r^ r` rb rc rd re rf ri rl ru rw r{ r� r� r� r� r� r� r� r� �getattr� BaseException�skipr� r r r r r , sH N - 1 r c @ s e Zd ZdZdd� ZdS )� BrokenStrzb An exception class the instances of which cannot be presented as strings via C{str}. c C s | �d S rj r r] r r r �__str__> s zBrokenStr.__str__N�r� r� r� r� r� r r r r r� 9 s r� c @ s e Zd ZdZdd� ZdS )�BrokenExceptionMetaclassza A metaclass for an exception type which cannot be presented as a string via C{str}. c C s t d��d S )Nz#You cannot make a string out of me.)r r] r r r r� I s z BrokenExceptionMetaclass.__str__Nr� r r r r r� D s r� c @ s e Zd ZdZeZdS )�BrokenExceptionTypeza The aforementioned exception type which cnanot be presented as a string via C{str}. N)r� r� r� r� r� Z __metaclass__r r r r r� N s r� c @ sP e Zd ZdZdd� Zdd� Zdd� Zdd � Zd d � Zd d � Z dd� Z dd� Z dS )�GetTracebackTestsz, Tests for L{Failure.getTraceback}. c C s, t � }t�|�}|j|d�}| �|t� dS )z� Construct a L{Failure} with an exception that raises an exception from its C{__str__} method and then call C{getTraceback} with the specified detail and verify that it returns a string. rg N)r� r r � getTraceback�assertIsInstancery )r rh �xr rp r r r �_brokenValueTest[ s z"GetTracebackTests._brokenValueTestc C s | � d� dS )z� A L{Failure} might wrap an exception with a C{__str__} method which raises an exception. In this case, calling C{getTraceback} on the failure with the C{"brief"} detail does not raise an exception. �briefN�r� r] r r r �test_brokenValueBriefDetailg s z-GetTracebackTests.test_brokenValueBriefDetailc C s | � d� dS )�Y Like test_brokenValueBriefDetail, but for the C{"default"} detail case. �defaultNr� r] r r r � test_brokenValueDefaultDetailp s z/GetTracebackTests.test_brokenValueDefaultDetailc C s | � d� dS )r� �verboseNr� r] r r r � test_brokenValueVerboseDetailw s z/GetTracebackTests.test_brokenValueVerboseDetailc C s( t �t� �}|j|d�}| �|t� dS )z� Construct a L{Failure} with an exception type that raises an exception from its C{__str__} method and then call C{getTraceback} with the specified detail and verify that it returns a string. rg N)r r r� r� r� ry )r rh r rp r r r �_brokenTypeTest~ s z!GetTracebackTests._brokenTypeTestc C s | � d� dS )a A L{Failure} might wrap an exception the type object of which has a C{__str__} method which raises an exception. In this case, calling C{getTraceback} on the failure with the C{"brief"} detail does not raise an exception. r� N�r� r] r r r �test_brokenTypeBriefDetail� s z,GetTracebackTests.test_brokenTypeBriefDetailc C s | � d� dS )zX Like test_brokenTypeBriefDetail, but for the C{"default"} detail case. r� Nr� r] r r r � test_brokenTypeDefaultDetail� s z.GetTracebackTests.test_brokenTypeDefaultDetailc C s | � d� dS )zX Like test_brokenTypeBriefDetail, but for the C{"verbose"} detail case. r� Nr� r] r r r � test_brokenTypeVerboseDetail� s z.GetTracebackTests.test_brokenTypeVerboseDetailN) r� r� r� r� r� r� r� r� r� r� r� r� r r r r r� W s r� c @ sJ e Zd ZdZdd� Zdd� Zdd� Zdd � Zd d � Ze d krFd Z e e_ d S )�FindFailureTestszE Tests for functionality related to L{Failure._findFailure}. c C s8 z dd W n | � tj�� � Y n X | �d� dS )z� Within an exception handler, _findFailure should return L{None} in case no Failure is associated with the current exception. r r z No exception raised from 1/0!?N)rN r r � _findFailure�failr] r r r �$test_findNoFailureInExceptionHandler� s z5FindFailureTests.test_findNoFailureInExceptionHandlerc C s8 t jdk rt �� | �t �� d � | �tj�� � dS )zS Outside of an exception handler, _findFailure should return None. r| rn N)rr r~ r rN rs r r r� r] r r r �test_findNoFailure� s z#FindFailureTests.test_findNoFailurec C sH t � }|�� z |�� W n | �tj�� |� Y n X | �d� dS )z� Within an exception handler, it should be possible to find the original Failure that caused the current exception (if it was caused by raiseException). �)No exception raised from raiseException!?N)r r< ro r r r r� r� r� r r r �test_findFailure� s z!FindFailureTests.test_findFailurec C s~ t � }|�� z |�� W nT t�� }|�� �� }|�� �� }| �||� | �|dd� |dd� � Y n X | � d� dS )ax When a Failure is constructed in the context of an exception handler that is handling an exception raised by raiseException, the new Failure should be chained to that original Failure. Means the new failure should still show the same origin frame, but with different complete stack trace (as not thrown at same place). ���Nr� ) r r< ro r r r� rA rB r r� )r r ZnewFr4 Znew_tbr r r �,test_failureConstructionFindsOriginalFailure� s "z=FindFailureTests.test_failureConstructionFindsOriginalFailurec C sL z t �� W n0 t jk r< t�� }| �|�t j�� Y n X | �d� dS )z� Pyrex and Cython are known to insert fake stack frames so as to give more Python-like tracebacks. These stack frames with empty code objects should not break extraction of the exception. z$No exception raised from extension?!N)r ro ZRaiserExceptionr r r, Zcheckr� r� r r r �/test_failureConstructionWithMungedStackSucceeds� s z@FindFailureTests.test_failureConstructionWithMungedStackSucceedsNz raiser extension not available) r� r� r� r� r� r� r� r� r� r ZskipMsgr� r r r r r� � s r� )r} � c C s | |||fS rj r ��fnrT �name�textr r r �<lambda> � r� �� FrameSummaryc C s t | ||�S rj r� r� r r r r� r� c @ s e Zd ZdZdd� Zdd� ZdS )�FormattableTracebackTestsa Whitebox tests that show that L{failure._Traceback} constructs objects that can be used by L{traceback.extract_tb}. If the objects can be used by L{traceback.extract_tb}, then they can be formatted using L{traceback.format_tb} and friends. c C s8 t �dddi i gg�}| �t�|�tdddd�g� dS )z� A C{_Traceback} object constructed with a single frame should be able to be passed to L{traceback.extract_tb}, and we should get a singleton list containing a (filename, lineno, methodname, line) tuple. rR � filename.py�{ N�r Z _Tracebackr rp rq �_tb�r r4 r r r �test_singleFrame s �z*FormattableTracebackTests.test_singleFramec C sP t �dddi i gdddi i gg�}| �t�|�tdddd�tdddd�g� dS )z� A C{_Traceback} object constructed with multiple frames should be able to be passed to L{traceback.extract_tb}, and we should get a list containing a tuple for each frame. Zmethod1r� r� Zmethod2�� Nr� r� r r r �test_manyFrames s � ��z)FormattableTracebackTests.test_manyFramesN)r� r� r� r� r� r� r r r r r� s r� c @ s e Zd ZdZdd� ZdS )�FrameAttributesTestszq _Frame objects should possess some basic attributes that qualify them as fake python Frame objects. c C s< t �dd�}| �|jt� | �|jt� | �|jt j� dS )z� L{_Frame} instances have the C{f_globals} and C{f_locals} attributes bound to C{dict} instance. They also have the C{f_code} attribute bound to something like a code object. Z dummynameZ dummyfilenameN)r Z_Framer� � f_globals�dict�f_locals�f_codeZ_Code)r �framer r r �test_fakeFrameAttributes3 s z-FrameAttributesTests.test_fakeFrameAttributesN)r� r� r� r� r� r r r r r� - s r� c @ s( e Zd ZdZdd� Zdd� Zdd� ZdS ) �DebugModeTestszF Failure's debug mode should allow jumping into the debugger. c sB t j�tjj� � �fdd�}| �|� g | _| jjt _t�� dS )zK Override pdb.post_mortem so we can make sure it's called. c s �t _� tj_d S rj )�pdb� post_mortemr r �__init__r �ZorigInitr� r r �restoreL s z%DebugModeTests.setUp.<locals>.restoreN) r� r� r r r� Z addCleanup�result�appendZstartDebugMode)r r� r r� r �setUpE s zDebugModeTests.setUpc C sP z dd W n" t �� \}}}t�� }Y nX | �| j|g� | �|j� dS )z~ If startDebugMode() is called, calling Failure() will first call pdb.post_mortem with the traceback. r r N)rr rs r r r r� Z assertFalser7 �r �typrz r4 r r r r �test_regularFailureV s z"DebugModeTests.test_regularFailurec C sT z dd W n& t �� \}}}tjdd�}Y nX | �| j|g� | �|j� dS )zk If startDebugMode() is called, passing captureVars to Failure() will not blow up. r r Tr6 N)rr rs r r r r� r, r7 r� r r r �test_captureVarsd s z DebugModeTests.test_captureVarsN)r� r� r� r� r� r� r� r r r r r� @ s r� c @ s@ e Zd ZdZdd� Zdd� Zdd� Zdd � Zd d � Zd d � Z dS )�ExtendedGeneratorTestszU Tests C{failure.Failure} support for generator features added in Python 2.5 c C s2 z|� |� W n tk r" Y n X | �d� d S )Nz<throwExceptionIntoGenerator should have raised StopIteration)ZthrowExceptionIntoGenerator� StopIterationr� )r r �gr r r �_throwIntoGeneratorx s z*ExtendedGeneratorTests._throwIntoGeneratorc s� g �� �fdd�}|� }t � }t|� � �||� � ��d d t� � ��d d t� � �t��d d �d d d� dS ) zr It should be possible to throw the exception that a Failure represents into a generator. c 3 s4 z d V W n �� t�� � Y n X � �d� d S )Nz$Yield should have yielded exception.)r� rr rs r� r �r Zstuffr r � generator� s zJExtendedGeneratorTests.test_throwExceptionIntoGenerator.<locals>.generatorr r rm rn rv N)r �nextr� r rL r� rp rq �r r� r� r r r� r � test_throwExceptionIntoGenerator� s z7ExtendedGeneratorTests.test_throwExceptionIntoGeneratorc sL t � }|�� g � � �fdd�}|� }t|� ��||� ��� |g� dS )z� Within an exception handler, it should be possible to find the original Failure that caused the current exception (if it was caused by throwExceptionIntoGenerator). c 3 s6 z d V W n � � tj�� � Y n X ��d� d S �Nz No exception sent to generator)r� r r r� r� r �Z foundFailuresr r r r� � s zEExtendedGeneratorTests.test_findFailureInGenerator.<locals>.generatorN)r r< r� r� r )r r r� r� r r� r �test_findFailureInGenerator� s z2ExtendedGeneratorTests.test_findFailureInGeneratorc s� t � }|�� |�� }g � � �fdd�}|� }t|� ��||� ��t� �d� ��||�� � ��� d �� |�� � ��d� d �� � �� d|�� � dS )z� When a Failure is constructed in the context of an exception handler that is handling an exception raised by throwExceptionIntoGenerator, the new Failure should be chained to that original Failure. c 3 s4 z d V W n � � t�� � Y n X ��d� d S r� )r� r r r� r �Z newFailuresr r r r� � s zVExtendedGeneratorTests.test_failureConstructionFindsOriginalFailure.<locals>.generatorr r r� N) r r< r� r� r� r �lenrB rC Z assertNotIn)r r Zoriginal_failure_strr� r� r r� r r� � s zCExtendedGeneratorTests.test_failureConstructionFindsOriginalFailurec s0 � fdd�}|� }t |� t� }� �||� dS )z� When a generator reraises a different exception, L{Failure._findFailure} inside the generator should find the reraised exception rather than original one. c 3 sH z$z d V W n g d Y nX W n � � t�� jt� Y nX d S �Nr )r� r r r& � IndexErrorr r] r r r� � s zJExtendedGeneratorTests.test_ambiguousFailureInGenerator.<locals>.generatorN)r� r r� r� r r] r � test_ambiguousFailureInGenerator� s z7ExtendedGeneratorTests.test_ambiguousFailureInGeneratorc C sP dd� }|� }t |� t� }z| �||� W n | �t�� jt� Y nX dS )z� When a generator reraises a different exception, L{Failure._findFailure} above the generator should find the reraised exception rather than original one. c s s$ z d V W n g d Y nX d S r� r r r r r r� � s zLExtendedGeneratorTests.test_ambiguousFailureFromGenerator.<locals>.generatorN)r� r r� r� r r r& r� r� r r r �"test_ambiguousFailureFromGenerator� s z9ExtendedGeneratorTests.test_ambiguousFailureFromGeneratorN) r� r� r� r� r� r� r� r� r� r� r r r r r� s s #r� )&r� Z __future__r r rO rr rp r� rX Ztwisted.python.compatr r Ztwisted.pythonr r Ztwisted.trial.unittestr r Z twisted.testr � ImportErrorr r rt r� r r� �objectr� r� r� r~ r� r� r� r� r� r� r r r r �<module> sB K] &3
Save File
Cancel