mirror of
				https://github.com/python/cpython.git
				synced 2025-10-31 13:41:24 +00:00 
			
		
		
		
	Add a comment to the csv reader documentation that explains why the
treatment of newlines changed in 2.5. Pulled almost verbatim from a comment by Andrew McNamara in <http://python.org/sf/1465014>.
This commit is contained in:
		
							parent
							
								
									45540b0922
								
							
						
					
					
						commit
						abd51a3585
					
				
					 1 changed files with 11 additions and 0 deletions
				
			
		|  | @ -70,6 +70,17 @@ Parameters'' for details of these parameters. | |||
| 
 | ||||
| All data read are returned as strings.  No automatic data type | ||||
| conversion is performed. | ||||
| 
 | ||||
| \versionchanged[ | ||||
| If literal newlines are important within a field, users need to read their | ||||
| file in a way that preserves the newlines. The behavior before 2.5 would | ||||
| introduce spurious characters into quoted fields, with no way for the user | ||||
| to control that behavior. The previous behavior caused considerable | ||||
| problems, particularly on platforms that did not use the unix line ending | ||||
| conventions, or with files that originated on those platforms - users were | ||||
| finding mysterious newlines where they didn't expect them. | ||||
| ]{2.5} | ||||
| 
 | ||||
| \end{funcdesc} | ||||
| 
 | ||||
| \begin{funcdesc}{writer}{csvfile\optional{, | ||||
|  |  | |||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue
	
	 Skip Montanaro
						Skip Montanaro