add a note to the documentation that pytest does not mimick nose try to perform "import isolation". Addresses issue268.
This commit is contained in:
		
							parent
							
								
									1dc2a45cb2
								
							
						
					
					
						commit
						4031588811
					
				| 
						 | 
					@ -40,6 +40,13 @@ Unsupported idioms / known issues
 | 
				
			||||||
  plain classes please post `to this issue
 | 
					  plain classes please post `to this issue
 | 
				
			||||||
  <https://bitbucket.org/hpk42/pytest/issue/377/>`_.
 | 
					  <https://bitbucket.org/hpk42/pytest/issue/377/>`_.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					- nose imports test modules with the same import path (e.g.
 | 
				
			||||||
 | 
					  ``tests.test_mod``) but different file system paths
 | 
				
			||||||
 | 
					  (e.g. ``tests/test_mode.py`` and ``other/tests/test_mode.py``)
 | 
				
			||||||
 | 
					  by extending sys.path/import semantics.   pytest does not do that
 | 
				
			||||||
 | 
					  but there is discussion in `issue268 <https://bitbucket.org/hpk42/pytest/issue/268>`_ for adding some support.  Note that 
 | 
				
			||||||
 | 
					  `nose2 choose to avoid this sys.path/import hackery <https://nose2.readthedocs.org/en/latest/differences.html#test-discovery-and-loading>`_.
 | 
				
			||||||
 | 
					  
 | 
				
			||||||
- nose-style doctests are not collected and executed correctly,
 | 
					- nose-style doctests are not collected and executed correctly,
 | 
				
			||||||
  also doctest fixtures don't work.
 | 
					  also doctest fixtures don't work.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
		Reference in New Issue