R. David Murray added the comment:
Well, we have a goal of keeping the stable buildbots green. If something turns
one or more red, it should either be fixed promptly, or the changeset that
turned it red backed out until a fix is ready.
The reason for keeping them green is so we know right
Terry J. Reedy added the comment:
Since the menu argument was the 'opposite' of the stop argument, both in theory
and practice, it was never needed as a parameter/argument. configGUI could have
had the following first line to create it.
menu = NORMAL if stop == DISABLED else DISABLED
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12067
___
___
Python-bugs-list
Geert Jansen added the comment:
Adding small patch (incremental to patch #4) to fix a test failure.
--
Added file: http://bugs.python.org/file36483/ssl-memory-bio-4-incr1.patch
___
Python tracker rep...@bugs.python.org
New submission from Fabian:
The ipaddress module accepts IPv6 addresses if the IPv4 address is formatted as
an octal number, but http://tools.ietf.org/html/rfc3986#section-3.2.2 doesn't
allow leading zeroes in the IPv4 address.
This is the current behaviour (in 3.4.1):
New submission from STINNER Victor:
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%209.0%203.x/builds/7213/steps/test/logs/stdio
building '_decimal' extension
gcc -pthread -fPIC -fno-strict-aliasing -Wsign-compare -g -O0 -Wall
-Wstrict-prototypes -Werror=declaration-after-statement
Ram Rachum added the comment:
I'd definitely consolidate.
First of all, I'd put a few useful numbers in `Executor.__repr__`. Something
like ThreadPoolExecutor(7), 3 workers busy, 0 work items queued. That already
makes to easy to get a general picture of how the executor is doing without
Stefan Krah added the comment:
Yeah, I know -- I have to release libmpdec-2.4.1. The bot is currently testing
the supported configuration that if _decimal fails to build, decimal.py should
be used automatically.
The tests fail due to #22280, otherwise the bot would be green even with the
New submission from STINNER Victor:
While investigation issue #22283, I noticed that when the _decimal is present,
the decimal looses its __all__ attribute. dir(decimal) contains 5 more symbols
than decimal.__all__:
{'ConversionSyntax',
'DecimalTuple',
'DivisionImpossible',
New submission from STINNER Victor:
When Python is built from source, the Modules/ subdirectory is added to
sys.path on UNIX. I don't understand why: it does not contain .py files nor .so
dynamic modules. Dynamic modules are built in
build/lib.linux-x86_64-3.5-pydebug.
A side effect of
Stefan Krah added the comment:
I agree. I plan to fix this as part of #19232. If decimal.py and
_decimal are split properly, these things show up immediately.
--
nosy: +mark.dickinson
___
Python tracker rep...@bugs.python.org
Changes by Stefan Krah stefan-use...@bytereef.org:
--
dependencies: +Speed up _decimal import
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22284
___
STINNER Victor added the comment:
A side effect of this issue is that when the _decimal cannot be build (ex:
#22283), the Python implementation of the decimal cannot be used. Extract of
buildbot test logs related to #22283:
---
Failed to build these modules:
_decimal
(...)
File
STINNER Victor added the comment:
Oh, it looks like I opened a similar issue: #22285 (with a patch).
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22280
___
STINNER Victor added the comment:
See also issue #22280 for the case of the wrong _decimal package.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22285
___
Stefan Krah added the comment:
Ah nice, let's continue with your issue then.
--
resolution: - duplicate
stage: - resolved
status: open - closed
superseder: - The Modules/ directory should not be added to sys.path
___
Python tracker
Martin v. Löwis added the comment:
The motivation for this feature is that modules built as shared libraries
through Modules/Setup end up in Modules, so Modules is added so that they are
found.
I'd like to preserve support for building dynamic extension modules through
Modules/Setup, but
Cristian Consonni added the comment:
Hi David,
at the moment the other parameters used by the open()[1] - 'new' and
'autoraise' - have no direct mapping to other subprocess.Popen(), they are
passed as options to the call for the specific browsers.
(e.g. firefox -new-tab
STINNER Victor added the comment:
A modified version of telco.py (using floats instead of decimals)
runs about 5-6% slower with the change here.
Would it be possible to optimize the pymalloc allocator to reduce this
slow-down?
--
___
Python
A. Libotean added the comment:
Can we close this issue then?
Yes, please. Sorry for the false alarm.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22272
___
Nick Coghlan added the comment:
I wouldn't mind heading in that direction at a later stage. PEP 432 is aimed at
a simpler proposition of breaking things up into two steps:
Step 1: get a functional bytecode compiler and eval loop up and running (only
builtin and frozen modules available) (this
New submission from Nick Coghlan:
In the discussion on issue 18814, Antoine pointed out that in a Python 3 world,
using backslashescape during decoding actually makes sense - it lets you
accurately report arbitrary bytes in the sequence, without needing
surrogateescape or surrogatepass to be
New submission from STINNER Victor:
On UNIX, time.time() currently uses clock_gettime(), but _PyTime_gettimeofday()
doesn't becauce pytime.c lacks a dependency on the librt module (needed on some
platforms).
Attached patch adds the dependency if needed and modify _PyTime_gettimeofday()
to
Martijn Pieters added the comment:
The documentation change in this patch introduced a bug in the Call grammar:
| * `expression` [, * `expression`] [, ** `expression`]
instead of
| * `expression` [, `keyword_arguments`] [, ** `expression`]
giving the impression that `*expression` is allowed
STINNER Victor added the comment:
To have an even smaller patch, I created the issue #22287 just to add the
dependency to the librt module in pytime.c.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22043
Changes by STINNER Victor victor.stin...@gmail.com:
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22286
___
___
Python-bugs-list
New submission from Martijn Pieters:
The changes for issue #3473 introduced a documentation bug. The Call expression
grammar implies that f(*[1, 2], *[3, 4]) is allowed:
| * `expression` [, * `expression`] [, ** `expression`]
I think Benjamin meant to use:
| * `expression` [,
Roundup Robot added the comment:
New changeset d984dfe8c34e by Victor Stinner in branch 'default':
Issue #22042: signal.set_wakeup_fd(fd) now raises an exception if the file
http://hg.python.org/cpython/rev/d984dfe8c34e
--
___
Python tracker
Changes by STINNER Victor victor.stin...@gmail.com:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22042
___
Nick Coghlan added the comment:
Note that pairing fsencode with 'utf-8' isn't guaranteed to do the right thing.
It would work for the default C locale (since that's ASCII), but not in the
general case.
Enhancing backslashreplace to also work on input is an interesting idea, but
worth making
STINNER Victor added the comment:
A first step would be to document the issue in the developer section of
asyncio documentation. Mention that the event loop should be closed and a new
event loop should be created.
--
___
Python tracker
Changes by STINNER Victor victor.stin...@gmail.com:
--
resolution: - not a bug
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22272
___
STINNER Victor added the comment:
I'd like to preserve support for building dynamic extension modules through
Modules/Setup, but they don't have to live in Modules; putting them into
build (say) would be fine as well.
Does it mean that you are ok to commit my patch?
--
Stefan Krah added the comment:
I think we have this behavior since 6c468df214dc and 227ce85bdbe0 (#17095).
--
nosy: +ned.deily, twouters
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22285
Stefan Krah added the comment:
The revisions that cause the bot to go red (6c468df214dc and 227ce85bdbe0) are
quite recent, so I suggest we address the failure in #22285.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22090
Roundup Robot added the comment:
New changeset f5f5553f219e by Victor Stinner in branch 'default':
Issue #22042: Fix test_signal on Windows
http://hg.python.org/cpython/rev/f5f5553f219e
--
___
Python tracker rep...@bugs.python.org
STINNER Victor added the comment:
I reopen the issue because these changes broke the decimal module when the
_decimal module is missing: see the issue #22285.
Martin von Loewis proposed to build modules in the build directory, not in the
Modules directory directly:
Changes by STINNER Victor victor.stin...@gmail.com:
--
nosy: +loewis, skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17095
___
___
New submission from STINNER Victor:
Attached patch should fix the following sporadic error. I wrote the patch for
Python 3.5. I will adapt it for Python 2.7 and 3.4 if the review is positive.
http://buildbot.python.org/all/builders/AMD64%20Ubuntu%20LTS%203.x/builds/4837/steps/test/logs/stdio
Martijn Pieters added the comment:
Proposed fix added in my fork.
--
hgrepos: +270
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22288
___
___
Changes by Martijn Pieters m...@python.org:
--
keywords: +patch
Added file: http://bugs.python.org/file36487/ffe77dc2979a.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22288
___
Changes by Martijn Pieters m...@python.org:
Removed file: http://bugs.python.org/file36487/ffe77dc2979a.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22288
___
Martijn Pieters added the comment:
Sigh, patch creation fails against a remove repository; I guess this only works
for the default branch.
Attached as a patch file instead.
--
Added file: http://bugs.python.org/file36488/issue22288.patch
___
Python
Changes by Martijn Pieters m...@python.org:
--
hgrepos: -270
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22288
___
___
Python-bugs-list mailing
STINNER Victor added the comment:
Another bug linked to the bad Modules/_ctypes package:
http://buildbot.python.org/all/builders/AMD64%20OpenIndiana%203.x/builds/8549/steps/test/logs/stdio
test test_ctypes crashed -- Traceback (most recent call last):
File
Fabian added the comment:
The patch adds an optional keyword which only accepts decimal numbers.
--
keywords: +patch
Added file: http://bugs.python.org/file36489/ipaddr.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22282
New submission from STINNER Victor:
I ran test_subprocess.test_preexec() 2000 times: I'm unable to reproduce the
issue on my OpenIndiana VM, nor on Linux. I used this command:
gdb -args ./python -m test -F -m test_preexec test_subprocess
The command on the buildbot is:
./python
STINNER Victor added the comment:
The error may be close to the call to the gc module: gc.isenabled(),
gc.disable() or gc.enable(). The error is maybe an exception raised before the
call to PyObject_Call(), because the called gc functions are very simple.
--
R. David Murray added the comment:
I think it is up to you motivate the reason why the new stdin and stderr
parameters should have *different* semantics from the same parameters used with
subprocess. Consistency is good, unless there is a specific reason to break
consistency. That is, if
R. David Murray added the comment:
I'm not going to argue this any further, but recent is exactly the point...if
all of the bots had turned red you'd understand that it needed to be fixed
*immediately* or the triggering change (regardless of what the actual bug was)
backed out. Since it
Cristian Consonni added the comment:
Hi David,
*now* I understand your point (!) and, yes, this is something I have thought
about.
Basically, I was thinking that with this addition I wanted an easy way to
suppress stdout/stderr output. I have thought about simply exposing
subprocess.Popen's
Cristian Consonni added the comment:
After re-reading myself a couple of times I have to say that following
subprocess.Popen and adding True and False with the meaning:
* True - subprocess inherits file descriptors from the parent process
(equivalent to None)
* False - /dev/null
seems to be a
New submission from Ben Rodrigue:
Small typo:
In the documentation for the random module. The documentation refers to the
semi-open range and then gives an example using a left bracket and then a
curved parenthesis on the right.
Link to page:https://docs.python.org/3.4/library/random.html
R. David Murray added the comment:
It makes sense, but I'm not sure avoiding the extra import is sufficient
motivation. If you weren't allowing redirection it would be a different story,
but allowing redirection seems logical.
We should get the opinion of some other developers. I've added
Martin v. Löwis added the comment:
Does it mean that you are ok to commit my patch?
No, because it will break #17095 again. A proper patch would do what you do,
plus find some other solution to #17095. Just reverting 6c468df214dc is not ok.
--
___
Stefan Krah added the comment:
I'm not going to argue this any further, but recent is exactly the
point...if all of the bots had turned red you'd understand that it needed to
be fixed *immediately* or the triggering change (regardless of what the
actual bug was) backed out. Since it
R. David Murray added the comment:
That's mathematical notation, not python syntax. Note that in the html it is
*not* styled as a literal code snippet.
--
nosy: +r.david.murray
resolution: - not a bug
stage: - resolved
status: open - closed
type: - behavior
STINNER Victor added the comment:
Since Hoxily didn't reply the question, I suggest to close this issue as not a
bug since we don't have enough information to understand it.
--
___
Python tracker rep...@bugs.python.org
STINNER Victor added the comment:
This issue is 6 years old. I don't understand the bug and the patch has no unit
test. I suggest to close the issue as out of date. The asynchat module is now
deprecated in favor of the new shiny asyncio module.
--
nosy: +haypo
R. David Murray added the comment:
Yeah, right now that's fine. We'll work out the more strict process if/when we
start actually enforcing it :)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22090
R. David Murray added the comment:
Since it is effectively a deprecated module, let's do that.
--
resolution: - works for me
stage: - resolved
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22059
STINNER Victor added the comment:
Why descriptor does not get polled if neither read nor write selected ?
IMO it's a deliberate design choice, made for performances.
In the asyncio module, the high-level StreamReader API stops listening to read
even if the buffer is too large (if we received
STINNER Victor added the comment:
The latest patch was written 5 years ago, it's probably a huge work to rebase
it. Giampaolo wrote that the code changed a lot since this time (especially
code handling errors).
asyncore-fix-refused-4.patch catchs EBADF. To me, it looks like a bug: if you
get
Guido van Rossum added the comment:
Loet's just spruce up the docs a bit. (Also maybe fix that awkward sentence in
the BufferedReader docs.)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22279
Jack O'Connor added the comment:
Agreed that changing read() would probably break tons of people. I don't think
a naming inconsistency meets the serious flaws are uncovered bar for breaking
a provisional package. If we actually prefer the asyncio way of doing things,
all the better.
That
Guido van Rossum added the comment:
Yeah, that too should just be documented. The read-until-eof behavior is
quite entrenched (in fact I had a hard time finding example read calls with
a size parameter :-). Specifying a huge buffer size in order to read until
EOF isn't really a common practice,
Min RK added the comment:
`--prefix` vs `--user` is the only conflict I have encountered, but based on
the way it works, it could just as easily happen with any of the various other
conflicting options in install (install_base, exec_prefix, etc.), though that
might not be very common.
There
New submission from attilio.dinisio:
= Error message =
pickle.dumps and pickle.dump generate the following error:
File /usr/lib/python3.4/pickle.py, line 283, in whichmodule
for module_name, module in sys.modules.items():
RuntimeError: dictionary changed size during iteration
= Test
endolith added the comment:
I ran into this bug with sets, too.
Expected:
{6, 5, 3}
Got:
set([5, 3, 6])
Documentation should illustrate how the function is actually meant to be used,
not contrived examples that convert to sorted output purely so that doctest can
understand them.
Roundup Robot added the comment:
New changeset 6f0dae921bee by Benjamin Peterson in branch '2.7':
properly handle file closing in error cases (closes #22266)
http://hg.python.org/cpython/rev/6f0dae921bee
--
nosy: +python-dev
resolution: - fixed
stage: - resolved
status: open - closed
Robert Collins added the comment:
The doc part of the patch was assuming this would be in 3.4 which it wasn't.
Updated to 3.5. Also found a corner case - when packages were imported the
_get_module_from_name method was not guarded for un-importable modules. This is
strictly a separate issue,
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21611
___
___
Python-bugs-list
Roundup Robot added the comment:
New changeset 3ae399c6ecf6 by Benjamin Peterson in branch '2.7':
correct call grammar error (#3473)
http://hg.python.org/cpython/rev/3ae399c6ecf6
--
nosy: +python-dev
___
Python tracker rep...@bugs.python.org
Raymond Hettinger added the comment:
doctest should be changed (or have an option) to understand
object equality rather than exact text output.
Sorry, but that would be at odds with the fundamental design of doctest which
is principally designed to test documentation in the form of
74 matches
Mail list logo