mirror of
				https://github.com/python/cpython.git
				synced 2025-10-31 05:31:20 +00:00 
			
		
		
		
	List constraints on xrange() objects.
This commit is contained in:
		
							parent
							
								
									c09cf33658
								
							
						
					
					
						commit
						5fe2c139d5
					
				
					 1 changed files with 14 additions and 8 deletions
				
			
		|  | @ -379,21 +379,27 @@ separating items with commas: \code{[a, b, c]}.  Tuples are | ||||||
| constructed by the comma operator (not within square brackets), with | constructed by the comma operator (not within square brackets), with | ||||||
| or without enclosing parentheses, but an empty tuple must have the | or without enclosing parentheses, but an empty tuple must have the | ||||||
| enclosing parentheses, e.g., \code{a, b, c} or \code{()}.  A single | enclosing parentheses, e.g., \code{a, b, c} or \code{()}.  A single | ||||||
| item tuple must have a trailing comma, e.g., \code{(d,)}.  Buffers are | item tuple must have a trailing comma, e.g., \code{(d,)}. | ||||||
| not directly supported by Python syntax, but can be created by calling the |  | ||||||
| builtin function \function{buffer()}.\bifuncindex{buffer}  XRanges |  | ||||||
| objects are similar to buffers in that there is no specific syntax to |  | ||||||
| create them, but they are created using the \function{xrange()} |  | ||||||
| function.\bifuncindex{xrange} |  | ||||||
| \obindex{sequence} | \obindex{sequence} | ||||||
| \obindex{string} | \obindex{string} | ||||||
| \obindex{Unicode} | \obindex{Unicode} | ||||||
| \obindex{buffer} |  | ||||||
| \obindex{tuple} | \obindex{tuple} | ||||||
| \obindex{list} | \obindex{list} | ||||||
|  | 
 | ||||||
|  | Buffer objects are not directly supported by Python syntax, but can be | ||||||
|  | created by calling the builtin function | ||||||
|  | \function{buffer()}.\bifuncindex{buffer}.  They don't support | ||||||
|  | concatenation or repetition. | ||||||
|  | \obindex{buffer} | ||||||
|  | 
 | ||||||
|  | Xrange objects are similar to buffers in that there is no specific | ||||||
|  | syntax to create them, but they are created using the \function{xrange()} | ||||||
|  | function.\bifuncindex{xrange}  They don't support slicing, | ||||||
|  | concatenation or repetition, and using \code{in}, \code{not in}, | ||||||
|  | \function{min()} or \function{max()} on them is inefficient. | ||||||
| \obindex{xrange} | \obindex{xrange} | ||||||
| 
 | 
 | ||||||
| Sequence types support the following operations.  The \samp{in} and | Most sequence types support the following operations.  The \samp{in} and | ||||||
| \samp{not in} operations have the same priorities as the comparison | \samp{not in} operations have the same priorities as the comparison | ||||||
| operations.  The \samp{+} and \samp{*} operations have the same | operations.  The \samp{+} and \samp{*} operations have the same | ||||||
| priority as the corresponding numeric operations.\footnote{They must | priority as the corresponding numeric operations.\footnote{They must | ||||||
|  |  | ||||||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue
	
	 Guido van Rossum
						Guido van Rossum