Anders Kaseorg added the comment:
It could and does, as quoted in my original report.
Content-Type: text/plain; charset*=utf-8”''utf-8%E2%80%9D
That’s a U+201D right double quotation mark.
This is not a valid charset for the charset of course, but it seems like the
code was intended
Anders Hovmöller added the comment:
For `foo(a, /, b)`, it could be:
"TypeError: foo() missing 1 required argument 'a', and one required positional
argument 'b'.
If we start on this road there are some more, like for `def foo(a, *, b)` you
get the error "TypeError: foo() missing
Anders Hovmöller added the comment:
Just dropping the word "positional" is very good. That word is a lie, and just
removing it makes it true.
--
___
Python tracker
<https://bugs.python.o
New submission from Anders Hovmöller :
>>> def foo(a):
... pass
...
>>> foo()
Traceback (most recent call last):
File "", line 1, in
TypeError: foo() missing 1 required positional argument: 'a'
This error is incorrect. It says "positional argument"
Anders Kaseorg added the comment:
> While optparse that it isn't being developed further, therebut will not
> be taken away. IIRC the reason for this was that it too had become
> difficult to build out and that is what necessitated the creation of
> argparse -- there wasn't clea
Anders Kaseorg added the comment:
If argparse will not be developed further to fix this bug, then we should undo
the deprecation of optparse in the documentation
(https://bugs.python.org/issue37103), since the stated justification for that
deprecation was that optparse will not be developed
Change by Gregory Anders :
--
keywords: +patch
pull_requests: +26323
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/27868
___
Python tracker
<https://bugs.python.org/issu
New submission from Gregory Anders :
Currently pydoc returns an exit code of zero no matter what, even with e.g.
pydoc lsjdfkdfj
However, the ability to know whether or not pydoc successfully found a result
is useful in tools that embed pydoc in some way.
Here's one use case: Vim
Anders Kaseorg added the comment:
> extra_states[o] = ExtraState(obj)
(Typo for extra_states[obj] = ExtraState(obj), obviously.)
--
___
Python tracker
<https://bugs.python.org/issu
New submission from Anders Kaseorg :
Because WeakKeyDictionary unconditionally maintains strong references to its
values, the garbage collector fails to collect a reference cycle from a
WeakKeyDictionary value to its key. For example, the following program
unexpectedly leaks memory:
from
Anders Munch added the comment:
Are you sure you want to do this?
This optimisation is not applicable if the matched values are given symbolic
names. You would be encouraging people to write bad code with lots of
literals, for speed.
--
nosy: +AndersMunch
New submission from Anders Kaseorg :
We ran into a UnicodeEncodeError exception using email.parser to parse this
email
<https://lists.cam.ac.uk/pipermail/cl-isabelle-users/2021-February/msg00135.html>,
with full headers available in the raw archive
<https://lists.cam.ac.uk/pip
Anders Munch added the comment:
>> What does use getlocale is time.strptime and datetime.datetime.strptime, so
>> when getlocale fails, strptime fails.
> Would they work with getlocale() returning None for the encoding ?
Yes. All getlocale is used for in _strptime.py is comp
Anders Munch added the comment:
> BTW: What is wxWidgets doing with the returned values ?
wxWidgets doesn't call getlocale, it's a C++ library (wrapped by wxPython) that
uses C setlocale.
What does use getlocale is time.strptime and datetime.datetime.strptime, so
when getlocale fa
Anders Munch added the comment:
getlocale is documented to return None for the encoding if no encoding can be
determined. There's no need to guess.
I can't change the locale.setlocale call, because where I'm actually having the
problem, I'm not even calling locale.setlocale: wxWidgets
Anders Munch added the comment:
I discovered that this can happen with underscores as well:
Python 3.8.7 (tags/v3.8.7:6503f05, Dec 21 2020, 17:59:51) [MSC v.1928 64 bit
(AMD64)] on win32
Type "help", "copyright", "credits" or "license"
New submission from Anders Munch :
getlocale fails with an exception when the string returned by _setlocale is
already an RFC 1766 language tag.
Example:
Python 3.10.0a4 (tags/v3.10.0a4:445f7f5, Jan 4 2021, 19:55:53) [MSC v.1928 64
bit (AMD64)] on win32
Type "help", "copyr
Anders added the comment:
Note: due to a change in Python 3.8 this example would be a lot less noticeable
if tested. The problem remains the same though.
If you run this snippet with Python 3.7, which is before the thread reuse was
introduced into the ThreadPoolExecutor, each thread
Anders Hovmöller added the comment:
We were also bitten by this. In fact we still run a compatibility shim in
production where we log if the new and old behavior are different. We also
didn't think this "bug fix" made sense or was treated with the appropriate
gravity in the rel
Anders Lorentsen added the comment:
As a person without much experience, it sounded like a simple enough task, but
having dug a bit, I found it quite complicated. It seems to me that the
interpreter loop (in the standard REPL, that you get when you start ./python,
blocks for input somewhere
Anders Lorentsen added the comment:
I have actually managed to lost my local branch of this fix, though I assume I
can just start another one, manually copy over the changes, somehow mark this
current PR as cancelled, aborted, or in my option the best:
"replaced/superseeded by: [n
Anders Lorentsen added the comment:
As far as I can recall, the patch is generally speaking good to go. A number of
discussions arose on various details, however. In any event, I'll take a look
at it during the next few days.
--
___
Python
New submission from Anders Kaseorg :
The optparse library is currently marked in the documentation as deprecated in
favor of argparse. However, argparse uses a nonstandard reinterpretation of
Unix command line grammars that makes certain arguments impossible to express,
and causes scripts
Anders Hovmöller added the comment:
That might be true, but that seems like a weak argument. If anything, it means
those others are broken. What is the logic behind "(.*)" returning the entire
string (which is what you asked for) and exactly one empty string? Why not two
empty str
Anders Hovmöller added the comment:
Just as a comparison, sed does the 3.6 thing:
> echo foo | sed 's/\(.*\)/x\1y/g'
xfooy
--
___
Python tracker
<https://bugs.python.org/issu
Anders Hovmöller added the comment:
This was a really bad idea in my opinion. We just found this and we have no way
to know how this will impact production. It's really absurd that
re.sub('(.*)', r'foo', 'asd')
is "foo" in python 1 to 3.6 but 'foofoo' in python 3.7.
-
Anders Hovmöller added the comment:
I think this is a great idea. We would have needed this many times for tests
over the years.
--
nosy: +Anders.Hovmöller
___
Python tracker
<https://bugs.python.org/issue36
Anders Hovmöller added the comment:
I just discovered this ticket again and see that it's stuck!
I have read through the thread but it's still a bit unclear what would be
required to test this with homebrew like Guido says is needed for this to go
forward. Is there anyone who can explain
Anders Kaseorg added the comment:
porton: Please don’t steal someone else’s issue to report a different bug.
Open a new issue instead.
--
title: argparse: add a full fledged parser as a subparser -> argparse does not
accept options taking arguments beginning with dash (regress
Anders Hovmöller added the comment:
Output before this patch:
3666 function calls (3556 primitive calls) in 0.005 seconds
Ordered by: standard name
ncalls tottime percall cumtime percall filename:lineno(function)
20.0000.0000.0020.001 :1009
Anders Hovmöller added the comment:
There is an example output on github. Should I paste it here too? I can do it
once I get home if you want.
--
___
Python tracker
<https://bugs.python.org/issue34
Change by Anders Hovmöller :
--
keywords: +patch
pull_requests: +9046
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue34861>
___
___
Py
New submission from Anders Hovmöller :
The standard output for cProfile when run from a command line is not very
useful. It has two main flaws:
- Default sort order is by name of function
- It strips the full path of source files
The first makes it very hard to look at the output. The second
Anders Rundgren <anders.rundgren@gmail.com> added the comment:
Thanx for the superquick response!
I really appreciate it.
I'm obviously a Python n00b
Anders
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
New submission from Anders Rundgren <anders.rundgren@gmail.com>:
Python 3.5.1 (v3.5.1:37a07cee5969, Dec 6 2015, 01:54:25) [MSC v.1900 64 bit
(AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>>
Anders Lorentsen <pha...@gmail.com> added the comment:
What do you mean "is a bug", and "the PR would encourage this"? Can't it be
fixed?
Are you saying that just because it is a bug now, we should be discouraged from
making it work in the way you'd expect it to
Anders Lorentsen <pha...@gmail.com> added the comment:
> # runs this weird file
> subprocess.run([bin])
> # Currently an error; if this is implemented, would run
> # /bin/ls, and pass it the -l argument. Refers to something
> # completely different than our .exist
Anders Lorentsen <pha...@gmail.com> added the comment:
Wait a minute. The failing test is test_nonexisting_with_pipes, and it fails
because args[0] is a tuple - how can that be? Nobody is supposed to pass
cmd=sequence-where-first-element-is-a-tuple!
Is everything all right with th
Anders Lorentsen <pha...@gmail.com> added the comment:
Also, isn't there continuous integration testing? Everything passed on the PR,
so where does this come from?
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
Anders Lorentsen <pha...@gmail.com> added the comment:
This is strange, because _execute_child calls os.fsdecode with `args` as the
argument, which may be a list. os.fsdecode calls fspath. Now, the python
docstring of _fspath, as defined in Lib/os.py on line 1031, clearly
New submission from Anders Kaseorg <ande...@mit.edu>:
PosixPathTest.test_expanduser fails in the NixOS build sandbox, where every
user has home directory /, so it falls off the end of the for pwdent in
pwd.getpwall() loop.
nixbld:x:30001:3:Nix build user:/:/noshell
nobody:x:65534
Change by Anders Hovmöller <bo...@killingar.net>:
--
nosy: +Anders.Hovmöller
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
Change by Anders Hovmöller <bo...@killingar.net>:
--
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue22490>
___
Anders Lorentsen <pha...@gmail.com> added the comment:
Writing my tests, I originally looked at Lib/test/seq_tests.py. One test case
uses indexes that are (+-)4*sys.maxsize. This does not fit in Py_ssize_t, and
so these tests cause my array implementation to raise an overflow exc
Anders Lorentsen <pha...@gmail.com> added the comment:
I decided to work on this, and I would like some review, as this would be my
second contribution to cpython. Also, a general question:
As I defined the start and end arguments Py_ssize_t, bigger indexes (more
negative or more po
Anders Lorentsen <pha...@gmail.com> added the comment:
While researching this, I discovered that on MS Windows
>>> subprocess.run([pathlike_object, additional_arguments])
did not run like it did on Posix. My PR includes this probl
Anders Lorentsen <pha...@gmail.com> added the comment:
I was able to make a test that reproduces your code, and expectedly fails. Also
implemented a fix for it. See a temporary diff here:
https://pastebin.com/C9JWkg0i
However, there is also a specific MS Windows version of _execute
Anders Lorentsen <pha...@gmail.com> added the comment:
Had my first go at a python patch. Added a test case for it, and all tests
passing when I test with
`./python -bb -E -Wd -m test -v test.test_sqlite -r -w -uall -R 3:2`
--
nosy: +
Anders Hovmöller added the comment:
@larsonreever That lib is pretty limited, in that it doesn't handle dates or
deltas. Again: my lib that is linked above does and has comprehensive tests.
--
___
Python tracker <rep...@bugs.python.org>
Anders Kaseorg added the comment:
Usui, this is a tutorial intended for beginners. Even if the change from
“most” to “built-in” were a relevant one (and I don’t see how it is), beginners
cannot possibly be expected to parse that level of meaning out of a single word.
The difference between
Anders Lorentsen added the comment:
I updated my patch to account for that second corner case. But ideally,
shouldn't it rather be accounted for in the function that does the actual
conversion, that is, in _PyLong_AsByteArray?
--
Added file:
http://bugs.python.org/file43942
Anders Lorentsen added the comment:
So, am I to understand that the only corner case we should fix is that
>>> (-1).to_bytes(0, 'big', signed=True)
should raise an overflow error (currently it returns b'') ?
--
Added file:
http://bugs.python.org/
Anders Lorentsen added the comment:
Isn't it possible to just add a small line of code that checks if length is
less than or equal to 0, and if it is, call the necessary c functions to have
python raise a valueerror...? Sorry if this is giving a solution without
actually submitting the patch
Changes by Anders Lorentsen <pha...@gmail.com>:
--
nosy: +Phaqui
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27623>
___
__
Anders Hovmöller added the comment:
Hmm, ok. I guess I was confused by "dates and times" part of the subject. Ok,
so only datetimes. My other comments still apply though.
> On 19 Jul 2016, at 16:20, Mathieu Dupuy <rep...@bugs.python.org> wrote:
>
>
> Mat
Anders Hovmöller added the comment:
The tests attached to this ticket seem pretty bare. Issues that I can spot
directly:
- only tests for datetimes, not times or dates
- only tests for zulu and "-8:00” timezones
- no tests for invalid input (parsing a valid date as a datetime for ex
Anders Hovmöller added the comment:
> The `arrow` library depends on the supposed "strict" behaviour of strptime
> that has never been guaranteed, which often results in very buggy behaviour
> under some conditions.
Well… the arrow library accepts all sorts of broken
Anders Hovmöller added the comment:
>
> By the way, I just discovered, that the way we treat microseconds differs
> from the strptime one : we are smarter read every digits and smartly round to
> six, strptime doesn't go that far and just *truncate* to this. Should go
Anders Rundgren added the comment:
In ES6/V8-compatible implementations which include "node.js", Chrome, Firefox,
Safari and (of course) my Java reference implementation you can take a
cryptographic hash of a JSON object with a predictable result.
That is, this request is in no w
Anders Rundgren added the comment:
An easier fix than mucking around in the pretty complex number serializer code
would be adding an "ES6Format" option to the "json.dump*" methods which could
use the supplied conversion code as is.
For JSON parsing in an ES6-compatible way
Anders Rundgren added the comment:
As I said, the problem is close to fixed in 3.5.
You should not consider the JCS specification as the [sole] target but the
ability to creating a normalized JSON object which has many uses including
calculating a hash of such objects
New submission from Anders Rundgren:
According to the documentation repr() and str() are different when it comes to
number formatting. A test with a 100 million random and selected IEEE 64-bit
values returned no differences
--
components: Interpreter Core
messages: 259244
nosy
Anders Rundgren added the comment:
Apparently the docs have changed since 2.7:
https://docs.python.org/3.5/tutorial/floatingpoint.html
However, the documentation still "sort of" mentions repr() as the most accurate
form which isn't entirely correct since it nowadays is identi
New submission from Anders Rundgren:
ECMA has in their latest release defined that JSON elements must be ordered
during serialization. This is easy to accomplish using Python's OrderedDict.
What is less trivial is that numbers have to be formatted in a certain way as
well. I have tested
New submission from Anders Rundgren:
pip install Crypto
Terminates correctly and the package is there as well.
Unfortunately the directory is named "crypto" rather than "Crypto" so when I
perform
>>>import Crypto
the interpreter fails.
>>>import cryp
Anders Rundgren added the comment:
Antoine Pitrou added the comment:
To cope with this potential problem, compliant parsers must preserve the
original textual representation of properties internally in order to support
JCS normalization requirements
That sounds ridiculous. Did someone
Anders Rundgren added the comment:
Antoine Pitrou added the comment:
I won't claim to know/understand the specifics, but message payload in
base64 actually sounds reasonable to me, if far from optimal (both from
readibility and space overhead POV) :-).
It is indeed a working solution
Anders Rundgren added the comment:
I guess my particular requirement/wish is unusual (keeping the original textual
representation of a floating point number intact) while using Decimal should be
fairly universal.
If these things could be combined in a Decimal support option I would
Anders Rundgren added the comment:
Bob,
Your'e right, I have put up a requirement for JSON serializing that may be
over the top. OTOH, there are (AFAICT...) only two possible solutions:
1. Outlaw floating point data from the plot
2. Insist that serializers conform to the spec
As a pragmatic I
Anders Rundgren added the comment:
Well, I could have insisted on canonicalization of floating-point data but
that's so awkward that outlawing such data is a cleaner approach. Since the
target for JCS is security- and payment-protocols, I don't think the absence of
floating-point support
Anders Rundgren added the comment:
Using simplejson I got it to work!!!
I just wonder what you think of the solution:
import collections
import simplejson as json
from decimal import Decimal
class EnhancedDecimal(Decimal):
def __str__ (self):
return self.saved_string
def __new__
Anders Rundgren added the comment:
Bob,
I'm not sure I understand why you say that JCS requires *almost* full
normalization. Using browsers you can generate fully compliant JCS objects
using like 20 lines of javascript/webcrypto (here excluding base64 support).
No normalization step
Anders Rundgren added the comment:
The current JCS validator is only 150 lines and does both RSA and EC signatures:
https://code.google.com/p/openkeystore/source/browse/python/trunk/src/org/webpki/json/JCSValidator.py
My Java-version is much more advanced but this is quite useful anyway
Anders Rundgren added the comment:
Ethan Furman added the comment:
I am not a regular json user, but my impression is the format is
pretty basic, and we would be overloading it to try and keep numbers
with three decimal places as Decimal, and anything else as float.
Isn't json's main
Anders Rundgren added the comment:
I was actually hoping to implement the final part of this:
https://openkeystore.googlecode.com/svn/resources/trunk/docs/jcs.html#Normalization_and_Signature_Validation
It seems that the current Decimal implementation wouldn't save me anyway since
it modifies
Anders Rundgren added the comment:
It would be great if I could use a sub-classed Decimal during parsing but since
it doesn't appear to be a way to serialize the result using the json package
I'm probably stuck with the current 99% solution.
I have solved this in Java and JavaScript
New submission from Anders Rundgren:
jsonString = '{t:6,h:4.50, g:text,j:1.40e450}'
jsonObject = json.loads(jsonString,
object_pairs_hook=collections.OrderedDict,parse_float=Decimal)
for item in jsonObject:
print jsonObject[item]
6
4.50
text
1.40E+450
Works as expected.
However, there seems
New submission from Anders Hammarquist:
Python 2.7 HTMLParse.py lines 185-199 (similar lines still exist in Python 3.4)
match = charref.match(rawdata, i)
if match:
...
else:
if ; in rawdata[i:]: #bail
Anders Hovmöller added the comment:
Éric Araujo: absolutely. Although I think my code can be improved (speed wise,
elegance, etc) since I just wrote it quickly a weekend :)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Anders Hovmöller added the comment:
I've written a parser for ISO 8601: https://github.com/boxed/iso8601
Some basic tests are included and it supports most of the standard. Haven't
gotten around to the more obscure parts like durations and intervals, but those
are trivial to add
Changes by Anders Kaseorg ande...@mit.edu:
--
assignee: docs@python
components: Documentation
nosy: andersk, docs@python
priority: normal
severity: normal
status: open
title: types.NoneType missing
type: behavior
versions: Python 3.2
___
Python
New submission from Anders Kaseorg ande...@mit.edu:
http://docs.python.org/py3k/library/constants.html#None says that None is the
sole value type types.NoneType. However, NoneType was removed from the types
module with Python 3.
--
___
Python
New submission from Anders Hammarquist i...@iko.pp.se:
When testing Eutaxia on PyPy (1.9) I discovered a discrepancy in the path_hooks
import hook implementation. In CPython (2.7), if the find_module() method
raises ImportError (as imp.find_module() does when it does not find a module
Anders Blomdell anders.blomd...@control.lth.se added the comment:
So my suggestion is to remove in pysql_connection_commit the call to :
pysqlite_do_all_statements(self, ACTION_RESET, 0);
to bring back the correct old behavior.
That's what I have been running for years, now...
And also
Anders Kaseorg ande...@mit.edu added the comment:
James: That’s not related to this issue. This issue is about options taking
arguments beginning with dash (such as a2x --asciidoc-opts --safe, where --safe
is the argument to --asciidoc-opts), not positional arguments beginning with
dash
New submission from Anders Kaseorg ande...@mit.edu:
This feels like an arbitrary restriction (obvious sequences have been replaced
with ‘…’ to save space in this report):
zip([0], [1], [2], …, [1999])
File stdin, line 1
SyntaxError: more than 255 arguments
especially when this works:
zip
Anders Kaseorg ande...@mit.edu added the comment:
I guess the desugaring is slightly more complicated in the case where the
original function call already used *args or **kwargs:
f(arg0, …, arg999, *args, k0=v0, …, k999=v999, **kwargs)
becomes something like
f(*((arg0, …, arg999) + args
Anders Kaseorg ande...@mit.edu added the comment:
@andersk: Would the restriction to only having flags with a fixed
number of arguments be acceptable for your use case?
I think that’s fine. Anyone coming from optparse won’t need options with
optional arguments.
However, FWIW, GNU
New submission from Anders Østhus grapz...@gmail.com:
Hi
I'm running Python 2.7.1 (r271:86832, Nov 27 2010, 17:19:03) [MSC v.1500 64 bit
(AMD64)] on win32 (Server 2008 R2).
I've discovered that when moving files with shutil.move, the file won't inherit
the security settings as it should
Anders Østhus grapz...@gmail.com added the comment:
Ok, but the whole page you linked to (http://docs.python.org/library/shutil)
confuses me then.
It states at the top:
Warning
Even the higher-level file copying functions (copy(), copy2()) can’t copy all
file metadata.
On POSIX platforms
Anders Østhus grapz...@gmail.com added the comment:
Ok.
But that makes the whole method inconsistent.
Basically, if it's on the same filesystem, rename the file, and thus not
inheriting ACL. If it's on another use copy2, and inherit ACL.
That makes no sense, atleast not to me
Anders Østhus grapz...@gmail.com added the comment:
On my system (Win Server 2008 R2 64-Bit, Python 2.7.1), when I use copy, copy2
or move(to another filesystem), the file _will_ get the ACL of the DST folder,
and remove any ACL in SRC file that the DST folder does not have.
Thus, it doesn't
Anders Østhus grapz...@gmail.com added the comment:
Thank you for taking the time to explain it to me, but it still seems
inconsistent to me.
I did a test with the functions copy, copy2, move, os.rename, copyfile, both on
the same filesystem and another filesystem, and the result is:
Same
Anders Kaseorg ande...@mit.edu added the comment:
There are some problems that ‘=’ can’t solve, such as options with nargs ≥ 2.
optparse has no trouble with this:
parser = optparse.OptionParser()
parser.add_option('-a', nargs=2)
parser.parse_args(['-a', '-first', '-second'])
(Values
Anders Kaseorg ande...@mit.edu added the comment:
That would be a good first step.
I continue to advocate making that mode the default, because it’s consistent
with how every other command line program works[1], and backwards compatible
with the current argparse behavior.
As far
Anders Kaseorg ande...@mit.edu added the comment:
(1) It's only deprecated in the documentation
Which is why I suggested un-deprecating it in the documentation. (I want to
avoid encouraging programmers to switch away from optparse until this bug is
fixed.)
# proposed behavior
parser
Anders Chrigström ander...@users.sourceforge.net added the comment:
This is indeed a duplicate of #1571184
--
resolution: - duplicate
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1571170
Anders Blomdell anders.blomd...@control.lth.se added the comment:
The culprit seems to be 'pysqlite_do_all_statements(self, ACTION_RESET, 0)' in
pysqlite_connection_commit, which resets all active statements, but subsequent
fetch/fetchall seems to trash the sqlite3 state in the statements
New submission from Anders Blomdell anders.blomd...@control.lth.se:
With version 2.7 (and 2.7.1rc1), the following sequence (see attached test):
c = cursor.execute(' select k from t where k == ?;', (1,))
conn.commit()
r = c.fetchone()
Traceback (most recent call last):
File
Changes by Anders Sandvig anders.sand...@gmail.com:
--
nosy: +asandvig
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue809163
___
___
Python-bugs
1 - 100 of 131 matches
Mail list logo