ed wolf added the comment:
Will ElementTree.write be updated to correct this issue?
--
___
Python tracker
<https://bugs.python.org/issue45336>
___
___
Python-bug
ed wolf added the comment:
Hi Andrew
I removed the quotes and still see an issue with the standalone not being added
to the xml declaration. I set the command as follows
rte_ecu_tree.write(rtexmlFile, encoding="UTF-8", xml_declaration=True,
default_namespace=None, m
New submission from ed wolf :
When executing the following command after modifiy an xml file an error is
prodcued.
import xml.etree.ElementTree as ET
rtexmlFile = 'Fox_CM3550A_SWP1_Rte_ecuc.arxml'
rte_ecu_tree = ET.parse(rtexmlFile)
root = rte_ecu_tree.getroot()
rte_ecu_tree.write(
New submission from ed :
some win7sp1 and win10:20H2 boxes cannot realpath a networked drive letter such
as b"n:" (also affects b"n:\\")
* observed with 3.8.7 and 3.9.1
* 3.7.9 is fine
requirements to trigger:
* bytestring (not unicode str)
* just the drive lette
New submission from Ed Catmur :
If a logging.FileHandler is configured with mode='w', or if logging.basicConfig
is called with filemode='w' (as suggested by the Basic Logging Tutorial
https://docs.python.org/3/howto/logging.html#logging-basic-tutorial)
and if some code
New submission from Ed Catmur :
Context: CentOS 7.8.2003, Python 3.8 from SCL. localhost has IPv4 and IPv6
bindings, IPv6 first:
$ python -c "import
socket;print(socket.getaddrinfo('localhost',0,type=socket.SOCK_STREAM))"
[(, , 6, '', ('::1',
New submission from Ed Morley :
The `ResourceWarning` warning has always been ignored by default, since it was
added in Python 3.2 in:
https://github.com/python/cpython/commit/08be72d0aa0112118b79d271479598c218adfd23#diff-db4e2b9efea108a38c53e06fa99cdd77R391
However there are several places in
Ed Schouten added the comment:
Ah, you folks switched to Git + Github in the mean time. Nice!
I've just sent this pull request: https://github.com/python/cpython/pull/4691
--
___
Python tracker
<https://bugs.python.org/is
Ed Schouten added the comment:
Having looked at various implementations of crypt() and crypt_r(), I can't
think of a reason why there would be any significant difference in performance.
On systems like FreeBSD, crypt() is just a simple wrapper around crypt_r():
https://svnweb.freebs
Changes by Ed Morley :
--
nosy: +edmorley
___
Python tracker
<http://bugs.python.org/issue27640>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ed Maste :
--
nosy: +emaste
___
Python tracker
<http://bugs.python.org/issue30104>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Ed Schouten added the comment:
Looks good to me!
--
___
Python tracker
<http://bugs.python.org/issue25658>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ed Schouten added the comment:
CloudABI uses a structure type, which is exactly why I filed this bug report.
Instead of speculating about what kind of type existing implementations use,
please just focus on the specification to which we're trying to stick: POSIX.
http://pubs.opengrou
Ed Schouten added the comment:
It can also be a structure or a union.
--
___
Python tracker
<http://bugs.python.org/issue25658>
___
___
Python-bugs-list mailin
New submission from Ed Schouten:
Modern C code should use inet_ntop()/inet_pton() as opposed to
inet_addr()/inet_aton()/inet_ntoa().
Though the former functions may typically act as drop-in replacements for the
latter, the inet_addr()/inet_aton() functions still have the advantage over
New submission from Ed Schouten:
The '_crypt' module provides a binding to the C crypt(3) function. It is used
by the crypt.crypt() function.
Looking at the C code, there are a couple of things we can improve:
- Because crypt() only depends on primitive C types, we currently get
New submission from Ed Schouten:
CloudABI is a POSIX-like strongly sandboxed runtime environment, for which we
got Python to work
(https://mail.python.org/pipermail/python-dev/2016-July/145708.html). Patches
for this are slowly being upstreamed.
CloudABI uses a capability-based security
New submission from Ed Schouten:
CloudABI is a POSIX-like strongly sandboxed runtime environment, for which we
got Python to work
(https://mail.python.org/pipermail/python-dev/2016-July/145708.html). Patches
for this are slowly being upstreamed.
As CloudABI uses a capability-based security
Ed Schouten added the comment:
Attached is an updated version of the patch that applies cleanly against Python
3.6.0b2.
--
Added file: http://bugs.python.org/file45181/27701.diff
___
Python tracker
<http://bugs.python.org/issue27
Ed Schouten added the comment:
I've been brainwashed by
https://google.github.io/styleguide/cppguide.html#Function_Parameter_Ordering
over the last couple of years, which is why I thought
`localtime()/localtime_r()`'s way of ordering the arguments made most s
Ed Schouten added the comment:
Does this patch look all right to you?
--
Added file: http://bugs.python.org/file44667/patch-pytime-localtime-gmtime
___
Python tracker
<http://bugs.python.org/issue28
Ed Schouten added the comment:
As a person who keeps a close eye on the Austin Group mailing lists (i.e., 'the
POSIX working group'), my guess is that it's very unlikely that POSIX will ever
add those *_s() extensions. Here's a discussion on Reddit that actually
captures
Ed Schouten added the comment:
Hi Alexander,
I'm absolutely no expert when it comes to the Python codebase, so I've got a
question. If we're going to movein this to Include/pytime.h, we should likely
introduce full wrappers that have a name starting with _PyTime_, right?
This
New submission from Ed Schouten:
CloudABI (https://mail.python.org/pipermail/python-dev/2016-July/145708.html)
does not provide getpid(). Though this may sound quite silly at first, there is
quite a good reason for this. One of the things that CloudABI wants to achieve
is making large scale
Changes by Ed Schouten :
--
title: Also stop using localtime() in timemodule -> [Patch] Also stop using
localtime() in timemodule
___
Python tracker
<http://bugs.python.org/issu
New submission from Ed Schouten:
Just like the BSDs and Mac OS X, CloudABI
(https://mail.python.org/pipermail/python-dev/2016-July/145708.html) provides
support for kqueue(). Its implementation, however, is far more limited. It can
only be used for polling on descriptors (EVFILT_READ
New submission from Ed Schouten:
In issue 28067, we changed _datetimemodule to stop using localtime() and
gmtime(), which is nice. I actually needed such a change for CloudABI
(https://mail.python.org/pipermail/python-dev/2016-July/145708.html) which does
not provide the thread-unsafe
New submission from Ed Schouten:
Our Autoconf bits already test for the presence of the POSIX 2008
clock_gettime() and clock_getres() functions, which is nice. Still, I'd like to
make two improvements there:
1. In timemodule.c, properly guard the use of clock_getres() bits
Ed Schouten added the comment:
Hmmm... Taking a second look at my patch: I still think it's conceptually a
good idea to pursue this, but I think it may be wiser to first focus on the
bits that are strictly necessary from my side. The patch that I've posted
previously has the disadva
Ed Schouten added the comment:
It does. I can now cross build Python for CloudABI by copying importlib.h and
importlib_external.h from the native build directory to the target build
directory. Thanks!
--
___
Python tracker
<http://bugs.python.
Ed Schouten added the comment:
The nice thing is that in our case, the importlib changes are already
compatible with the native build. So yes, we can reuse the frozen module from
the native build. :-)
Ah, yes. Issue 27641 already prevents that it's cross compiled. This patch was
wr
New submission from Ed Schouten:
For CloudABI
(https://mail.python.org/pipermail/python-dev/2016-July/145708.html) we're
providing packages containing a precompiled copy of Python. As we had to make
some changes to importlib (namely to deal with directory file descriptors), we
have to
New submission from Ed Schouten:
CloudABI is a UNIX-like runtime environment that uses a capability-based
security model. As there is no support for traditional UNIX credentials (uid_t,
gid_t), its struct stat doesn't provide st_uid and st_gid.
Python can already deal with the absen
Ed Schouten added the comment:
Sure thing! Attached is an updated patch.
--
Added file: http://bugs.python.org/file44434/patch-arc4random
___
Python tracker
<http://bugs.python.org/issue27
Ed Schouten added the comment:
I think that PEP 11 also doesn't rule out changes in this area. For example,
consider the paragraph starting with the sentence "This policy does not
disqualify supporting other platforms indirectly. [...]"
Attached is a patch that accomplishes
New submission from Ed Schouten:
Python's fcntl module already provides some support for making support for file
locking optional. For example, constants like F_SETFL are only defined if
present. Unfortunately, the accompanying functions 'flock()' and 'lockf()' are
New submission from Ed Schouten:
POSIX only requires socket types SOCK_STREAM, SOCK_DGRAM and SOCK_SEQPACKET to
be present. SOCK_RAW is optional, as it is placed between [RS] tags in the
specification:
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/sys_socket.h.html
It looks like
New submission from Ed Schouten:
CloudABI is a sandboxed UNIX-like environment
(https://mail.python.org/pipermail/python-dev/2016-July/145708.html). As it
implements a security framework similar to FreeBSD's Capsicum, file system
access is only permitted by using POSIX-2008-style dire
Ed Schouten added the comment:
Believe it our not, dealing with the absence of those system calls is more
contained than you'd think. What is pretty nice about Python is that (almost)
all of the file system operations are performed through posixmodule.c. Most of
the changes in that are
Ed Schouten added the comment:
That's a very good question. One of the goals of CloudABI's C library is to
leave out definitions for things that are known not to work in the environment.
For example, our doesn't contain open(), as with our security model
(Capsicum), t
New submission from Ed Schouten:
The SCHED_* constants that are part of POSIX's are all optional:
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/sched.h.html
Python already declares the SCHED_SPORADIC constant as part of the POSIX module
optionally, depending on whether
New submission from Ed Schouten:
RFC 6093 states that applications "SHOULD NOT" make use of TCP's out-of-band
data. For this reason, CloudABI
(https://mail.python.org/pipermail/python-dev/2016-July/145708.html) does not
provide support for it. This means that its poll() functi
Ed Schouten added the comment:
I've filed the contributor form earlier today, but I suspect it still takes
some time to get processed.
The reason why the Mercurial headers were missing from the patch was because I
generated this patch from the Python 3.6.0a3 source tarball. I'll ma
New submission from Ed Schouten:
While porting Python over to CloudABI
(https://mail.python.org/pipermail/python-dev/2016-July/145708.html), we
stumbled upon a small issue that caused the build to fail.
As CloudABI is a sandboxed runtime environment, there is no support for
accessing the
New submission from Ed Schouten:
While porting Python over to CloudABI
(https://mail.python.org/pipermail/python-dev/2016-July/145708.html), we
stumbled upon a small issue that caused the build to fail.
As CloudABI is a sandboxed environment, there currently isn't any support for
modi
New submission from Ed Schouten:
While porting Python over to CloudABI
(https://mail.python.org/pipermail/python-dev/2016-July/145708.html), we
noticed that the core Python code maps ESHUTDOWN over to BrokenPipeError. This
is fine, except for the fact that ESHUTDOWN is used unconditionally
New submission from Ed Doxtator:
In the documentation for pyvenv
(https://docs.python.org/dev/library/venv.html), there is a table that shows by
platform the command required to activate a virtual environment by OS. For
Windows, the values are:
PlatformShell Command to
Changes by Ed Behn :
Added file: http://bugs.python.org/file42087/patch
___
Python tracker
<http://bugs.python.org/issue26507>
___
___
Python-bugs-list mailing list
Unsub
New submission from Ed Behn:
Currently, the default pickle protocol is used to return worker results in a
multiprocessing pool. The highest protocol should be used because backwards
compatibility is not an issue.
--
components: Extension Modules
files: patch
messages: 261318
nosy
New submission from Ed Schouten:
While trying to port Python over to a new platform (CloudABI), I noticed a
couple of compiler errors in PyThread_create_key(), PyThread_delete_key(),
PyThread_delete_key_value() and PyThread_set_key_value() caused by fact that
pthread_key_t is converted to an
Changes by Ed Maste :
--
nosy: +emaste
___
Python tracker
<http://bugs.python.org/issue24520>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Ed Maste added the comment:
I believe the 0-based vs 1-based history is only one of a few different
inconsistencies between libedit and readline. Workarounds will be necessary
until a fixed libedit is deployed on all operating systems / distros of
interest, but yes I agree that eventually
Ed Maste added the comment:
Actually, in msg245395 I should claim the issue is with libedit / GNU readline
compatibility and/or the workarounds in Python's readline module, not that it's
specifically Issue24388.
--
___
Python trac
Ed Maste added the comment:
It looks like rust developers hit the issue in Issue24388 with lldb on Ubuntu
15.04 as well: https://github.com/rust-lang/rust/issues/26297
--
___
Python tracker
<http://bugs.python.org/issue13
Ed Maste added the comment:
Note that the patch in Issue24388 is more a proof of concept. I'm not sure it's
the "right" fix.
LLDB is a bit of a special case: LLDB links against libedit, but the Python
libedit module is built as if readline is in use. It turns out this &q
Ed Maste added the comment:
This issue causes the LLDB debugger to crash on FreeBSD (it uses Python as its
embedded script interpreter).
What needs to be done to make some progress on this issue?
--
___
Python tracker
<http://bugs.python.
Ed Maste added the comment:
Presumably the #ifdefs ought to just be deleted though, relying on the runtime
detection of libedit compatibility issues on any platform.
--
___
Python tracker
<http://bugs.python.org/issue24
New submission from Ed Maste:
I encountered a segfault in Python's call_readline from LLDB on FreeBSD, with
libedit. There is a fix for this issue already in readline.c, but under #ifdef
__APPLE__
Backtrace:
(lldb) target create "/data/emaste/src/llvm/build/bin/lldb" --core
&
Ed Maste added the comment:
For reference, this fd leak was causing one of LLDB's tests to fail. It is now
marked XFAIL pending a resolution of this issue:
http://llvm.org/viewvc/llvm-project?view=revision&revision=229704
Linux is also affected, the Linux LLDB tests were previously r
Changes by Ed Maste :
--
nosy: +Ed.Maste
___
Python tracker
<http://bugs.python.org/issue23458>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Ed Sesek:
See the attached config file. logging.config.fileConfig() is attempting to
write to the file specified in the file_handler section even though that
handler is not configured for use in this config. If its going to write to the
file, it should only do so if the
Ed Morley added the comment:
Meant to add: the ActivePython release does this already - but it would be
great if upstream did too.
--
___
Python tracker
<http://bugs.python.org/issue21
New submission from Ed Morley:
A python.org 2.7.6 release of the Windows MSI installer, results in only the
following python binaries in the installation directory:
C:\Python27\python.exe
C:\Python27\pythonw.exe
In Mozilla bug https://bugzilla.mozilla.org/show_bug.cgi?id=957721 we would
like
Changes by Ed Campbell :
--
nosy: +esc24
___
Python tracker
<http://bugs.python.org/issue11445>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ed Campbell added the comment:
I think this is a real improvement. Thanks. I have a few comments:
I suspect you know this, but the rendering problem occurs because of the call
to curses.endwin() in tearDown(). I experimented with delaying this until
teadDownClass() but this led to even more
Changes by Ed Maste :
--
nosy: +Ed.Maste
___
Python tracker
<http://bugs.python.org/issue15745>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ed Campbell :
--
nosy: +esc24
___
Python tracker
<http://bugs.python.org/issue15730>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ed Campbell :
--
nosy: +esc24
___
Python tracker
<http://bugs.python.org/issue17128>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ed Campbell :
--
nosy: +esc24
___
Python tracker
<http://bugs.python.org/issue10544>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ed Campbell :
--
nosy: +esc24
___
Python tracker
<http://bugs.python.org/issue16848>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ed Campbell :
--
nosy: +esc24
___
Python tracker
<http://bugs.python.org/issue15663>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ed Campbell :
--
nosy: +esc24
___
Python tracker
<http://bugs.python.org/issue16773>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ed Campbell added the comment:
I'd suggest using unittest.TestCase.assertRaises() as a context manager to
remove some try-excepts. For example I think function
test_userptr_without_set() on line 245 could use:
with self.assertRaises(curses.panel.error):
p.userptr()
I could create a
Changes by Ed Wodrich :
--
nosy: -ewodrich
___
Python tracker
<http://bugs.python.org/issue14735>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Ed Wodrich :
Greetings,
I am a brand new user attempting to learn Python. I downloaded and installed
the .msi installer version 3.2.3 on May 5, 2012. I am running Windows XP SP2
32-bit on a Pentium 4. I opted to load all features of the program.
Installation finished
New submission from Ed Plese :
Both Linux and Solaris define uid_t and gid_t as unsigned integers. The
pwd and grp modules cast these to signed long values that are then
converted with PyInt_FromLong. For large values, greater than 2 ** 32 -
1, the result is correct when Python is compiled as
Changes by Ed Summers <[EMAIL PROTECTED]>:
--
nosy: +edsu
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1544339>
___
___
Python
New submission from Ed Vinyard:
In the email module example, email-unpack.py
(http://docs.python.org/lib/email-unpack.txt), line 56 throws an
AttributeError. It is currently
ext = mimetypes.guess_extension(part.get_type())
I think this line should be
ext = mimetypes.guess_extension
78 matches
Mail list logo
