Barry A. Warsaw added the comment:
Note that the headers in the subpart don't matter at all. I'm sure this
is not a problem with MIME parsing, but with line ending issues. It
might be related to mixing line endings, but we know that the email
package has some line endin
Barry A. Warsaw added the comment:
Please, please, please contact the email-sig and help pitch in. For
many reasons I simply haven't had the cycles to work on this and I don't
see that happening any time soon. There are folks willing to work on
the package in the email-sig and I w
Barry A. Warsaw added the comment:
I agree that this is a release blocker for 2.6.3
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue6844>
___
___
Barry A. Warsaw added the comment:
Agreed this should be a release blocker for 2.6.3
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue6
Barry A. Warsaw added the comment:
Agreed this should be a release blocker for 2.6.3
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue6
Barry A. Warsaw added the comment:
I'm willing to leave this as a release blocker for 2.6.3, but I will
re-evaluate it if no progress is made on it.
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/i
Barry A. Warsaw added the comment:
I'll make this a release blocker, but I agree a test would be useful to
have. Let's try to get this in for 2.6.3.
--
nosy: +barry
priority: -> release blocker
___
Python tracker
<http://bugs.pyth
Changes by Barry A. Warsaw :
--
priority: -> release blocker
___
Python tracker
<http://bugs.python.org/issue6990>
___
___
Python-bugs-list mailing list
Un
Barry A. Warsaw added the comment:
Moving to deferred blocker to get this out of the way for 2.6.3
--
nosy: +barry
priority: release blocker -> deferred blocker
___
Python tracker
<http://bugs.python.org/iss
Barry A. Warsaw added the comment:
Since we do not yet have a patch for this, I'm knocking it off the list
for 2.6.3. It seems like an annoying loss of compatibility, but do we
have any reports of it breaking real-world code?
--
nosy: +barry
priority: release blocker -&
Changes by Barry A. Warsaw :
--
assignee: -> pjenvey
keywords: -needs review
resolution: -> accepted
___
Python tracker
<http://bugs.python.org/
Barry A. Warsaw added the comment:
I'd like to accept this for 2.6.3, but I'd also really like a test for
this change. Giampaolo, do you think you could whip up a test for this.
I know it's short notice.
--
___
Python
Barry A. Warsaw added the comment:
Gaimpaolo thanks. Please give it a try.
--
___
Python tracker
<http://bugs.python.org/issue3890>
___
___
Python-bugs-list m
Barry A. Warsaw added the comment:
Please apply this for 2.6.3rc1
--
priority: -> release blocker
resolution: -> accepted
___
Python tracker
<http://bugs.python.org/
Barry A. Warsaw added the comment:
Thanks for the feedback Giampaolo. It sounds like this patch is not yet
fully baked so I'll defer it to Python 2.6.4.
--
priority: release blocker -> high
___
Python tracker
<http://bugs.python.or
Barry A. Warsaw added the comment:
We'll need tests to include it in 2.6.3.
--
priority: high -> release blocker
___
Python tracker
<http://bugs.python.or
Barry A. Warsaw added the comment:
Not gonna make it for 2.6.3rc1
--
priority: release blocker -> high
___
Python tracker
<http://bugs.python.org/iss
Barry A. Warsaw added the comment:
I'm afraid so. Please consider this for landing after 2.6.3 is released.
--
assignee: barry ->
___
Python tracker
<http://bugs.python.or
Barry A. Warsaw added the comment:
yes. rc1 on 6 oct 2009 and final on 18 oct 2009 (tentative)
--
___
Python tracker
<http://bugs.python.org/issue7064>
___
___
Barry A. Warsaw added the comment:
Tarek, please commit this fix before 2.6.4rc1 (i.e. asap :)
--
priority: -> release blocker
resolution: -> accepted
___
Python tracker
<http://bugs.python.org/
Barry A. Warsaw added the comment:
Sorry, 2.6.4 will be solely to remove the brown paper bag of 2.6.3 from
our heads. This can go in 2.6.5 though.
--
___
Python tracker
<http://bugs.python.org/issue5
Barry A. Warsaw added the comment:
Tarek,
Can you please look at this for 2.6.4? We might need another rc and it
would be better to do that sooner rather than later.
Thanks!
--
priority: -> release blocker
status: closed -> open
___
Barry A. Warsaw added the comment:
Please apply this for 2.6.4rc2
--
priority: -> release blocker
resolution: fixed -> accepted
status: pending -> open
___
Python tracker
<http://bugs.python.o
Barry A. Warsaw added the comment:
Agreed this is a release blocker for 2.6.4rc2.
I plan on tagging the release some time Saturday, probably around 1600
UTC. Do you think you can add a test and apply the patch by then?
--
___
Python tracker
<h
Barry A. Warsaw added the comment:
Making this a deferred blocker so as not to clutter 2.6.4 release.
--
nosy: +barry
priority: release blocker -> deferred blocker
___
Python tracker
<http://bugs.python.org/iss
New submission from Barry A. Warsaw :
Try this:
>>> from urllib2 import build_opener
>>> build_opener().handlers
In Python 2.4, you will see ProxyHandler as the first handler, but this
handler is missing from the list in Python 2.5, 2.6, and 2.7, despite this
text in
Barry A. Warsaw added the comment:
This may end up being just a documentation issue. If the environment
has http_proxy set, you do get a ProxyHandler automatically.
>>> import os
>>> os.environ['http_proxy'] = 'localhost'
>>> from urllib2
Barry A. Warsaw added the comment:
Ronald, please apply asap. This is the last thing I'm waiting on before
I tag 2.6.4rc2.
--
resolution: -> accepted
___
Python tracker
<http://bugs.python.or
Barry A. Warsaw added the comment:
I think this is caused by the fix for bug 5890 and isn't a regression.
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/i
Barry A. Warsaw added the comment:
Apparently this affects more than just Boost. lifeless (Robert Collins)
tells me that "__doc__ becoming readonly buggered some code of ours in
bzr too, IIRC".
He thinks it was in pure Python (i.e. not extension code). Does anybody
have a p
Barry A. Warsaw added the comment:
Robert indicated later that this probably did /not/ affect Bazaar.
--
___
Python tracker
<http://bugs.python.org/issue7
Barry A. Warsaw added the comment:
Thanks David, that's what I suspect too (that's its a problem with
extension types). Unless we get more information, I'm not inclined to
hold up the 2.6.4 release for this.
--
___
Python
Barry A. Warsaw added the comment:
After discussion on python-dev, this will not block 2.6.4
--
priority: release blocker -> high
___
Python tracker
<http://bugs.python.org/iss
Changes by Barry A. Warsaw :
--
assignee: -> barry
priority: -> high
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.pytho
New submission from Barry A. Warsaw :
It would be very useful to have an environment variable $PYTHONWARNINGS,
tied to the -W option for silencing various warnings (most importantly,
DeprecationWarnings).
Use case: a test suite running many subprocesses, testing that those
subproc output is
Barry A. Warsaw added the comment:
Robert's patch looks fine to me. My concern is changing this in a point
release (e.g. 2.6.5). I know Guido said he was fine for this going into
2.6 but that was in January 08, before 2.6 final was released in October
08. At this point, the questi
Barry A. Warsaw added the comment:
Guido - agreed! Versions updated.
--
versions: +Python 3.2 -Python 2.6
___
Python tracker
<http://bugs.python.org/issue1
Changes by Barry A. Warsaw :
--
versions: +Python 2.6, Python 2.7, Python 3.2
___
Python tracker
<http://bugs.python.org/issue6895>
___
___
Python-bugs-list mailin
Barry A. Warsaw added the comment:
Emacs navigation command forward-page and backward-page. Python treats
them as whitespace, so what's the problem? :)
--
priority: -> low
resolution: -> wont fix
status: open -> closed
___
Python
Barry A. Warsaw added the comment:
@Lennart: yes, I do think you should add a test for that case. I
haven't yet decided whether this should go into 2.6.
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/i
New submission from Bernard A. Badger :
Change obvious usage error /chosing/choosing/
and script redirection /./>/ typos.
--
assignee: georg.brandl
components: Documentation
files: pep-0374.txt.patch
keywords: patch
messages: 97383
nosy: bab9e9, georg.brandl
severity: normal
sta
Barry A. Warsaw added the comment:
I think it would be useful to have.
___
Python tracker
<http://bugs.python.org/issue1818>
___
___
Python-bugs-list mailing list
Unsub
New submission from Jürgen A. Erhard :
Confirmed to exist in 2.6.1 (r261:67515) and 3.0 (r30:67503). Seems to
have been introduced somewhere in the 2.5 timeline, as 2.4 doesn't show
this bug.
--
components: Library (Lib)
messages: 84060
nosy: jae
severity: normal
status: open
Jürgen A. Erhard added the comment:
Microscopic typo in title fixed (stickler for details, me? ;)
--
title: os.path.ismount take a cross-device symlink for a mountpoint ->
os.path.ismount takes a cross-device symlink for a mountpoint
___
Pyt
Barry A. Warsaw added the comment:
I propose that you only document the getitem header access API. I.e.
the thing that info() gives you can be used to access the message
headers via message['content-type']. That's an API common to both
rfc822.Messages (the ultimat
Barry A. Warsaw added the comment:
So astoundingly, this change has deep implications. The upshot is that
it's difficult to fix this so that headers look nice for e.g. Subject
headers, but so that splitting and wrapping work as expected for e.g.
machine readability of Received headers.
Changes by Barry A. Warsaw :
--
assignee: cjw296 -> barry
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue1645148>
___
___
Pyth
Changes by Barry A. Warsaw :
--
assignee: -> barry
versions: +Python 3.1
___
Python tracker
<http://bugs.python.org/issue5610>
___
___
Python-bugs-list mai
Barry A. Warsaw added the comment:
I think this is a good idea. Does the existing test suite still pass
with this change?
For a long time, email's philosophy was to use native line endings and
never expected mixed eol, and it definitely never expected mixed line
endings, so we'
Barry A. Warsaw added the comment:
I'm -0, but if the tests pass and Matthias wants to commit this to 2.6
and 2.7, it's fine with me.
--
assignee: -> doko
nosy: +barry
resolution: -> accepted
versions: +Python 2.7 -Python 2.5
__
Barry A. Warsaw added the comment:
I'll mark this as a release blocker for 2.6.2 for now, until Mark weighs in.
--
priority: -> release blocker
___
Python tracker
<http://bugs.python.or
Barry A. Warsaw added the comment:
We'll omit this for 2.6.2. Mark, please feel free to apply it once
2.6.2 is released so that it makes it into 2.6.3.
--
priority: release blocker -> high
___
Python tracker
<http://bugs.python.or
Barry A. Warsaw added the comment:
Accepted for 2.6.3.
--
resolution: -> accepted
___
Python tracker
<http://bugs.python.org/issue5724>
___
___
Python-
Barry A. Warsaw added the comment:
The patch looks fine to me, except that it's missing documentation
updates. The feature and names are fine too.
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/i
Barry A. Warsaw added the comment:
On Apr 15, 2009, at 7:43 PM, Robert Collins wrote:
> Robert Collins added the comment:
>
> On Wed, 2009-04-15 at 23:19 +0000, Barry A. Warsaw wrote:
>> Barry A. Warsaw added the comment:
>>
>> The patch looks fine to m
Changes by Barry A. Warsaw :
--
assignee: -> barry
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue3244>
___
___
Python-bugs-list mailing list
Un
Barry A. Warsaw added the comment:
I agree with Antoine.
--
versions: -Python 2.6
___
Python tracker
<http://bugs.python.org/issue5970>
___
___
Python-bug
Barry A. Warsaw added the comment:
Feel free to apply this to 2.6.
--
nosy: +barry
resolution: -> accepted
___
Python tracker
<http://bugs.python.org/iss
Barry A. Warsaw added the comment:
dato: We've started some branches that try to address this, by exposing
both a read-a-buncha-bytes interface and a read-a-string interface.
rdm: As it turns out, yes. There are use cases for reading a string
containing only ascii bytes.
In general, th
Barry A. Warsaw added the comment:
The patch looks pretty good, except that you should not change
test_email.py. It specifically tests the old names, while
test_email_renamed.py tests the new names.
There's no point in fixing Python 2.5 since there won't be another
maintenance relea
Barry A. Warsaw added the comment:
Looks good; feel free to commit.
--
versions: -Python 2.5
___
Python tracker
<http://bugs.python.org/issue2622>
___
___
Pytho
Changes by Barry A. Warsaw :
--
versions: -Python 3.1
___
Python tracker
<http://bugs.python.org/issue8739>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
resolution: -> wont fix
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue2456>
___
___
Python-bugs-
Barry A. Warsaw added the comment:
I cannot reproduce this on Ubuntu 10.04 with current py3k (r81268), even using
the boiled down example given by Antoine. What platform are you on?
--
___
Python tracker
<http://bugs.python.org/issue8
Barry A. Warsaw added the comment:
Thanks, Antoine filled me in on IRC just before my 'net connection went down
for many hours. The good news is that I have a fix for this and will commit it
in a little while.
--
___
Python tracker
Barry A. Warsaw added the comment:
r81290
--
assignee: brett.cannon -> barry
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.o
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue8324>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Barry A. Warsaw :
As described in the thread started here:
http://mail.python.org/pipermail/python-dev/2010-June/100998.html
this bug requests that a new configure option called --with-so-abi-tag be added
to Python 3.2 to support sharing of .so files for different versions
Changes by Barry A. Warsaw :
--
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue9193>
___
___
Python-bugs-list mailing list
Unsubscri
Barry A. Warsaw added the comment:
Attaching patch from live branch living here:
https://code.edge.launchpad.net/~barry/python/sovers
--
Added file: http://bugs.python.org/file17895/preview.diff
___
Python tracker
<http://bugs.python.org/issue9
Barry A. Warsaw added the comment:
Actually, the changes to distutils are not strictly necessary for PEP 3149
implementation (what the PEP-in-progress will be numbered). Once PEP 384 is
implemented, it might be useful, but OTOH there might be a better way to
support that.
In any case
Barry A. Warsaw added the comment:
Updated patch.
--
Added file: http://bugs.python.org/file18125/diff.txt
___
Python tracker
<http://bugs.python.org/issue9
Barry A. Warsaw added the comment:
I'd love it if Windows was also supported, but right now I don't have the
cycles to make and test the changes, or the expertise to understand any related
Windows issues. I've mentioned this in PEP 3149, and I'd happily accept code
Barry A. Warsaw added the comment:
If the changes are to the documentation only, you've confirmed that the docs
build in 2.6.6, and you get the changes in before 2.6.6rc1, then you can go
ahead and commit them. I don't need to review them too closely - I trust you -
but if you wan
New submission from Barry A. Warsaw :
On http://docs.python.org/library/constants.html?highlight=__debug__#__debug__
* Be more explicit that assigments to None and __debug__ are illegal even when
used as attributes. IOW it's not just assignment to the built-in names that
are il
Barry A. Warsaw added the comment:
You have about 5 hours as of this writing to apply the doc patch for Python
2.6.6 rc1 and then it will be too late to get it into Python 2.6.6 (though I
might make an exception for doc-only patches like this, for post rc1).
While I haven't built the do
Changes by Barry A. Warsaw :
--
priority: release blocker -> high
___
Python tracker
<http://bugs.python.org/issue9264>
___
___
Python-bugs-list mailing list
Un
Barry A. Warsaw added the comment:
Georg committed this patch to the 2.6 tree, and besides, this is doesn't seem
like a blocking issue, so I'm kicking 2.6 off the list and knocking the
priority down.
--
priority: release blocker -> high
versions:
Barry A. Warsaw added the comment:
Unless someone can upload a specific patch to review in the next couple of
hours, I'm going to reduce the priority for 2.6.6rc1.
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/i
Barry A. Warsaw added the comment:
Hi Ezio, what's the status on this issue for 2.6.6rc1?
--
___
Python tracker
<http://bugs.python.org/issue7092>
___
___
Barry A. Warsaw added the comment:
I am removing this as a release blocker given all of Ezio's great work to get
the test suite clean with -3. I will leave it up to him to actually close the
issue once the work is complete. It no longer needs to block 2.6.6.
--
priority: re
Barry A. Warsaw added the comment:
This also affects 2.6 but I've only been able to verify it on Debian squeeze
and Ubuntu maverick, both of which are unreleased. On Ubuntu lucid (stable),
this error does not occur. I'm testing Debian stable now...
--
no
Changes by Barry A. Warsaw :
--
versions: +Python 2.6
___
Python tracker
<http://bugs.python.org/issue8433>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
Confirmed on Ubuntu:
Lucid, libncurses5 5.7+20090803-2ubuntu3 passes
Maverick, libncurses5 5.7+20100626-0ubuntu1 fails
--
___
Python tracker
<http://bugs.python.org/issue8
Barry A. Warsaw added the comment:
Confirmed on Debian
squeeze, ncurses 5.7+20100313-2 failed
lenny, ncurses 5.7+20081213-1 succeeds
So clearly something about the curses module is not compatible with the newer
versions of ncurses.
--
___
Python
Barry A. Warsaw added the comment:
Thanks Mark, go ahead and apply this, then close this issue.
--
resolution: -> accepted
___
Python tracker
<http://bugs.python.org/iss
Barry A. Warsaw added the comment:
The latest relevant RFC is 5321:
http://www.faqs.org/rfcs/rfc5321.html
smtplib should be reviewed for compliance with this updated spec.
--
___
Python tracker
<http://bugs.python.org/issue5
Barry A. Warsaw added the comment:
Doko asks in IRC to apply this for 2.6.6. Approved.
--
nosy: +barry
status: pending -> open
___
Python tracker
<http://bugs.python.org/iss
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue28833>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Barry A. Warsaw:
This has finally bugged me enough to file an issue, although I wouldn't be able
to use it until Python 3.7. There's a subtle but documented difference in
str.split() when sep=None:
>>> help(''.split)
Help on built-in function
Barry A. Warsaw added the comment:
On Dec 11, 2016, at 03:32 PM, Serhiy Storchaka wrote:
>Current behavior is consistent with str.count():
>
>len(string.split(sep)) == string.count(sep) + 1
>
>and re.split():
>
>re.split(re.escape(sep), string) == string.split(sep)
Barry A. Warsaw added the comment:
On Dec 11, 2016, at 03:57 PM, Serhiy Storchaka wrote:
>I meant adding boolean argument that changes the behavior when sep is None,
>not when it is not None.
Ah, I understand now, thanks. However, I'm not sure that addresses my
particular use
Barry A. Warsaw added the comment:
I really appreciate all the feedback. Here are some thoughts.
I'm well aware of the filter(), re, and other options, and certainly those can
be made to work, but they're non-obvious. The reason I suggested an
enhancement to str.split() is because
Barry A. Warsaw added the comment:
On Dec 12, 2016, at 04:16 PM, Guido van Rossum wrote:
>So the proposal would be: prune=False -> empty strings stay, prune=True,
>empty strings are dropped, prune=None (default) use True if sep is None,
>False otherwise. Right?
Yep!
>
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue28180>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
On Jan 05, 2017, at 11:11 AM, STINNER Victor wrote:
>I'm sure that many Linux, UNIX and BSD systems don't have the "C.UTF-8"
>locale. For example, HP-UX has "C.utf8" which is not exactly "C.UTF-8".
>
>I'
Barry A. Warsaw added the comment:
On Jan 18, 2017, at 10:56 AM, Jeroen Van Goey wrote:
>sudo add-apt-repository ppa:jonathonf/python-3.6
>sudo apt-get update
>sudo apt-get install python3.6
>
>I made a string, using the new literal string interpolation, but I supplied
>
Barry A. Warsaw added the comment:
On Jan 18, 2017, at 03:57 PM, Matthias Klose wrote:
>I don't think we need a PEP for this
Correct. Generally we don't need PEPs for build system changes.
--
___
Python tracker
<http:/
New submission from Just a Person:
Lately, I have been having trouble using the multiprocessing library's shared
memory on Windows. Often, updating the .value property seems to fail for no
reason. As shown in the attached video, changing ```if __name__ ==
'__main__':``` in
On 01.02.2017 10:14, Christian Heimes wrote:
>
> PEP 456 defines an API to add more hashing algorithms and make the selection
> of hash algorithm a compile time option. We can easily add SipHash-1-3 and
> make it the default algorithm. Vendors then can select between FNV2,
>
2001 - 2100 of 2582 matches
Mail list logo