Lines Matching full:boundary
108 #GAN 29Mar09 bugs 1555570, 1721862 Confusion at 8K boundary ending with \r:
283 boundary = self._cur.get_boundary()
284 if boundary is None:
286 # defined a boundary. That's a problem which we'll handle by
299 # boundary as well as the end-of-multipart boundary. Don't push
302 separator = '--' + boundary
318 # If we're looking at the end boundary, we're done with
320 # the closing boundary, then we need to initialize the
325 # We saw an inter-part boundary. Were we in the preamble?
329 # to the boundary.
338 # We saw a boundary separating two parts. Consume any
339 # multiple boundary lines that may be following. Our
359 # Because of RFC 2046, the newline preceding the boundary
360 # separator actually belongs to the boundary, not the
388 # We've seen either the EOF or the end boundary. If we're still
389 # capturing the preamble, we never saw the start boundary. Note
402 # If the end boundary ended in a newline, we'll need to make sure
