Barry A. Warsaw added the comment:
r86837
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue10520>
___
___
Barry A. Warsaw added the comment:
+0 for Amaury's suggestion in msg122792. Who wants to write that patch? I'd
happily review it.
--
___
Python tracker
<http://bugs.python.o
Changes by Barry A. Warsaw :
--
title: Add --disable-abi-flags option to `configure` -> Add --soabi option to
`configure`
___
Python tracker
<http://bugs.python.org/issu
Barry A. Warsaw 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 and distr
Barry A. Warsaw 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 app
Barry A. Warsaw 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 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 b
Barry A. Warsaw added the comment:
I'm okay classifying this as a security bug that should be fixed in the 2.6
tree.
--
___
Python tracker
<http://bugs.python.org/i
Barry A. Warsaw 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
<http://bugs.python.org/issue6
Barry A. Warsaw 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 tracker
Barry A. Warsaw added the comment:
Please include your ./configure command too
--
___
Python tracker
<http://bugs.python.org/issue10687>
___
___
Python-bug
Changes by Barry A. Warsaw :
--
assignee: -> barry
___
Python tracker
<http://bugs.python.org/issue10687>
___
___
Python-bugs-list mailing list
Unsubscri
Barry A. Warsaw 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 ed
Barry A. Warsaw added the comment:
Thanks for testing it! r87213
--
___
Python tracker
<http://bugs.python.org/issue10687>
___
___
Python-bugs-list mailin
Changes by Barry A. Warsaw :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue10687>
___
___
Python-bugs-list
Barry A. Warsaw 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 to test your
Barry A. Warsaw 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...@examp
Barry A. Warsaw 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 the most
Barry A. Warsaw 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
<http://bugs.python.
Barry A. Warsaw 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
Barry A. Warsaw 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. To me,
Barry A. Warsaw 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 enou
Barry A. Warsaw added the comment:
Please ignore, testing roundup.
--
___
Python tracker
<http://bugs.python.org/issue10214>
___
___
Python-bugs-list mailin
Barry A. Warsaw 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 like this d
Changes by Barry A. Warsaw :
--
assignee: tarek -> barry
___
Python tracker
<http://bugs.python.org/issue11171>
___
___
Python-bugs-list mailing list
Unsubscri
Barry A. Warsaw 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
Barry A. Warsaw 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 ->
New submission from Barry A. Warsaw <[EMAIL PROTECTED]>:
As reported by Matthias Klose, the 3.0a5 tarball contains an extra py3k
ssubdir with the whole source included again. He says a4 was okay.
Check the release scripts before 3.0b1.
--
assignee: barry
components: Instal
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
This is a huge thread and I don't have time to look at the entire patch.
However, it seems like the main purpose of the proxy class is to work
around a basic deficiency in Python. Now, if this is a purposeful
omissions (i.e.
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
priority: release blocker -> critical
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pyth
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
This is a bug and not a new feature, so it could go in after beta. I'm
knocking it down to a critical.
--
nosy: +barry
priority: release blocker -> critical
___
Python tracker <
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
priority: critical -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Thanks for the pronouncement Guido. We will not let this issue hold up
the beta releases.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
resolution: -> accepted
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2997>
___
__
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
This is a bug, not a new feature so it's not release critical for the
first alphas.
--
nosy: +barry
priority: release blocker -> critical
___
Python tracker <[EMAIL
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
This is a bug that can be fixed after beta, so I'm knocking it back to
critical for beta 1.
--
priority: release blocker -> critical
___
Python tracker <[EMAIL PROTECTED]>
<
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Perhaps collections.namedtuple() can be used with a custom subclass?
In any case, it's not worth holding up the first beta for this. We can
fix it after beta. Knocking this down to critical.
--
nosy: +barry
priori
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
We've got what we've got for the first betas.
--
nosy: +barry
priority: release blocker -> critical
___
Python tracker <[EMAIL PROTECTED]>
<http
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
This didn't get done for the betas, but we're still going to release.
Knocking it down to critical.
--
nosy: +barry
priority: release blocker -> critical
___
Python tracke
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
This didn't get done for the first beta. Please try to do it asap after
the beta releases.
--
nosy: +barry
priority: release blocker -> critical
___
Python tracker <[EMAIL
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Reviewed and applied to Python 3.0 in r64161. The patch did not apply
cleanly for 2.6. I'm going to bump this down to critical for the first
betas. Humberto, can you back port it to Python 2.6?
--
nosy: +barry
priori
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
This patch works for me in Python 3.0. It's basically Humberto's patch
with the two failing tests fixed.
Added file: http://bugs.python.org/file10597/applied_mimetools.patch
___
Python
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file10597/applied_mimetools.patch
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Actually, try this one.
Added file: http://bugs.python.org/file10598/applied_mimetools.patch
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
r64164 in Python 3.0. This doesn't apply cleanly to Python 2.6; could
someone please back port it?
--
priority: release blocker -> critical
___
Python tracker <[EMAIL
New submission from Barry A. Warsaw <[EMAIL PROTECTED]>:
For me, test_multiprocessing hangs consistently on OS X 10.5.3. It
passes just fine on Ubuntu 8.04.
--
components: Library (Lib)
messages: 68053
nosy: barry
priority: release blocker
severity: normal
status: open
New submission from Barry A. Warsaw <[EMAIL PROTECTED]>:
Subject says it all. None of the 3.0 buildbots are passing.
--
components: Build
messages: 68054
nosy: barry
priority: release blocker
severity: normal
status: open
title: All 3.0 buildbots are red
versions: Pyth
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 12, 2008, at 8:57 AM, Benjamin Peterson wrote:
> Benjamin Peterson <[EMAIL PROTECTED]> added the comment:
>
> On Wed, Jun 11, 2008 at 11:09 PM, Barry A. Warsa
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 12, 2008, at 9:02 AM, Benjamin Peterson wrote:
> It passes for me on Leopard. Can you post the test running in verbose
> mode so we can see where it hangs?
It never ha
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 12, 2008, at 4:36 PM, Humberto Diogenes wrote:
> Humberto Diogenes <[EMAIL PROTECTED]> added the comment:
>
> [msg68060]
>>> Why does it need to be in
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
I'm going to knock this one down to critical since it's working for me
now on OS X and buildbot looks green. We can address any additional
patches after the beta release.
--
priority: release blo
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
There are green buildbots now so I'm releasing beta 1.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http:/
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
There are green buildbots now so I'm releasing beta 1.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
This must have been a packaging snafu for 3.0a5. The candidate 3.0b1
tarball looks fine.
--
resolution: -> invalid
status: open -> closed
___
Python tracker <[EMAIL PR
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
I'm pretty convinced that this stuff is broken and needs serious
attention. Unfortunately, I won't have time to address the email
package before 2.6 and 3.0 get released. My current work lives at
bzr+ssh://[EMAIL PROTECT
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
nosy: +barry
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue648658>
___
__
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
I would really like to get this in by beta2, but it's not quite enough
to hold up the release. Please try to get this cleaned up and committed
by July 16 for beta 2.
--
nosy: +barry
priority: release blocker -> de
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
I think we'll defer this as a blocker. It would be good to get 2to3
working right for the betas, but I don't think it should hold up beta2.
--
nosy: +barry
priority: release blocker -&g
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
What's the plan to fix this? I'm not going to hold up beta2 for this.
--
nosy: +barry
priority: release blocker -> deferred blocker
___
Python tracker <[EMAIL PROTECTED]>
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 15, 2008, at 8:10 PM, Nick Edds wrote:
> Nick Edds <[EMAIL PROTECTED]> added the comment:
>
> I've got it finished, I just need to write some tests for it. I
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Sadly _multiprocessing apparently doesn't even build on my Ubuntu 8.04
machine and it still hangs on my 10.5 machine.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Something's very strange. The first make after configure fails to build
_multiprocessing, but a subsequent make succeeds. I'll see if I can
capture the compilation error message.
__
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Here's the 'make' output. What's strange is that moving
_multiprocessing{_failed,}.so, the import works just fine.
building '_multiprocessing' extension
creating
build/temp.linux-i686-3.0/home/ba
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Not blocking beta 2 because there's not enough time for the fix, but
this will definitely block beta 3.
--
nosy: +barry
priority: release blocker -> deferred blocker
___
Python t
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Is anybody working on a patch for this? Nick, I agree with you about
undesirable behavior, however if there is no patch currently under
development, I'm inclined to defer blocking until beta3.
--
n
New submission from Barry A. Warsaw <[EMAIL PROTECTED]>:
_multiprocessing.so has build problems on both OS X 10.5 and Ubuntu
Linux 8.04. It's very strange though because there are no apparent
errors in compilation, however when the build process tries to import
the module, that f
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Er, make that bug 3088
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3375>
___
__
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
dependencies: +test_multiprocessing hangs intermittently on POSIX platforms
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
On Jul 16, 2008, at 9:12 AM, Jesse Noller wrote:
> I don't want to change the API or any other code before we get the
> change
> in for issue874900 which should fix/resolve issue3088
What
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
py3k. i think the thing to do is to try to figure out why the import is
failing even though the compilation appears to succeed. it's the
suppressed import error that's going to be the clue.
__
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Okay, I have more information, but still no diagnosis. I stuck a
'raise' in the setup.py so that when the ImportError occurs, it doesn't
get swallowed. Instead it stops the build process in its tracks. The
attac
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
priority: deferred blocker -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
priority: deferred blocker -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
priority: deferred blocker -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
priority: deferred blocker -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
priority: deferred blocker -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
priority: deferred blocker -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
I'm not sure it's a good idea. When exit=False, don't you lose the
results? It would be better to return the results, but then that makes
for an ugly API (changing the return value based on an argument is a
general
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
I still think a different method would be better for the no-exit
functionality.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Guido, this is fine for 3.0 and 2.6. As Terry points out, it's not user
visible and it improves reliability. I'm -0 on backporting it to 2.5,
but don't really feel strongly about that.
Go for it!
--
assignee
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Making an existing attribute a property is a nice, API-neutral way to
handle this. Let's call the inconsistency a bug and this a bug fix
so that it's fine to add to 2.6 and 3.0 at this point.
--
nosy: +
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Let's disable it and add it to the release notes. If nobody steps
forward to fix it, we'll just leave it turned off for the final release.
--
nosy: +barry
___
Python tracker &
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Has there been any progress on this? We can fix this after beta 3 if
necessary.
--
nosy: +barry
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Does this affect 2.6 as well? It's hard to tell from the buildbot output.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
While this is a bug, it's not serious enough to hold up the release.
--
priority: release blocker -> high
___
Python tracker <[EMAIL PROTECTED]>
<http://bu
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Can you get this done before beta 3?
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
It's looking pessimistic that this is going to make it by beta 3. If
they can't get in by then, it's too late.
--
nosy: +barry
___
Python tracker <[EMAIL PROTECTED]&
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
I haven't looked at the specific patch, but based on the description of
the behavior, I'm +1 on committing this before beta 3. I'm fine with
leaving the re.ASCII flags in there -- it will be a marker to indicate
per
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Make sure of course that the documentation is updated and a NEWS file
entry is added.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
I don't have time to review the patch, but based on the description, I'm
+1 on landing this before beta 3. I'd like to get the API right for 3.0
and it will be too late to land it after the release candidates start.
--
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Guido's approved it, so please go ahead and add it before beta 3.
--
resolution: -> accepted
___
Python tracker <[EMAIL PROTECTED]>
<http://bu
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
priority: -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3611>
___
_
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
priority: high -> deferred blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
resolution: -> accepted
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3611>
___
__
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3611>
___
__
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
priority: deferred blocker -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
priority: deferred blocker -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
priority: deferred blocker -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
priority: deferred blocker -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
priority: deferred blocker -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
301 - 400 of 2273 matches
Mail list logo