Zack McCauley added the comment:
If you use the older methods to detect OSVersion, Monterey will also
identify as 10.16. iirc there’s an environment variable to enable or
disable that.
On Thu, Nov 4, 2021 at 7:54 AM Marc Culler wrote:
>
> Marc Culler added the comment:
>
&g
Zack McCauley added the comment:
Awesome, thanks for the clear update reason. Makes more sense now. I was
able to get our software to patch around.
An API to get the installer urls would be super helpful.
Thanks Ned!
On Wed, Nov 3, 2021 at 4:19 PM Ned Deily wrote:
>
> Ned Deily
Zack McCauley added the comment:
Could this be bumped to a version update to like 3.10.1 or just replace the old
package with this updated one? The package name and format now break
automations that relied on matching version names in the url. This pattern has
worked since 2.7 releases
Zack added the comment:
Hello. I want to record a game in Windows 7 and I can not install it can you
help me
--
nosy: +Zack_Barton
___
Python tracker
<https://bugs.python.org/issue43
Zack Weinberg added the comment:
The code that needs to be changed is in distutils, setuptools just calls into
it. I haven't checked flit but I expect it does the same.
--
___
Python tracker
<https://bugs.python.org/issue38
Zack Weinberg added the comment:
I have yet another use case for the function implemented by this patch (i.e.
retrieving the cert chain actually sent by the server, regardless of whether
that gives a path to a trust anchor). I'm implementing a network forensics
tool, and one
New submission from Zack Weinberg :
Recent versions of the gzip command-line utility have an option `-n` which
causes it to omit the FNAME field of the gzip file header, and write out the
MTIME field as zero. Both of these properties are desirable when constructing
reproducible build
New submission from Zack Weinberg :
Recent versions of the gzip command-line utility have an option `-n` which
causes it to omit the FNAME field of the gzip file header, and write out the
MTIME field as zero. Both of these properties are desirable when constructing
reproducible build
New submission from Zack Weinberg :
Recent versions of the gzip command-line utility have an option `-n` which
causes it to omit the FNAME field of the gzip file header, and write out the
MTIME field as zero. Both of these properties are desirable when constructing
reproducible build
New submission from Zack Weinberg :
Reproducibility has so far been concerned primarily with binary packages, but
it's also desirable for source tarballs to be reproducible starting from a
version-control checkout. This is particularly important for Python, where
'setup.py sdist' can run
Zack Weinberg added the comment:
> To be clear: this issue is NOT a bug in Python
I don't think that's entirely true. I think CPython needs to be linked against
libgcc_s.so, so that this class of application bugs will no longer manifest as
interpreter crashes. I filed #37
New submission from Zack Weinberg :
There are several existing issues (e.g. #18748 and #35866) where at least part
of the problem is that GNU libc tried to dlopen() `libgcc_s.so` at a moment
when that's not safe, e.g. during thread or process shutdown. This converts a
recoverable error
Zack Weinberg added the comment:
I have observed this problem in a production application using Python 3.5 and
3.6 (system-packaged interpreters from Ubuntu) and I would like to mention that
this is an effective workaround:
```
import ctypes
libgcc_s = ctypes.CDLL("libgcc_s
New submission from zack :
the json.loads function think a string variable is a json type, but the
variable is "123"
--
components: Library (Lib)
files: json_test.py
messages: 325639
nosy: jaihong
priority: normal
severity: normal
status: open
title: json module loads fun
Zack Weinberg added the comment:
Also, whether or not the current behavior is the intended behavior, I think
programmers would appreciate an explicit statement of whether or not it might
change in the future.
--
___
Python tracker
<ht
New submission from Zack Weinberg :
The documentation of the semantics of range expressions in regular expression
character classes is not precise enough. All it says is
Ranges of characters can be indicated by giving two characters and
separating them by a '-', for example [a-z
New submission from Zack Weinberg <za...@panix.com>:
[_]thread.start_new_thread can fail if the underlying OS primitive fails
(pthread_create / _beginthreadex), but the exception that is thrown when this
happens is a generic RuntimeError (it's _called_ ThreadError in the source
New submission from Zack Elan <b...@zackelan.com>:
Repro: Call asyncio.wait_for(some_queue.get(), some_timeout) repeatedly, with
no items in the queue, so that the call times out each time.
Expected: No increase in memory while polling an empty queue
Actual: The queue holds on to p
Zack Weinberg added the comment:
It looks to me as if NameAliases.txt is the better reference for the C0 and C1
controls. It matches the UnicodeData.txt field 10 names for most entries where
the field 1 name is "", but it has names for U+0080, U+0081, U+0084,
and U+0099, which hav
New submission from Zack Weinberg:
unicodedata.name() doesn't have name information for the C0 and C1 control
characters. To see this, run
pprint.pprint(["U+{:04X} {}".format(n, unicodedata.name(chr(n), ""))
for n in range(256)])
and you will observe printed for U+
New submission from Zack Weinberg:
Occasionally one encounters binary formats which do not stick to one byte order
throughout. For example, I have a C program that reads and writes arrays of
this struct:
```
struct conn_data
{
uint32_t ipv4_addr; /* read - network byte order - target IPv4
New submission from Fairuz Zack:
html diff threat 2.011 as whole line added instead of only "11" is changed.
example file i want to diff is under bug_report.txt. seems the diff not
reasonable for other line in the txt as well.
--
components: Library (Lib)
files: bug_
Zack Weinberg added the comment:
> Obvious question: why not working on the asyncio support in this library?
The whole point of a transparent SOCKS module is that it provides a function
that's a *drop-in replacement* for socket.socket(). An asyncio-based SOCKS
module would have a complet
New submission from Zack Weinberg:
This is pretty esoteric, please bear with me. I'm attempting to enhance a
transparent-SOCKS module (https://github.com/Anorov/PySocks) to support
non-blocking connect(). This means, you should be able to do this:
socks.set_default_proxy(socks.SOCKS5
New submission from Zack Weinberg:
The `re` module documentation does not do a good job of explaining exactly what
`\w` matches. Quoting https://docs.python.org/3.5/library/re.html :
> \w
> For Unicode (str) patterns:
> Matches Unicode word characters; this includes most characters
&
Zack Weinberg added the comment:
FWIW, the actual behavior of \w matching "everything in Unicode general
categories L* and N*, plus U+005F (underscore)" is consistent across all
versions I can conveniently test (2.7, 3.4, 3.5).
In 2.7, there are four characters in general category
Zack Weinberg added the comment:
In terms of the formal grammar of the language, you are correct. However, the
position of the caret should be chosen based *not* on the formal grammar, but
on a heuristic estimation of what the most probable mistake actually is. In
both of the cases I listed
New submission from Zack Weinberg:
I tripped over a couple of SyntaxError cases where the diagnostic caret is
misplaced.
While x:
File stdin, line 1
While x:
^
SyntaxError: invalid syntax
The caret should point to the capital W in 'While'.
for x
Zack added the comment:
From memory, something along the lines of
from json import JSONEncoder
class ExtendedJSONEncoder(JSONEncoder):
def _iterencode(self, o, markers=None):
if isinstance(o, tuple) and hasattr(obj, '_fields'):
gen = self._iterencode_dict(o.__dict__
New submission from Zack:
We used to be able to override _iterencode prior to 2.7 to get our namedtuples
to be encoded as dict using json.dump(s) but now we can not.
Namedtuples are automatically encoded as list but it would be more logical and
convenient to have them encoded as dict
Simon Zack added the comment:
For those who want to use this right away, I've added a python implementation
of the patch, which passes the unit tests. There's a slight difference in
usage, where instead of using super() directly, super_prop(super()) needs to be
used, so we can still use super
Simon Zack added the comment:
+1 to this feature, this will dramatically simplify property setting code.
--
nosy: +simonzack
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14965
Simon Zack added the comment:
Ok, my bad, I was creating my own OSErrors so I was just testing it out. I just
found the default to be rather confusing as I thought None would not be mapped
to anything.
--
___
Python tracker rep...@bugs.python.org
Changes by Simon Zack simonz...@gmail.com:
--
components: +ctypes
versions: +Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22961
New submission from Simon Zack:
The ctypes.WinError function returns:
OSError(None, descr, None, code)
However OSError does not appear to allow None as a first argument, and converts
it to 22 which is the EINVAL Invalid Argument error. This is rather confusing
as there was no invalid
New submission from Simon Zack:
Python already has tuple unpacking in many places, I wonder if this has been
considered for arguments yet, it seems rather convenient and a natural
extension to me.
Here's what I mean:
def func((a, b, c)):
print(a, b, c)
func((1, 2, 3))
should print 1 2
New submission from Simon Zack:
Functions added by addTypeEqualityFunc is not used for comparing list elements
in assertListEqual, and only used in assertEqual.
It would be nice to have assertListEqual use functions added by
addTypeEqualityFunc for comparisons of list elements. I think
Changes by Simon Zack simonz...@gmail.com:
--
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22452
___
___
Python-bugs-list
New submission from Simon Zack:
The python unittest module currently uses camel case. This feels rather
inconsistent with the rest of the python library, which is in lower case and
follows PEP8.
Would it be a good idea to add lower-case aliases, and possibly deprecate the
camel case methods
Simon Zack added the comment:
The problem is still present in python 3.4 with mingw gcc 4.8.2. I was having
trouble with compiling radare2's python swig bindings.
The solution described here:
http://ascend4.org/Setting_up_a_MinGW-w64_build_environment#Setup_Python_for_compilation_of_extensions
Zack Weinberg added the comment:
Here is a new patch vs latest trunk.
--
Added file: http://bugs.python.org/file29924/issue16624-v34a.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16624
Changes by Zack Weinberg za...@panix.com:
Removed file: http://bugs.python.org/file28247/issue16624-v34.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16624
Zack Weinberg added the comment:
I think that it will be better not introduce a new argument, but reuse stdin.
Just allow io.BytesIO (or perhaps even any file object) be specified as stdin.
If we were designing from scratch I might agree, but we aren't. Principle of
least astonishment says
Zack Weinberg added the comment:
Note also that allowing `stdin=any filelike` in a clean fashion would require
rather more surgery than you suggest, because a filelike can produce an
infinite stream of data, and people would expect that to work when the
subprocess only reads a finite prefix
Zack Weinberg added the comment:
My position is:
* input= should be supported in check_output(), for consistency with
communicate().
* I like the idea of making stdin= support file-like objects which don't have a
fileno, in both communicate() and everything that calls it, but that does
Zack Weinberg added the comment:
??? communicate() has always had input= AFAIK.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16624
Zack Weinberg added the comment:
OK, I get that, but what I'm saying is I think input= is still desirable even
if stdin= becomes more powerful.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16624
Zack Weinberg added the comment:
Contributor agreement resent by email. Sorry for the delay.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16624
Zack Weinberg added the comment:
OK, here is a patch against the latest development version. Now also with
tests and documentation updates.
--
Added file: http://bugs.python.org/file28247/issue16624-v34.diff
___
Python tracker rep
Changes by Zack Weinberg za...@panix.com:
Removed file:
http://bugs.python.org/file28218/subprocess-check-output-allow-input.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16624
Zack Weinberg added the comment:
I don't have the ability to test on Windows, but the construct you are
concerned about was copied from other tests in the same file which were not
marked as Unix-only.
I have faxed in a contributor agreement
New submission from Zack Weinberg:
subprocess.check_output calls Popen.communicate but does not allow you to
specify its argument (i.e. data to send to the child process's stdin). It
would be nice if it were enhanced to allow this. Proposed patch attached (to
the 2.7 subprocess.py; should
Zack Goldstein gol...@gmail.com added the comment:
I've started going through the demos. So far I've gone through cgi and classes.
If this is what you're looking for I'll try and go through the rest in the next
week or so.
Python 3.2a0
/cgi
all work
/classes
Complex.py - fail
Zack Goldstein gol...@gmail.com added the comment:
I'm assuming tested means run, and that a good demo is one that works for
some nominal input.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7962
54 matches
Mail list logo
