Barry A. Warsaw ba...@python.org added the comment:
I can't reproduce it either any more on Ubuntu 10.10 in either 2.6 or py3k.
--
resolution: - out of date
status: pending - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Barry A. Warsaw ba...@python.org added the comment:
On Nov 21, 2010, at 11:02 PM, Éric Araujo wrote:
I noticed in the output of pydoc that get_makefile_filename does not have a
docstring. I added one in my local copy (“Return the path of the Makefile.”)
and also removed “s” in verbs in other
Changes by Barry A. Warsaw ba...@python.org:
Removed file: http://bugs.python.org/file19564/9807.txt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9807
Barry A. Warsaw ba...@python.org added the comment:
Here's an updated patch which address's Matthias's last concerns.
--
Added file: http://bugs.python.org/file19776/9807.txt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9807
Barry A. Warsaw ba...@python.org added the comment:
So, you must have done a 'make install' or 'make altinstall' to get a build
into /usr/local, right? Without that of course it works fine.
You're probably still right about changing the order so it picks up the local
copy first
Barry A. Warsaw ba...@python.org added the comment:
I'm bumping the status down since this likely won't affect the average user,
only developers who do their own source installs.
--
assignee: - barry
priority: critical - high
___
Python tracker rep
Barry A. Warsaw ba...@python.org added the comment:
r86731
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9807
Barry A. Warsaw ba...@python.org added the comment:
r86734
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10520
Barry A. Warsaw ba...@python.org added the comment:
BTW, I am not sure it's worth backporting this to 3.1 and 2.7. It seems like a
corner case that will not affect most users.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Barry A. Warsaw ba...@python.org added the comment:
r86837
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10520
Barry A. Warsaw ba...@python.org added the comment:
+0 for Amaury's suggestion in msg122792. Who wants to write that patch? I'd
happily review it.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10262
Changes by Barry A. Warsaw ba...@python.org:
--
title: Add --disable-abi-flags option to `configure` - Add --soabi option to
`configure`
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10262
Barry A. Warsaw ba...@python.org added the comment:
grepping the code without the tests doesn't seem that compelling a use case to
me, given that grep and find both provide options to prune directories. I do
think that moving the tests out of the email package will make it harder to
maintain
Barry A. Warsaw ba...@python.org added the comment:
TBH, the fact that this test only runs under sudo is more troublesome. It's
clearly a test that doesn't get run much. E.g. it sneaked through pre-release
testing and doesn't affect the buildbots.
But I agree that this shouldn't be applied
Barry A. Warsaw ba...@python.org added the comment:
Of course, you don't change configure directly, you change configure.in and let
autoconf update the configure (but you already know that I'm sure :).
The patch looks fairly reasonable, though I haven't tried it. One question:
does $SO have
Barry A. Warsaw ba...@python.org added the comment:
On Nov 30, 2010, at 10:12 PM, Amaury Forgeot d'Arc wrote:
The value of get_config_var(SO) is the same as before, something like
.cpython-32.so by default on Linux. (see, I just moved the line
SO=.$SOABI$SO at the bottom of the patch).
Cool
Barry A. Warsaw ba...@python.org added the comment:
I'm okay classifying this as a security bug that should be fixed in the 2.6
tree.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9129
Barry A. Warsaw ba...@python.org added the comment:
I do not see this as a security bug so no patch for 2.6 please. (Comment
requested from IRC).
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6706
Barry A. Warsaw ba...@python.org added the comment:
r87174 moves the creation of the hard link between python-3.2m and python-3.2
from the bininstall target to the altbininstall target.
--
resolution: - fixed
status: open - closed
___
Python
Barry A. Warsaw ba...@python.org added the comment:
Please include your ./configure command too
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10687
Changes by Barry A. Warsaw ba...@python.org:
--
assignee: - barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10687
___
___
Python-bugs-list
Barry A. Warsaw ba...@python.org added the comment:
I've tested the following patch with both ./configure --prefix=/tmp/python and
./configure --without-pymalloc --prefix=/tmp/python. Both seem to work as
expected.
Note that this patch fixes a small drive-by bug I found, and it makes editing
Barry A. Warsaw ba...@python.org added the comment:
Thanks for testing it! r87213
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10687
Changes by Barry A. Warsaw ba...@python.org:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10687
Barry A. Warsaw ba...@python.org added the comment:
Amaury, did you see my suggestion re $SOBASE and $SOEXTRA?
Also, do you think you can write some tests, even if they only run on a single
platform?
I suspect the Makefile.pre.in part of the patch will have to be updated now.
Please be sure
Barry A. Warsaw ba...@python.org added the comment:
On Dec 18, 2010, at 06:31 PM, R. David Murray wrote:
Barry, I've added you as nosy in case you disagree with this fix. The
essential point is that before, parseaddr would turn 'merwok w...@example.com'
into 'merwok...@example.com', and now
Barry A. Warsaw ba...@python.org added the comment:
For Python 3.2, I think adding the version number alone makes sense. Can you
think of any situations where the trailing digits could break something?
For Python 3.2 I'd suggest also adding the build flags to sys.executable. If
you want
Barry A. Warsaw ba...@python.org added the comment:
Peter, please explain exactly how you built Python to trigger this bug. I.e.
include the exact commands and directories you used. I cannot reproduce this
yet.
--
___
Python tracker rep
Barry A. Warsaw ba...@python.org added the comment:
I'm a little uncomfortable with relying on a non-standards track RFC for this
interpretation, and I'm also not sure I'd say that the email package is a
transport agent, but in cases where it's acting on the user's behalf (i.e.
headers
Barry A. Warsaw ba...@python.org added the comment:
I'm inclined not to support backporting to Python 2.6. It seems like a fairly
rare and narrow hole for security problem, because it would require a program
to add the bogus header explicitly, as opposed to getting it after parsing some
data
Barry A. Warsaw ba...@python.org added the comment:
I'm mildly uncomfortable advocating many different new dot directories in $HOME
(e.g. .python2.7 .python3.1 .python3.2). Let's say -0. Also, because of
backward compatibility, I think most configuration files will end up being
similar
Barry A. Warsaw ba...@python.org added the comment:
Please ignore, testing roundup.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10214
Barry A. Warsaw ba...@python.org added the comment:
Hmm. That's problematic. How would that interact with a system Python that is
already looking in __pycache__ for its pyc files? Would it suddenly start
ignoring those and wanting to write them to .pycache?
IIRC we thought about something
Changes by Barry A. Warsaw ba...@python.org:
--
assignee: tarek - barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11171
___
___
Python-bugs
Barry A. Warsaw ba...@python.org added the comment:
The suggested change works for me, both when prefix == exec_prefix and when it
doesn't. All standard tests pass, so the fix should be committed. I'm holding
off on doing that to see whether it's applicable to other versions, though if
3.2
Barry A. Warsaw ba...@python.org added the comment:
Fixed in release27-maint: r88422
I am unable to reproduce in Python 3.1 (which does not have the sysconfig
module) or 3.2 (which uses a different build-flags specific location for its
Makefile).
--
resolution: - fixed
status: open
Barry A. Warsaw ba...@python.org added the comment:
I'd support updating to argparse *if* you write a test suite for full coverage
of the existing cli first. Once that passes, you'll have more confidence in
your port. Modernizing the argument parsing in that case would be a useful
addition
Barry A. Warsaw ba...@python.org added the comment:
On Feb 22, 2011, at 08:15 PM, Xavier Morel wrote:
Barry, do I correctly understand your comment to mean I should write
end-to-end tests of the CLI (until reaching the already tested meat of
smtpd), not just the CLI options parsing?
Given
Barry A. Warsaw ba...@python.org added the comment:
On Feb 25, 2011, at 12:35 AM, Éric Araujo wrote:
Éric Araujo mer...@netwok.org added the comment:
Barry, could you try reproducing with distutils.sysconfig?
I'm not quite sure what you mean, but configuring Python 3.1 with different
--prefix
Barry A. Warsaw ba...@python.org added the comment:
On Feb 25, 2011, at 01:16 PM, Palm Kevin wrote:
I think that this issue needs to be reopened... since it never has been
resolved... I just downloaded the new version of Python 3.2 and tried to
compile, install and use it on Redhat Linux
Barry A. Warsaw added the comment:
I believe this is because string_find_internal() uses an O with
_PyEval_SliceIndex() to convert its start and end arguments, but the
latter function does not accept None. To fix this, you'd have to change
string_find_internal() to do its own argument checking
Barry A. Warsaw added the comment:
facundo, robert and i looked at this patch and it seems okay.
suggestions: document the reference count semantics of
_ParseTupleFinds() and include a definition of that function in a .h
file. since its non-public, maybe find.h is the right place to put
Barry A. Warsaw added the comment:
The change looks good to me, thanks! I made a minor change to your
patch (i.e. .keys() not needed in sorted()), did some whitespace
normalization, and fixed up the --dump output. Otherwise, the patch is
quentin's and I've committed it to the tree.
r59581
Changes by Barry A. Warsaw:
--
components: Documentation
nosy: barry
priority: low
severity: normal
status: open
title: Undocumented urllib functions
versions: Python 2.5
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1722
New submission from Barry A. Warsaw:
urllib.splithost() and .splittype() are included in urllib's __all__ but
are not documented in urllib's module documentation. They are used
quite extensively in the module so they should be documented
__
Tracker [EMAIL
New submission from Barry A. Warsaw:
operator.attrgetter() is neutered because it only accepts a single
attribute name, but it would really be much more useful if it accepted,
and followed a dotted attribute path, e.g.:
sorted(seq, key=operator.attrgetter('person.displayname'))
Of course
Barry A. Warsaw added the comment:
Unfortunately, that already has different, existing (and IMHO less
useful) semantics. :(
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1826
Barry A. Warsaw added the comment:
I don't even mind if you *write* the patch :)
I actually haven't had time yet to hack it up, but I just reached my
threshold of tolerance so I had to at least report the bug. I think
it's always a good idea to review patches before they go in anyway, so
if I
Barry A. Warsaw added the comment:
Hey Guido, can I borrow the keys to the time machine to get this into
Python 2.5.0? :)
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1826
Barry A. Warsaw added the comment:
I'm not /personally/ concerned with the breakage because practicality
beats purity, and I don't want to use lambda because it's slower. I've
never used operator.attrgetter() outside the specific use case of
sorted() and list.sort() so I'd like to make it able
Barry A. Warsaw added the comment:
You're right that this should probably be fixed in the subclass, but you
also have to remember that the parser generally doesn't create subclass
instances. It only creates instances of Message. As long as you can
make it work properly with the parser
Changes by Barry A. Warsaw [EMAIL PROTECTED]:
--
versions: +Python 3.0
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2314
__
___
Python-bugs-list mailing list
New submission from Barry A. Warsaw [EMAIL PROTECTED]:
For the Bazaar experiment http://www.python.org/dev/bazaar,
sysmodule.c needs to be made compatible with Bazaar, for build number
display.
--
assignee: barry
components: Interpreter Core
messages: 64327
nosy: barry
priority: normal
Changes by Barry A. Warsaw ba...@python.org:
--
versions: -Python 3.1
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8739
___
___
Python-bugs-list
Changes by Barry A. Warsaw ba...@python.org:
--
resolution: - wont fix
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2456
Barry A. Warsaw ba...@python.org 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 rep...@bugs.python.org
http
Barry A. Warsaw ba...@python.org 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
Barry A. Warsaw ba...@python.org added the comment:
r81290
--
assignee: brett.cannon - barry
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8727
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8324
___
___
Python-bugs-list mailing
New submission from Barry A. Warsaw ba...@python.org:
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
Changes by Barry A. Warsaw ba...@python.org:
--
stage: - patch review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9193
___
___
Python-bugs-list
Barry A. Warsaw ba...@python.org 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 rep
Barry A. Warsaw ba...@python.org 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
Barry A. Warsaw ba...@python.org added the comment:
Updated patch.
--
Added file: http://bugs.python.org/file18125/diff.txt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9193
Barry A. Warsaw ba...@python.org 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
and PEP
Barry A. Warsaw ba...@python.org 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
New submission from Barry A. Warsaw ba...@python.org:
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
Barry A. Warsaw ba...@python.org 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
Changes by Barry A. Warsaw ba...@python.org:
--
priority: release blocker - high
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9264
___
___
Python
Barry A. Warsaw ba...@python.org 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: -Python 2.6
Barry A. Warsaw ba...@python.org 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 rep...@bugs.python.org
http
Barry A. Warsaw ba...@python.org added the comment:
Hi Ezio, what's the status on this issue for 2.6.6rc1?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7092
Barry A. Warsaw ba...@python.org 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
Barry A. Warsaw ba...@python.org 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...
--
nosy: +barry
Changes by Barry A. Warsaw ba...@python.org:
--
versions: +Python 2.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8433
___
___
Python-bugs-list
Barry A. Warsaw ba...@python.org added the comment:
Confirmed on Ubuntu:
Lucid, libncurses5 5.7+20090803-2ubuntu3 passes
Maverick, libncurses5 5.7+20100626-0ubuntu1 fails
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8433
Barry A. Warsaw ba...@python.org 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
Barry A. Warsaw ba...@python.org added the comment:
Thanks Mark, go ahead and apply this, then close this issue.
--
resolution: - accepted
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5798
Barry A. Warsaw ba...@python.org 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 rep...@bugs.python.org
http
Barry A. Warsaw ba...@python.org added the comment:
Doko asks in IRC to apply this for 2.6.6. Approved.
--
nosy: +barry
status: pending - open
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7567
Barry A. Warsaw ba...@python.org added the comment:
Patch accepted, please apply for 2.6.6.
--
resolution: - accepted
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9543
Changes by Barry A. Warsaw ba...@python.org:
--
priority: normal - release blocker
versions: +Python 2.6 -Python 2.7, Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7467
Barry A. Warsaw ba...@python.org added the comment:
I'm putting this one in the same category as bug 7467. I think these two, plus
the patches which were applied to release26-maint after rc1 (without approval
;) will require an rc2. If that can be worked out schedule-wise, I'll allow
Barry A. Warsaw ba...@python.org added the comment:
The fix for this was applied after 2.6.6rc1, and it wasn't approved by me. Is
it critical for 2.6? Is it a regression since 2.6.5? The way I see it, we
either back this out or release an rc2. There may be other reasons to release
an rc2
Changes by Barry A. Warsaw ba...@python.org:
--
priority: normal - release blocker
status: closed - open
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2944
Barry A. Warsaw ba...@python.org added the comment:
Why was this merged to 2.6 after 2.6.6rc1 without approval?
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1285086
Changes by Barry A. Warsaw ba...@python.org:
--
priority: low - release blocker
status: closed - open
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1285086
Barry A. Warsaw ba...@python.org added the comment:
flox reverted in r83967 for 2.6.6.
--
priority: release blocker -
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1285086
Barry A. Warsaw ba...@python.org added the comment:
I agree w/mvl. Giampaolo, please revert this for 2.6.6.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2944
Barry A. Warsaw ba...@python.org added the comment:
Since the patch only changes a test, and it looks innocent enough (i.e. no
possibility of regression), and it only changes a test that is run with -u all,
I will allow this for 2.6.6.
Mark, please apply your test_curses_getmouse.patch. You
Barry A. Warsaw ba...@python.org added the comment:
After chatting with __ap__ on irc, i'm going to reject this patch for 2.6.6.
--
nosy: +barry
priority: release blocker -
status: open - closed
___
Python tracker rep...@bugs.python.org
http
Barry A. Warsaw ba...@python.org added the comment:
Just to close the loop: thanks for reverting this for 2.6.6!
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2944
Barry A. Warsaw ba...@python.org added the comment:
Thanks guys. I'll allow this in for 2.6.6 if you can commit it before Sunday
8/15. I'd like the buildbots to have plenty of time to turn green before
schedule release on Monday. Please include a NEWS item and close this issue
once it's
Barry A. Warsaw ba...@python.org added the comment:
This is a regression introduced in 2.6.6rc1. After discussion in irc with
merwok, it is agreed that he will revert to pre-2.6.6rc1 behavior and not apply
any fix. It's way too late to be changing behavior in 2.6.6. Folks using
Python 2.6
Barry A. Warsaw ba...@python.org added the comment:
Please upload a patch specifically for 2.6.6 finally so that I can review it
(and test it locally). It *seems* safe enough so if you and I both have a high
confidence it won't regress anything, and it can go in before Monday, then I
might
Barry A. Warsaw ba...@python.org added the comment:
Looks okay to me on *nix. You can check this in as long as test -u all passes
on Windows. Please include a NEWS file entry and close this issue when it's
committed. Thanks!
--
resolution: - accepted
Barry A. Warsaw ba...@python.org added the comment:
The one thing that looks weird to me is VRFY. Since it never actually does
verify the user, should we even claim to support the command? Why not let
subclasses claim support if they want to add
Barry A. Warsaw ba...@python.org added the comment:
Guido has spoken:
http://mail.python.org/pipermail/python-dev/2010-August/103104.html
We'll keep the change for 2.6.6rc2.
--
nosy: +barry
status: open - closed
___
Python tracker rep
Barry A. Warsaw ba...@python.org added the comment:
r84103 in release26-maint
I will let Ronald commit to the other branches. I did this one due to the
timing of 2.6.6 rc 2. Bumping status away from release blocker.
--
priority: release blocker - high
Barry A. Warsaw ba...@python.org added the comment:
I think it's too late to try to get this into 2.6.6. rc2's already been
released, I don't expect/want an rc3, and I'm not comfortable changing this at
this point. Unless you can convince me it's absolutely critical, I won't
approve
1 - 100 of 2236 matches
Mail list logo