New submission from Ezio Melotti:
__main__.py seems to only be mentioned briefly in a couple of places in the
official docs:
1) https://docs.python.org/3/library/__main__.html
2) https://docs.python.org/3/using/cmdline.html#cmdoption-m
The first link only says:
For a package, the same effect
Ned Deily added the comment:
Serhiy, I'll try making a 3.5.0b3+patch installer build in the same manner as
the 3.5.0b3 installer build. But I may not get to it for several days.
--
___
Python tracker rep...@bugs.python.org
New submission from Sébastien Celles:
Hello,
the package name readme conflicts with Python installed site-packages/README
file on case-insensitive filesystems (Mac OS X).
https://github.com/pypa/readme/issues/26
https://github.com/mgedmin/restview/issues/30
Chris Smowton added the comment:
+1 to the above; suggest this should be rolled back and replaced with a total
message size limit.
--
nosy: +Chris Smowton
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16041
Guido van Rossum added the comment:
I've added the return True from eof_received() to the asyncio repo
(https://github.com/python/asyncio/commit/ce3ad816a2ef9456b4b1c26b99dfc85ea1236811),
but it still needs a unittest and merging into CPython 3.4 and up.
--
Ned Batchelder added the comment:
BTW, the Stack Overflow answer: http://stackoverflow.com/a/4043007
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24632
___
Changes by Robert Collins robe...@robertcollins.net:
--
keywords: +patch
Added file: http://bugs.python.org/file39924/issue24633.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24633
___
Changes by Martin Panter vadmium...@gmail.com:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24629
___
___
Robert Collins added the comment:
So, README is a valid package name. readme conflicting with README on case
insensitive filesystems is a special case, but the general problem remains.
We've no particular reason to use README rather than e.g. README.txt, which
would open with a much more
Chris Smowton added the comment:
I found the same problem retrieving mail from my ISP's (unknown) POP3 server. I
was sent an HTML email as one long 50KB line, which naturally broke everything.
Instead of limiting line length, I suggest you should limit total message body
size, since that's
Serhiy Storchaka added the comment:
In 3.5+ lru_cache() is implemented in C. Is this issue still actual?
--
nosy: +serhiy.storchaka
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21952
___
Ned Deily added the comment:
I agree with IIan's comments you cited in
https://groups.google.com/a/continuum.io/forum/#!topic/anaconda/AGHXzB1sN0I.
Python has been installing the README file in site-packages for a very long
time and there have been case-insensitive file systems for a very
Ronald Oussoren added the comment:
I agree with Robert: renaming the file to README.txt would be a good idea
regardless to enable easily opening the file with a GUI editor and as a bonus
removes any change of conflict with a package name.
The patch looks good to me.
--
Ned Deily added the comment:
I'm +0 on the name change but, again, it wouldn't solve the conflict problem
for potential users of the readme package until 3.6.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24633
Ned Deily added the comment:
(And such a change would only be appropriate in a feature release, as it would
complicate things for existing release installers and downstream distributions,
etc.)
--
stage: - patch review
versions: -Python 3.4, Python 3.5
R. David Murray added the comment:
Could you open a separate bug for the recovery problem, please?
Using a maximum message size would not solve this problem, but it would give
the library user control of when it failed, so it is a good feature request.
--
Changes by Brett Cannon br...@python.org:
--
title: Not a directory:
'//anaconda/lib/python2.7/site-packages/readme/__about__.py' - README file
installed into site-packages conflicts with package named readme
___
Python tracker
Brett Cannon added the comment:
+1 on the file renaming. There really shouldn't be any files we put into
site-packages that don't have a dot or some other symbol that we would never
support as a file name for importing.
--
nosy: +brett.cannon
___
Brad Larsen added the comment:
Both test cases cause segfaults for me:
(1) on 64-bit Python 3.4.3 built from source on Mac OS X
(2) on the system 64-bit Python 3.4.3 from Debian Jessie
I do not see the segfaults with a 64-bit build of the latest sources (cpython
`default` branch at
Brett Cannon added the comment:
There's no patch to review.
--
nosy: +brett.cannon
stage: patch review - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24631
___
Serhiy Storchaka added the comment:
Oh, sorry. Here is it.
--
keywords: +patch
stage: needs patch - patch review
Added file: http://bugs.python.org/file39925/timeit_multiline_setup.patch
___
Python tracker rep...@bugs.python.org
Robert Collins added the comment:
This is a regression in 3.5 vs 3.3 I think. It would have worked with the
initial mock import.
https://github.com/testing-cabal/mock/issues/280
Minimal reproducer case attached (With commentted out bits to switch out the
mock for the rolling backport etc).
New submission from Steve Dower:
Lib/uuid.py includes the following code that runs on import:
import ctypes, ctypes.util
# The uuid_generate_* routines are provided by libuuid on at least
# Linux and FreeBSD, and provided by libc on Mac OS X.
for libname in ['uuid', 'c']:
Steve Dower added the comment:
Patch is against Python 3.5, but uuid.py is identical in all versions and the
change should be applied to all four branches.
--
keywords: +patch
Added file: http://bugs.python.org/file39927/24634_1.patch
___
Python
Changes by Robert Collins robe...@robertcollins.net:
--
nosy: +rbcollins
versions: +Python 3.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18622
___
eryksun added the comment:
This code can cause issues on Windows
What's the issue or issues here? For 2.7, Windows won't be able to find
msvcr90.dll without an activation context, but that's just an
ERROR_MOD_NOT_FOUND OS error. It should be ignored by the try/except block. For
3.4, it
New submission from R. David Murray:
See for example:
http://buildbot.python.org/all/builders/AMD64%20Windows8.1%20Non-Debug%203.x/builds/106
It might be a test order dependency, but see
http://buildbot.python.org/all/builders/x86%20Ubuntu%20Shared%203.x/builds/11931
where the test passed
Robert Collins added the comment:
So unittest.main, the symbol, needs to exist.
What currently references unittest.main, the module, today?
AFAICT its only accessible vis sys.modules['unittest.main'] because of the
shadowing.
--
___
Python tracker
Robert Collins added the comment:
Applying this to 3.4 and up with a test.
Laurent, it would be good to sign the CLA - since your change here is minimal
and Nicola has, I'm just going ahead.
--
___
Python tracker rep...@bugs.python.org
Roundup Robot added the comment:
New changeset 4c8cb603ab42 by Robert Collins in branch '3.4':
- Issue #18622: unittest.mock.mock_open().reset_mock would recurse infinitely.
https://hg.python.org/cpython/rev/4c8cb603ab42
--
nosy: +python-dev
___
Joe Jevnik added the comment:
I updated the docstring
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24379
___
___
Python-bugs-list mailing list
eryksun added the comment:
That would break anyone else who's manually managing their own
activation context around ctypes.
Since this can't be made to work automatically, I prefer your suggestion to
continue checking for uuid.dll. You could just do something like the following:
eryksun added the comment:
Actually, it finds the DLL fine and the DLL terminates the entire
process when it fails to detect an activation context.
OK, in that case it finds msvcr90.dll via PATH. I was only thinking of the DLL
being installed in a subdirectory of the system WinSxS
Robert Collins added the comment:
I think its worth noting that both the original mock_open and the new one are
entirely broken for mocking access to multiple files.
But, the breakage was not deliberate, and as the mock-280 example shows, folk
subclassing a test suite will be surprisingly
Steve Dower added the comment:
For 2.7, Windows won't be able to find msvcr90.dll without an activation
context, but that's just an ERROR_MOD_NOT_FOUND OS error.
Actually, it finds the DLL fine and the DLL terminates the entire process when
it fails to detect an activation context. There's
Changes by Robert Collins robe...@robertcollins.net:
--
keywords: +patch
Added file: http://bugs.python.org/file39928/issue-21750.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21750
Changes by Robert Collins robe...@robertcollins.net:
--
nosy: +rbcollins
versions: +Python 3.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23004
___
Changes by Robert Collins robe...@robertcollins.net:
--
assignee: michael.foord - rbcollins
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18622
___
Changes by Robert Collins robe...@robertcollins.net:
--
assignee: - rbcollins
versions: +Python 3.5, Python 3.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21750
___
Steve Dower added the comment:
ctypes could activate this context before calling LoadLibrary.
That would break anyone else who's manually managing their own activation
context around ctypes. At best we could expose functions to enable Python's
activation context (which I'm willing to help
eryksun added the comment:
windll.python27._Py_ActivateActCtx would suffice
It would instead be ctypes.pythonapi._Py_ActivateActCtx -- if the DLL exported
a function with this name. ctypes.pythonapi is a PyDLL instance that wraps
sys.dllhandle.
I think it would be more useful in general
Roundup Robot added the comment:
New changeset c0ec61cf5a7d by Robert Collins in branch '3.5':
- Issue #18622: unittest.mock.mock_open().reset_mock would recurse infinitely.
https://hg.python.org/cpython/rev/c0ec61cf5a7d
New changeset a4fe32477df6 by Robert Collins in branch 'default':
- Issue
Serhiy Storchaka added the comment:
Likely this crash was fixed by issue24552 patch.
--
nosy: +benjamin.peterson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24630
___
Brett Cannon added the comment:
The modules seem to have existed since at least Python 3.2, so I think a proper
DeprecationWarning is necessary for just one release.
The trick is going to be unittest.main since it seems code in the wild relies
on it at least partially existing and Michael
44 matches
Mail list logo