Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Small typo, conveyed to Crys_ in irc.
--
nosy: +barry
resolution: -> accepted
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
I don't see enough progress on this issue, and I'm not going to hold up
3.0rc2 for it, so I'm deferring.
--
nosy: +barry
priority: release blocker -> deferred blocker
__
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
This seems like a corner case to me. We should fix it before the final
release, but I don't think it's worth holding up 3.0rc2 for it. Deferring.
--
priority: release blocker -&g
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
This is really done, so closing.
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
New submission from Barry A. Warsaw <[EMAIL PROTECTED]>:
The Python 3.0 documentation is broken. This is blocking the 3.0rc2
release.
I'm too tired right now to figure out what the base problem is.
This was during the ".../release.py --export 3.0rc2" build phase.
pdflate
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Sorry, but this is still not fixed:
tnow using/cmdline Exception occurred:
File
"/private/tmp/py3k/dist/Python-3.0rc2/Doc/tools/docutils/parsers/rst/states.py",
line 2055, in run_directive
% (type_name, i, result[i])
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
r67136 is a workaround found by Christian. We'll go with this for the
3.9rc2 release and make this a deferred blocker for a proper fix for the
next rc.
--
priority: release blocker -> deferred blocker
res
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Raising to deferred blocker. This will definitely block 3.0rc3.
--
nosy: +barry
priority: high -> deferred 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:
After consultation with MvL and Crys_ on irc, we've agreed that this
should be fixed someday but it's a pathological case that shouldn't hold
up the release. I'm lowering to critical because I don't think i
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
This example works though, and it also works in earlier Pythons.
from email.header import Header
def main():
# coding: utf8
ADDRESS = '[EMAIL PROTECTED]'
from email.mime.text import MIMEText
msg = MIMEText(
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
I'm rejecting the patch because the old way of making this work still
works in Python 3.0. Any larger changes to the API need to be made in
the context of redesigning the email package to be byte/str aware.
--
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
patch applied; r67299
--
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
I'm okay with the roundtrip not being supported. One thing I don't
quite understand is in the third test, where you're using "w+" mode and
testing f.buffer.mode and f.buffer.raw.mode is "r+"
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
r67300 (with after the fact whitespace normalization of
Lib/tests/test_io.py)
--
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 20, 2008, at 5:07 PM, STINNER Victor wrote:
> STINNER Victor <[EMAIL PROTECTED]> added the comment:
>
>> I'm rejecting the patch because the old way of makin
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
status: closed -> open
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4362>
___
__
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]>:
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3741>
___
___
Python-bugs-list mailing list
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:
Deferring until 3.0 final is out.
--
nosy: +barry
priority: release blocker -> deferred blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Guido... ping?
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2306>
___
___
Python
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Jesse, please apply so we can close this issue.
--
nosy: +barry
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
I agree with MvL and MAL. We can't change Python, so this is a
documentation issue. I'm lowering the priority so it doesn't block the
release.
--
nosy: +barry
priority: releas
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Since this is a Python 2.5.3 issue, I'm lowering to deferred blocker
until after 3.0 and 2.6.1 are released.
--
nosy: +barry
priority: release blocker -> deferred blocker
___
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Martin, the patch looks okay to me. I vote for applying it.
--
nosy: +barry
resolution: -> accepted
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Lowering priority since this is not a Python 3.0 or 2.6.1 issue.
--
nosy: +barry
priority: release blocker -> deferred blocker
___
Python tracker <[EMAIL PROTECTED]>
<http
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Go for it Martin.
--
resolution: -> accepted
versions: +Python 2.6, Python 3.0
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Guido, ETA? I think this will be one of the last things before we can
tag the tree for release.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Jesse, does this affect Python 3.0? If not, then I will lower the
priority and release 2.6.1 without it (there's always 2.6.2 :).
If so, then we need to know if 1) it's really a release blocker; 2) what
the ETA on a fix i
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
This looks like it only affects printing exceptions with implicit
chaining when the exception propagates to the top level. (Maybe it also
affects the traceback module?)
In that case, I agree with Antoine. Let's fix
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
I don't much like the
lock is True
lock is False
idioms much, but I don' thave a better suggestion, and it would be nice
to fix this for the releases.
--
resolution: -> accepted
___
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
I've changed my mind based on the API change. This should be discussed
on the mailing list and deferred until 2.6.2 at least.
--
resolution: accepted ->
___
Python tracker <
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
For 2.6.1, yes you can fix the comments if you can do it now :)
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
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 thought we had fixed that :(
--
priority: -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Actually, it turns out that the doc build process leaves a few more pyc
turds now. I've updated release.py to remove them, though the script
really should complain loudly if it ever finds pycs in the distribution.
That'
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Withdrawn
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Barry A. Warsaw <[EMAIL PROTECTED]> added the comment:
Wait, should Doc/tools/sphinxext be included in the source tarball or
not? I thought it was a documentation build artifact. If so, then we
need to clean out the pycs it contains in a different way.
In any case, the 3.0 tarballs
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: critical -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
priority: high -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:
--
priority: high -> release blocker
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Barry A. Warsaw :
--
priority: high -> release blocker
___
Python tracker
<http://bugs.python.org/issue4580>
___
___
Python-bugs-list mailing list
Un
New submission from Peter A Silva :
tough% cat toy.py
from ctypes import *
class foo(Structure):
_fields_ = [ ( "bar", c_char_p ) ]
foofoo = foo()
babar = create_string_buffer(32)
foofoo.bar = babar
tough% python toy.py
Traceback (most recent call last):
File "toy.p
Barry A. Warsaw added the comment:
This isn't a bug in Python, since it does the right thing by aliasing
'utf8' with 'utf-8'. If this is incompatible with external mail tools,
then you should use 'utf-8' instead, but I don't think
Barry A. Warsaw added the comment:
I think we should update the documentation to mention these exceptions.
___
Python tracker
<http://bugs.python.org/issue1440
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue47022>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue47061>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue47153>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
I personally don't think we need to change this. C and Python are different,
and the PEP 7 rules have been in place for ages.
+Guido
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/is
New submission from D. A. Pellegrino :
The unittest documentation makes reference to a potential parallelization
feature:
"Note that shared fixtures do not play well with [potential] features like test
parallelization and they break test isolation. They should be used with care.&quo
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue34690>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue38010>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue38014>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
See also this ticket:
https://gitlab.com/python-devs/importlib_resources/issues/58
We've basically agreed that you should be able to load resources from
subdirectories that aren't packages. It turns out to be not a simple change in
importlib
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue38208>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue38289>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Barry A. Warsaw :
test_py_compile fails on macOS Catalina beta (19A573a)
==
ERROR: test_relative_path (test.test_py_compile.PyCompileTestsWithSourceEpoch
Barry A. Warsaw added the comment:
+1 Serhiy.
--
___
Python tracker
<https://bugs.python.org/issue38249>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue38605>
___
___
Python-bugs-list mailing list
Unsubscribe:
cale settings.
I had added locale.getdefaultlocale() to give applications a chance
to determine the locale setting defined by the process environment
*without* calling setlocale(LC_ALL, '') and causing problems
in other threads. I used the X11 database for locale encodings,
which was the cl
eeds to return what the lib C currently
>> knows and uses as encoding.
>
> This is locale.get_current_locale_encoding(). I would like to put "current"
> in the name, because there is a lot of confusion between
> get_current_locale_encoding() encoding and locale.getp
On 19.03.2021 12:05, STINNER Victor wrote:
> I'm not sure what to do with locale.getdefaultlocale(). Should we deprecate
> it? I never used this function. How is it used? For which purpose?
>
> I undertand that in 2000, locale.getdefaultlocale() was interesting to avoid
> calling setlocale(LC_CTY
ogic and not add encoding details which are
specific to Python's view on I/O (sys or io) or the file system (os).
Hopefully, in a few years, we can get rid of all this and standardize
on UTF-8 everywhere.
--
Marc-Andre Lemburg
eGenix.com
___
dows
or gives wrong results. Is that incorrect ?
If it does work, getencoding() could just be a shim over
nl_langinfo(CODESET) on all platforms.
--
Marc-Andre Lemburg
eGenix.com
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
gs :-) So this is unnecessary as well.
>
> The problem is that there are two different "locale encodings", what I call:
>
> * "current locale encoding": nl_langinfo(CODESET) in short
> * "Python locale encoding": "UTF-8" in some cases, nl_langi
UTF-8 mode.
Please address UTF-8 mode explicitly in open() or elsewhere. The locale
module is about the state of the lib C, not what Python enforces via
options in its own I/O layers.
As mentioned, both should ideally be synchronized, though, so
UTF-8 mode in Python should trigger setting a UTF-8 enc
Change by Christopher A. Chavez :
--
nosy: +chrstphrchvz
___
Python tracker
<https://bugs.python.org/issue43511>
___
___
Python-bugs-list mailing list
Unsub
On 31.03.2021 11:30, STINNER Victor wrote:
>
> To me, it sounds really weird to accept an encoding when a file is opened in
> binary mode. open(filename, "rb", encoding="locale") looks like a bug.
Same here.
If encoding is used as an argument and then not used,
Barry A. Warsaw added the comment:
I'd still like to. I'm also happy to review any PRs if someone beats me to it.
--
___
Python tracker
<https://bugs.python.o
Barry A. Warsaw added the comment:
@jaraco beat me to it. PRs approved!
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue43817>
___
___
Python-bugs-list mailing list
Unsubscribe:
On 04.05.2021 22:07, Steve Dower wrote:
>
> Perhaps what I'm suggesting here is that I don't see any reason for "sudo pip
> install ..." into a distro-installed Python to ever need to work, and would
> be quite happy for it to just fail miserably every time (whic
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue40280>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
+1 for removal
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue44498>
___
___
Python-bugs-list mailin
Change by Barry A. Warsaw :
--
pull_requests: +25459
pull_request: https://github.com/python/cpython/pull/26882
___
Python tracker
<https://bugs.python.org/issue44
Barry A. Warsaw added the comment:
New changeset 8488b85c6397fe58f17fc00e047044c959ac0b04 by Barry Warsaw in
branch 'main':
bpo-44498: Issue a deprecation warning on asynchat, asyncore and smtpd import
(#26882)
https://github.com/python/cpyt
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue44246>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue43945>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue33025>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Barry A. Warsaw :
As discussed with Jason, importlib.metadata will be made non-provisional in
3.10. I have a PR in the works for this.
--
assignee: barry
components: Documentation
messages: 397344
nosy: barry, jaraco
priority: normal
severity: normal
status: open
Change by Barry A. Warsaw :
--
keywords: +patch
pull_requests: +25649
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/27101
___
Python tracker
<https://bugs.python.org/issu
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue44616>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
New changeset f6954cdfc50060a54318fb2aea4d80408381243a by Barry Warsaw in
branch 'main':
bpo-44613: Make importlib.metadata non-provisional (#27101)
https://github.com/python/cpython/commit/f6954cdfc50060a54318fb2aea4d80
Barry A. Warsaw added the comment:
New changeset 7223ce3b3f50ec8a825e317437ea0359b6ad6856 by Miss Islington (bot)
in branch '3.10':
bpo-44613: Make importlib.metadata non-provisional (GH-27101) (#27106)
https://github.com/python/cpython/commit/7223ce3b3f50ec8a825e317437ea03
Change by Barry A. Warsaw :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Barry A. Warsaw added the comment:
Jason, I think the question you raise re: accelerated deprecation, is probably
a RM or SC question. I'll nosy in Pablo and see if he has a strong opinion.
--
nosy: +pablogsal
___
Python tracker
&
Barry A. Warsaw added the comment:
Pablo, this is triggered by my bug report here:
https://github.com/nedbat/coveragepy/issues/1187
I tested this again today with the 3.10 git head and still got the coverage
misses. Happy to try any other combinations
Barry A. Warsaw added the comment:
I just retested my test case (see the coveragepy link below) with Python 3.10
git head and coveragepy git head, and I'm still seeing the misses only in
Python 3.10:
-- coverage: platform darwin, python 3.10.0-beta-4 ---
Barry A. Warsaw added the comment:
Thanks Ned. Seems you might be right. I thought I'd done a clean test, but in
any event, I just pulled 3.10 head and verified that it's producing 100%
coverage. Thanks all for the fix!
--
resolution: -> fixed
status: o
New submission from Barry A. Warsaw :
In the PEP 467 discussion, I proposed being able to use
>>> (65).to_bytes()
b'A'
IOW, adding default arguments for the `length` and `byteorder` arguments to
`int.to_bytes()`
https://mail.python.org/archives/list/python-...
Change by Barry A. Warsaw :
--
keywords: +patch
pull_requests: +26685
pull_request: https://github.com/python/cpython/pull/28265
___
Python tracker
<https://bugs.python.org/issue45
801 - 900 of 2560 matches
Mail list logo