Changes by Joshua Bronson :
--
nosy: +jab
___
Python tracker
<http://bugs.python.org/issue4753>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Joshua Kinard :
I'm attempting to get Python to cross-compile, and I'm not sure if this
is an actual flaw in the build system or not, but thought I'd detail
what I can here and seek comment from those in the know.
What happens is under a cross-environment se
Joshua Kinard added the comment:
Gotcha, I'll poke around and see what I can find. Are you guys open to
patches for 2.5.x still if we find something that needs patching (versus
passing lots of variables to the make process)?
___
Python tracker
Joshua Kinard added the comment:
Gotcha. Not sure how far off Gentoo is from supporting 2.6 -- our
primary package manager relies on it, so the updates tend to be slow.
for moving to new versions.
Do you guys maintain any kind of an "internals" guide to the build
system anywhere
Joshua Kinard added the comment:
Anyone gotten farther on getting Python-2.5.x to cross-compile? I'm
trying to get x86_64-pc-linux-gnu --> mipsel-unknown-linux-gnu, and
after some hacking at the last updated cross-2.5.1.patch, plus a fix for
the %zd printf bugaboo, plus adding in co
Joshua Kinard added the comment:
Making progress!
Adapted the cross-2.5.1.patch from Issue #1597850, integrated the %zd
printf fixup patch, and added another cross-compiler check for the
libffi configure bits in setup.py (it'd pass libffi's configure no
--host options, so libffi wou
Joshua Kinard added the comment:
Roumen,
I took a look at 4010, and tried your patch (as well as attempted to
apply the latter patch, but they changes are too great). Neither one
helped resolve my issue, but I should probably explain the angle I'm
attacking this from so you have an id
Changes by Joshua Logan :
--
nosy: +jaylogan
___
Python tracker
<http://bugs.python.org/issue2636>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Joshua Kugler :
On the page lib/http-redirect-handler.html it says the signature of
redirect_request is:
redirect_request( req, fp, code, msg, hdrs)
It is actually:
redirect_request(req, fp, code, msg, hdrs, newurl)
Well, technically the signature is:
redirect_request
New submission from Joshua Kugler :
I tried to edit my e-mail address in the python bug tracker
(under "Your Details"), but when I hit submit, it tells me:
You do not have permission to edit user
--
components: None
messages: 83833
nosy: jkugler
severity: normal
status:
Joshua Kinard added the comment:
Is there any movement on this perchance? Just bumped into this on my
MIPS platform and discovered this bug.
--
nosy: +kumba
___
Python tracker
<http://bugs.python.org/issue4
Changes by joshua williams :
--
nosy: +jowillia
___
Python tracker
<http://bugs.python.org/issue5723>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Joshua Bronson:
Since code can be clearer than prose, I just sketched this idea out in the
attached patch. Please take a look at it as a minimum demonstration of the
concept.
Rationale:
The Python standard library provides collections.OrderedDict, along with
several ABCs
Joshua Bronson added the comment:
This patch improves the OrderedMapping.__eq__ implementation to be more generic
in the case that ``other`` is an unordered Mapping of the same length as
``self``.
--
Added file: http://bugs.python.org/file45805/jab-orderedmapping-2.patch
Joshua Bronson added the comment:
Come to think of it, to be exact, rather than extending Reversible,
OrderedMapping could extend a narrower interface, something like
collections.abc.Ordered, along with extending Mapping. (Reversible implies
Ordered, but Ordered does not imply Reversible: a
Joshua Bronson added the comment:
I only just found the "[Python-ideas] Adding collections.abc.Ordered" thread at
https://mail.python.org/pipermail/python-ideas/2015-November/037146.html -
sorry for not seeing it sooner. Looking forward to catching up on wha
Joshua Bronson added the comment:
Sorry to hear but thanks for the consideration. To follow up on your comments:
> nice to see Guido's reasons for giving a -0 on the proposal.
(Guido was giving his -0 on a proposal for collections.abc.Ordered, whereas the
main proposal
Joshua Bronson added the comment:
For the record, it looks like Victor Stinner suggested doing this in
https://mail.python.org/pipermail/python-dev/2016-September/146349.html
Brett Cannon replied in
https://mail.python.org/pipermail/python-dev/2016-September/146350.html to
suggest adding
Joshua Kinard added the comment:
Hi,
I came across a StackOverflow question that apparently turned up a bug in Tk
itself with regards to Spinboxes on Windows Aero themes. The question is here:
http://stackoverflow.com/q/30783603/
And I did a deep-dive of the issue here as the accepted answer
Joshua Kinard added the comment:
@Terry: This only applies on the Windows release of Python. On both Linux and
FreeBSD, you can wind up with Python 2.7 and Tk-8.6.x by default in some
instances:
# pkg info | grep python27
python27-2.7.13_1 Interpreted object-oriented programming
Joshua Kinard added the comment:
Fair enough. I am stuck working with 2.7 for quite a while longer due to
platform constraints, but hopefully can migrate over to 3.x at some point. Was
worth asking :)
At least try to cherrypick that one commit from the TCL/Tk source I referenced
so that
New submission from Joshua Haas:
According to the 2.7 docs at
https://docs.python.org/2/library/configparser.html, you can create in-line
comments using ";" if it is preceded by white space.
However, if the value of a config option contains a semi-colon, for example
"pass
New submission from Joshua Haas:
Originally reported at http://bugs.python.org/issue27762 as a behavior bug but
was determined to be won't fix. Thus I think this needs to be mentioned in the
documentation at https://docs.python.org/2/library/configparser.html
I propose that directly afte
Joshua Haas added the comment:
I'm not sure it's deprecated so much as moved. Python 3.5 includes an
additional init parameter, so setting inline_comment_prefixes=';' allows inline
comments even for values containing the ';' character, displaying the "
Joshua Chia added the comment:
Added test case
--
resolution: -> duplicate
status: open -> closed
Added file: http://bugs.python.org/file29639/test.py
___
Python tracker
<http://bugs.python.org/i
Joshua Chia added the comment:
Seems to be duplicate of http://bugs.python.org/issue12776
--
___
Python tracker
<http://bugs.python.org/issue13271>
___
___
Pytho
New submission from Joshua Harlow:
When a future can't be accepted by an executor that it is has been submitted to
it would be really nice to throw have a type of 'RejectedExecutionException'
(this is the name the java folks have used) to denote that the executors policy
doe
New submission from Joshua Chin:
Currently, in-place operations on 'collections.Counter' with unsupported types
raises an 'AttributeError'.
Example:
>>> import collections
>>> counter = collections.Counter()
>>> counter += 1
Traceback (most r
New submission from Joshua Chin:
The documentation for urlopen states that it "Raises URLError on errors."
However, urlopen can raise a ValueError. In fact, test_urllib.
urlopen_FileTests.test_relativelocalfile specifically checks if urlopen raises
a ValueError. I suggest re
Changes by Joshua Chin :
Added file: http://bugs.python.org/file37131/urlopen_doc.patch
___
Python tracker
<http://bugs.python.org/issue22797>
___
___
Python-bugs-list m
New submission from Joshua Ellinger:
The problem is that the python path name is quoted if it contains spaces. The
launcher does not remove the extra quotes and fails.
I 'solved' by editing the pip.exe to remove the quotes.
ps - Windows programs are normally installed under c:\Pro
Joshua Ellinger added the comment:
Having pip not work after a straight install to the normal place you'd install
it on windows can't be a feature.
Even after I changed the .exe, pip itself breaks on the same problem.
Basically, you can't install python to
the normal place o
Joshua Ellinger added the comment:
The safest fix would be to make subprocess strip double-quotes from the
executable path.
Double quote (") is not an allowed character in Windows file systems. There is
no case under
which it can be correct to spawn a process in Windows where the pa
Joshua Landau added the comment:
The problem seems to be that with the removal of
-else if (TYPE(ch) == STAR) {
-vararg = ast_for_expr(c, CHILD(n, i+1));
-if (!vararg)
-return NULL;
-i++;
-}
-else if (TYPE(ch
Joshua Landau added the comment:
This causes a segmentation fault if any keyword arguments come after a
**-unpack. Minimal demo:
f(**x, x=x)
--
___
Python tracker
<http://bugs.python.org/issue2
Joshua Landau added the comment:
Just change
if (!PyUnicode_Compare(tmp, key)) {
when iterating over prior keyword arguments to
if (tmp && !PyUnicode_Compare(tmp, key)) {
since tmp (the argument's name) can now be NULL.
--
_
Joshua Landau added the comment:
I take it back; that just causes
>>> f(**{}, c=2)
XXX lineno: 1, opcode: 105
Traceback (most recent call last):
File "", line 1, in
SystemError: unknown opcode
--
___
Py
Joshua Landau added the comment:
I think I've got it working; I'm just working out how to make a patch and
adding a test or two. I think I'll also need to sign the contributor agreement.
While I'm at it, here are a few other deviations from the PEP:
- {*()} and {**
Joshua Landau added the comment:
This was a rather minor fix; I basically moved from STORE_SUBSCR to STORE_MAP
and fixed a BUILD_MAP opcode.
--
Added file: http://bugs.python.org/file37795/starunpack7.diff
___
Python tracker
<http://bugs.python.
Joshua Landau added the comment:
Aye, I'd done so (see starunpack7.diff). It was the fuss to reapply it ontop of
your newer diff and making sure I'd read at least *some* of the devguide before
barging on.
Anyhow, here's another small fix to deal with the [*[0] for i in [0]] pr
Joshua Landau added the comment:
I'm getting
>>> f(x=5, **{'x': 1}, **{'x': 3}, y=2)
Traceback (most recent call last):
File "", line 1, in
TypeError: f() got multiple values for keyword argument 'x'
Which, as I underst
Joshua Landau added the comment:
> The problem with using STORE_MAP is you create a new dict for each keyword
> argument in that situation.
You don't; if you look at the disassembly for producing a built-in dict
("dis.dis('{1:2, 2:3, 3:4}')") you'll s
Joshua Landau added the comment:
2 here as well:
15 LOAD_CONST 2 ('w')
18 LOAD_CONST 3 (1)
21 BUILD_MAP1
24 LOAD_CONST 4 (2)
27 LOAD_CONST 5 ('x')
30 STORE_MAP
31 BUILD_MAP
Joshua Landau added the comment:
Some of the tests seemed to be failing simply because they were incorrect. This
fixes that.
--
Added file: http://bugs.python.org/file37806/starunpack12.diff
___
Python tracker
<http://bugs.python.org/issue2
Joshua Landau added the comment:
I think I've fixed the memory leaks (plural).
There were also a host of other problems with the _UNPACK opcodes in ceval.
Here are the things I remember fixing, although I think I did slightly more:
- Not throwing an error when PyDict_New or PyDict_U
Joshua Landau added the comment:
> The _UNPACK opcodes are new in this changelist.
Yup, but they're used in the other unpacking syntax too:
(*(1, 2, 3), *(4, 5, 6))
--
___
Python tracker
<http://bugs.python.or
Joshua Landau added the comment:
Good catch.
CALL_FUNCTION seems to split its opcode into two to give it a
positional-keyword pair so this seems fine. I'd hope we can do the same thing;
personally I would do:
BUILD_MAP_UNPACK(
position_of_function_in_stack_or_0
Joshua Landau added the comment:
Functions are already limited to 255 arguments, so I don't think so.
--
___
Python tracker
<http://bugs.python.org/i
Joshua Landau added the comment:
According to the standard, int can be only 16 bits long so that only leaves
255/255. However, if the offset is on top of the dictionary count, this is
easily enough to clear the limits for the maximum function size (worst case is
a merge of 255 dicts with an
Joshua Landau added the comment:
We wouldn't want to replace STORE_MAP since that's used in dictionary
comprehensions, but replacing BUILD_MAP with BUILD_MAP(n) sounds like a great
idea.
--
___
Python tracker
<http://bugs.python.
Joshua Landau added the comment:
I've looked at BUILD_MAP(n). It seems to work and has speed improvements but:
- I was wrong about the 16-bit int thing. It turns out CPython is happily
treating them as 32 bit as long as they are prefixed by an EXTENDED_ARG bytecode
https://docs.pytho
Joshua Landau added the comment:
Why would that simplify things?
--
___
Python tracker
<http://bugs.python.org/issue2292>
___
___
Python-bugs-list mailin
Joshua Landau added the comment:
I phrased that badly. Whilst I can see minor simplifications to
BUILD_MAP_UNPACK, the only way to add more information to CALL_FUNCTION_XXX
would be through EXTENDED_ARG. This seems like it would outweigh any benefits,
and the tiny duplication of error
Joshua Landau added the comment:
I imagine it like (in the map unpacking code)
func_offset = (oparg >> 8) & 0xFF;
num_maps = oparg & 0xFF;
// later
if (func_offset) {
// do checks
if (repeated_argument) {
raise_error_from_function(PE
Joshua Landau added the comment:
We wouldn't actually need to raise it "from" somewhere else; the line numbering
and frame are already correct. The only difficulty is that the traceback
currently says
# func(a=1, **{'a': 1})
TypeError: func() got multiple va
Joshua Landau added the comment:
The stack will have the function, then any number of positional arguments, then
optionally an *args, then any number (>= 2) of maps to unpack. To get to the
function, you need to know the sum count of all of th
Joshua Landau added the comment:
The function object that's on the stack.
--
___
Python tracker
<http://bugs.python.org/issue2292>
___
___
Python-bugs-list m
Joshua Landau added the comment:
Just before any arguments to the function.
--
___
Python tracker
<http://bugs.python.org/issue2292>
___
___
Python-bugs-list m
Joshua Landau added the comment:
No, that happens in CALL_FUNCTION_KW:
>>> import dis
>>> dis.dis("f(x=1, **{'x': 1})")
1 0 LOAD_NAME0 (f)
3 LOAD_CONST 0 ('x')
6 LOAD_CONS
New submission from Joshua Landau:
It is claimed that all expressions are evaluated left-to-right, including in
functions¹. However,
f(*a(), b=b())
will evaluate b() before a().
¹ https://docs.python.org/3/reference/expressions.html#evaluation-order
--
components: Interpreter
Joshua Landau added the comment:
Amazing, thanks.
I also just uncovered http://bugs.python.org/issue23316; we'll need to support
a patch for that. In fact, bad evaluation order is why I haven't yet gotten
down my unification strategy. I wouldn't worry about extra opcodes when
Joshua Landau added the comment:
If we're supporting
f(**x for x in y)
surely we should also support
f(x: y for x, y in z)
I personally don't like this idea.
--
___
Python tracker
<http://bugs.python.
Joshua Landau added the comment:
Quick-fix for Guido's bug attached. I'm not familiar with this part of the
code, yet, so take this tentatively. I just changed
while (containers > 1) {
to
while (containers) {
---
@Guido
My comments were assuming `f(**x for x in y)`
Joshua Landau added the comment:
Update for the error messages fix.
I've put aside the idea of unifying things for now because there are a couple
of interdependencies I wasn't expecting and I absolutely don't want the
fast-path for f(x) to get slower.
--
A
Joshua Landau added the comment:
Special-cased `(*i for i in x)` to use YIELD_FROM instead of looping. Speed
improved, albeit still only half as fast as chain.from_iterable.
Fixed error message check in test_syntax and removed semicolons.
--
Added file: http://bugs.python.org
Joshua Landau added the comment:
I don't know the etiquette rules for the issue tracker, but I'd really
appreciate having something to debug -- it's working for me, you see.
--
___
Python tracker
<http://bugs.py
New submission from Joshua Bronson:
Is it intentional that the second assertion in the following code fails?
```
from collections import OrderedDict
d = dict(C='carbon')
o = OrderedDict(d)
assert d == o
assert d.viewitems() == o.viewitems()
```
Since d == o, I'm surprised t
New submission from Joshua Harlow:
It would be quite useful to have some types of metrics attached to future
objects so that callers could use them for various activities (scheduling
repeated runs, post-analysis and such):
Some of the ones that I can think would be useful:
- 'submitt
Joshua Harlow added the comment:
I like the pluggable/hookable idea, that would be nice (I'm siding on the side
of hookable, since I think that would be more 'elegant'). If these are just
callbacks that can be hooked in for these specific 'events' that would allow
Joshua Harlow added the comment:
A prototype (WIP) of how this could work, initial thoughts welcome :-)
--
keywords: +patch
Added file: http://bugs.python.org/file39711/prototype.patch
___
Python tracker
<http://bugs.python.org/issue24
Joshua Harlow added the comment:
Out of curiosity what reference cycles can't be broken in various python
versions? Is it documented/explained anywhere?
--
nosy: +Joshua.Harlow
___
Python tracker
<http://bugs.python.org/is
New submission from Joshua Harlow:
In situations where thread-local variables need to be setup it is quite useful
to be able to hook into the thread creation process, so that as each new thread
is spun up by the ThreadPoolExecutor that the threads created initially call
into a provided
Changes by Joshua Harlow :
--
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issue24980>
___
___
Python-bugs-list mailing list
Unsubscrib
Changes by Joshua Harlow :
--
versions: +Python 3.6
___
Python tracker
<http://bugs.python.org/issue24980>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Joshua Harlow :
--
components: +Library (Lib)
___
Python tracker
<http://bugs.python.org/issue24980>
___
___
Python-bugs-list mailing list
Unsubscribe:
Joshua Harlow added the comment:
Initial possible patch.
--
keywords: +patch
type: enhancement ->
Added file: http://bugs.python.org/file40318/add_future_callback.patch
___
Python tracker
<http://bugs.python.org/issu
New submission from Joshua Bronson:
ConfigParser.getboolean[1] has logic to convert strings like '0' and 'False' to
False. This logic is generally useful in other contexts and need not be coupled
to ConfigParser. Would you consider accepting a patch that factored this
str
Joshua Bronson added the comment:
One way this could be offered is as a new static method on bool (something like
bool.parse_str?), but I of course defer to the better judgment of the Python
core developers. I'd be happy to take a crack at a patch adding it wherever you
like, if you
Changes by Joshua Landau :
--
versions: +Python 3.6
___
Python tracker
<http://bugs.python.org/issue21593>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Joshua Bronson :
--
nosy: +jab
___
Python tracker
<http://bugs.python.org/issue17006>
___
___
Python-bugs-list mailing list
Unsubscribe:
Joshua Bronson added the comment:
My friend @novalis_dt and I worked up a patch for this including tests
(attached). First time working with the CPython codebase but hope it's a
reasonable start.
Here's a preview:
~>
New submission from Joshua Cannell:
There seems to be an issue capturing keyboard interrupts on Windows 10 when
using raw_input() inside of a class method w/python 2.7.x.
So far I have tested this on:
2.7.11 x86 on Windows 10 x64 - Does not capture (Traceback)
2.7.11 x64 on Windows 10 x64
Joshua Cannell added the comment:
Hi,
Thanks for the quick response.
I tried your code, it doesn't capture the keyboard interrupt, so the method
doesn't seem to be needed. Also, the code doesn't carry on if interrupt was
received, but instead produces the stack traceback. For
Joshua Cannell added the comment:
I can post a script if necessary, but it looks like Zach has already done so. I
appreciate you verifying this.
--
___
Python tracker
<http://bugs.python.org/issue26
Joshua Cannell added the comment:
Yeah, so this looks like a behavior in Windows in which an EOFError is raised
when a Ctrl + C is pressed, followed by a KeyboardInterrupt.
This post basically explains how to overcome it:
http://stackoverflow.com/questions/31127652/cannot-catch
New submission from Joshua Landau:
This is effectively a continuation of https://bugs.python.org/issue9712.
The line in Lib/tokenize.py
Name = r'\w+'
must be changed to a regular expression that accepts Other_ID_Start at the
start and Other_ID_Continue elsewhere. Hence tokeniz
Joshua Landau added the comment:
Sorry, I'd stumbled on my old comment on the closed issue and completely forgot
about the *last* time I did the same thing.
--
___
Python tracker
<http://bugs.python.org/is
Joshua Bronson added the comment:
Hi Raymond, I'm a bit confused by your comment. The patch I attached to my
previous message adds the static method `bool.parse_config_str`. So there's no
need to `import configparser` to use this, and "from" is no longer included in
the
Joshua Bronson added the comment:
Actually, looks like the version of the patch I attached did use the name
`bool.from_config_str`, sorry about that -- I'll attach a new patch renaming
this to `bool.parse_config_str` if there is interest in further consider
Joshua Bronson added the comment:
Though come to think of it, the issue you raised with using "from" in the
method name wouldn't apply here, since the static method is on the bool class,
and the method does return bool.
--
___
Python
New submission from Joshua Morton:
Following the comments in python ideas [1], I'm submitting a bug report. In
python 3, dictionary views (KeysView and ItemsView specifically) do not adhere
to the same interface as Sets. Specifically, the __and__, __or__, __xor__, and
__sub__ methods on
Joshua Morton added the comment:
There (seemed to be) consensus between the one or two on topic commenters that
something was off, although much of the discussion was on a tangent. Although
on looking back, there was even less discussion than I originally thought. Heh.
My response was going
Joshua Bronson added the comment:
Quoting Victor Stinner:
> I may workaround the bug during Python finalization if more users report
> this issue.
Read the above so reporting I'm hitting this too fwiw.
Thanks for the great work on asyncio.
--
Joshua Bronson added the comment:
Not sure if it's related / helpful but just in case, since upgrading from 3.4.2
to 3.4.3, I'm now seeing this printed to stderr sometimes when my program exits:
Exception ignored in: Exception ignored in: Exception ignored in: Exception
ignored in:
Changes by Joshua Bronson :
--
nosy: +jab
___
Python tracker
<http://bugs.python.org/issue23894>
___
___
Python-bugs-list mailing list
Unsubscribe:
Joshua Landau added the comment:
This doesn't seem to be a complete fix; the regex used does not include
Other_ID_Start or Other_ID_Continue from
https://docs.python.org/3.5/reference/lexical_analysis.html#identifiers
Hence tokenize does not accept '℘·'.
Credit to mo
Joshua Landau added the comment:
There is a change as part of this to make dict building more like list and set
building, which both have this behaviour.
The same changes have likely occurred before whenever BUILD_LIST and BUILD_SET
were introduced, and this behaviour seems particularly
Joshua Landau added the comment:
This should also be applied to regex.search's docstring.
https://docs.python.org/3.5/library/re.html#re.regex.search
--
resolution: fixed ->
status: closed -> open
___
Python tracker
<http://b
New submission from Joshua Landau:
This is valid:
℘· = 1
print(℘·)
#>>> 1
But this gives an error token:
from io import BytesIO
from tokenize import tokenize
stream = BytesIO("℘·".encode("utf-8"))
print(*tokenize(stream.read), sep=&qu
Changes by Joshua Bronson :
--
nosy: +jab
___
Python tracker
<http://bugs.python.org/issue27350>
___
___
Python-bugs-list mailing list
Unsubscribe:
201 - 300 of 343 matches
Mail list logo
