R. David Murray added the comment:
Thanks, Martin and Demian. I tweaked the patch slightly before commit, so I've
uploaded the diff. After thinking about it I decided that it does indeed make
sense that the new exception subclass both ConnectionResetError and
BadStatusLine, exactly because
Cyd Haselton added the comment:
Latest error:
gcc --sysroot=/usr/gcc-4.9.2/sysroot -c -Wno-unused-result -Wsign-compare
-Wunreachable-code -DNDEBUG -g -O3 -Wall -Wstrict-prototypes
-Werror=declaration-after-statement -I. -IInclude -I./Include
-DPy_BUILD_CORE -o
Marc-Andre Lemburg added the comment:
On 05.04.2015 23:25, R. David Murray wrote:
MAL: then what you are arguing for is that the SSL changes in 2.7.9 should
not have happened. Which is an argument that Antoine and I at least are
sympathetic to :)
I think those changes were probably
R. David Murray added the comment:
Actually I was in favor of an environment variable (or something like that)
from the start, because it could be set per-process (making it as close to
per-application as we can get from upstream). But a global config file I think
is a bad idea (at least in
Roundup Robot added the comment:
New changeset eba80326ba53 by R David Murray in branch 'default':
#3566: Clean up handling of remote server disconnects.
https://hg.python.org/cpython/rev/eba80326ba53
--
nosy: +python-dev
___
Python tracker
On 05.04.2015 22:49, Donald Stufft wrote:
Donald Stufft added the comment:
I don't consider monkey patching a proper way to configure a Python
installation.
The point is that that TLS validation on/off isn't conceptually a Python level
configuration option, that's going to be a per
polynice is a nice(1)-like command line utility for unix systems to
throttle long running processes beyond what can be achieved by nice(1),
by repeatedly suspending and resuming the process.
It is written for python3, though there is some python2.7 compatibility.
Author:
Radovan Garabík
URL:
Sepideh Ghanavati sepideh...@gmail.com writes:
I know basic of python and I have an xml file created from csv
What XML schema defines the document's format?
Without knowing the schema, parsing will be unreliable.
What created the document? Why is it relevant that the document was
“created
On 05Apr2015 12:20, Daniel Ellis ellis...@gmail.com wrote:
I have a small little tool I'd like to make. It essentially takes piped input,
modifies the text in some way, and immediately prints the output. The problem
I'm having is that any output I pipe to the program seems to be buffered,
On Mon, 6 Apr 2015 06:38 am, Dave Hein wrote:
I would like to distribute a python package with different code for
Python 2.* than for Python 3.*. (Mostly this is because of different
unicode string handling).
There is nothing in to setuptools or PyPi that directly supports
this scenario.
On 05/04/2015 21:38, Dave Hein wrote:
I would like to distribute a python package with different code for
Python 2.* than for Python 3.*. (Mostly this is because of different
unicode string handling).
There is nothing in to setuptools or PyPi that directly supports
this scenario.
But perhaps
Donald Stufft added the comment:
I don't consider monkey patching a proper way to configure a Python
installation.
The point is that that TLS validation on/off isn't conceptually a Python level
configuration option, that's going to be a per application configuration
option. The monkeypatching
Cyd Haselton added the comment:
issue_20306.patch won't install; attempting to do so yields the following:
patching file configure.ac
Hunk 56 FAILED 4944/4944.
AC_MSG_RESULT($ENSUREPIP)
AC_SUBST(ENSUREPIP)
R. David Murray added the comment:
MAL: then what you are arguing for is that the SSL changes in 2.7.9 should not
have happened. Which is an argument that Antoine and I at least are
sympathetic to :)
--
___
Python tracker
On Sun, 05 Apr 2015 12:20:48 -0700, Daniel Ellis wrote:
This only seems to print from the parent process. I read that I need to
do the os.read call for the fork to happen. I've also tried printing
*after* the os.read call.
The child process has its std{in,out,err} attached to the
Changes by Berker Peksag berker.pek...@gmail.com:
--
stage: needs patch - resolved
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18553
___
___
Sepideh Ghanavati schrieb am 06.04.2015 um 04:26:
I know basic of python and I have an xml file created from csv which has
three attributes category, definition and definition description.
I want to parse through xml file and identify actors, constraints,
principal from the text. However, I am
Dave Hein schrieb am 05.04.2015 um 22:38:
I would like to distribute a python package with different code for
Python 2.* than for Python 3.*. (Mostly this is because of different
unicode string handling).
There is nothing in to setuptools or PyPi that directly supports
this scenario.
But
Raymond Hettinger added the comment:
This seems like a reasonable intermediate step.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23870
___
Changes by Terry J. Reedy tjre...@udel.edu:
--
superseder: - IDLE: Ability to run 3rd party code checkers
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18704
___
Hi,
I know basic of python and I have an xml file created from csv which has three
attributes category, definition and definition description. I want to
parse through xml file and identify actors, constraints, principal from the
text. However, I am not sure what is the best way to go. Any
Thanks, got the python bit down is just the Web for flask and django. Getting
the templates and snippets to work in a good flow is where I am looking for
advice.
Cheers
Sayth
--
https://mail.python.org/mailman/listinfo/python-list
FWIW: I just ran into a situation where the new approach resulted
in pip, setuptools and zc.buildout not working anymore.
This was on an AIX system which did come with CA root certificates
at all.
Now, I knew how to fix this, but the solution was not
an obvious one. I had to use truss to figure
Antoine Pitrou added the comment:
This was on a system where Python 2.7.3 had been installed
previously. After the upgrade to Python 2.7.9 nothing worked
anymore.
Who did the upgrade and with which binaries?
If you're compiling Python from source, especially for an exotic system, well,
Changes by Benjamin Peterson benja...@python.org:
--
versions: -Python 2.7
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23872
___
___
Roundup Robot added the comment:
New changeset cc2c7aa2d7a6 by Benjamin Peterson in branch '3.4':
fix extended command syntax (closes #23872)
https://hg.python.org/cpython/rev/cc2c7aa2d7a6
New changeset 2c89c1c34e19 by Benjamin Peterson in branch 'default':
merge 3.4 (#23872)
Nick Coghlan added the comment:
PEP 476 *has* a mechanism in it that was supposed to deal with this problem,
thus leaving *end users* in full control of the decision on when they upgrade
their security infrastructure rather than having that decision arbitrarily
imposed on them by a vendor or
Antoine Pitrou added the comment:
weakrefs are traditionally cleared by the cyclic GC before calling any __del__
method. This used to be mandatory to eschew situations where a weakref callback
could see cleared objects, but produces the side effect that __del__ methods
can see dead weakrefs.
Antoine Pitrou added the comment:
Concretely, the possible workarounds are:
- don't do anything complex in your __del__
- be prepared to deal with unexpected errors in your __del__
- starting from Python 3.4, don't define __del__ and use weakref.finalize()
instead:
Cyd Haselton added the comment:
Hey Ryan,
Just now patching downloaded/unzipped tip and was wondering if there was an
order in which patches should be applied.
I ask because i'm getting the following when applying the
android_segfault_fix.patch
/bld/python/cpython-3.4/cpython-3.4/Python $
Cyd Haselton added the comment:
UPDATE: I found the file in github, under master, in Python/. It's not in the
3.4 or origin/3.4 branches...aren't we working on those? Or does it not matter?
--
___
Python tracker rep...@bugs.python.org
Ryan Gonzalez added the comment:
I thought this was for the tip, i.e. the 3.5 dev...?
But I created the patches in the order that I wrote the descriptions in the
comment. So you might want to use that order.
If that fails, I can figure out the revision I was at when I created the
patches.
Serhiy Storchaka added the comment:
Here is reworked patch for the _codecs module. No optional groups are used, all
parameters have sensible defaults. Default encoding is utf-8, default errors
is strict or None (if function accepts None), default mapping is None.
Unified names and coding
Antti Haapala added the comment:
well, they wouldn't and shouldn't behave like range. range is a sequence
whereas count or repeat wouldn't necessarily be sequences. (they can be
infinite and thus not having length). And the count shouldn't be *reiterable*
because that is why it exists
Serhiy Storchaka added the comment:
Updated patch. Converted __init__ methods and removed explicit declarations of
self parameters. SubElement and Element.__init__ still are not converted, as
they need the support of **kwargs.
--
Added file:
Antoine Pitrou added the comment:
By the way, if a vendor wants vendor-specific behaviour, forking the standard
library is a normal price to pay.
(in this case, the diff wouldn't be large, and it's made against an extremely
stable upstream branch)
--
Changes by Serhiy Storchaka storch...@gmail.com:
--
nosy: +rhettinger
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23871
___
___
Python-bugs-list
Donald Stufft added the comment:
On it's own I think this switch is a bad idea because it's too big of a hammer.
Someone shouldn't accidentally disable TLS verification in pip for instance
because they wanted to disable TLS verification for some random tool that only
hit internal TLS but
Nick Coghlan added the comment:
The discussion isn't on python-ideas yet because I wanted to get a better sense
of what might be politically feasible before putting this question to a broader
audience. I agree it needs to move there eventually (likely during or after
PyCon), and will almost
Nick Coghlan added the comment:
As far as Alex's post goes, it's simply wrong, and I wish he had spoken to me
about his frustrations with the significant challenges of infrastructure
maintenance in large established organisations before posting it. Red Hat's
been fighting the battle for
Armin Rigo added the comment:
The PyArg_ParseTuple() size arguments should be of type Py_ssize_t instead of
int.
--
nosy: +arigo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23830
___
Antoine Pitrou added the comment:
Le 05/04/2015 12:25, Nick Coghlan a écrit :
This does mean spending more time upfront coming up with a way of
designing the feature that the core development community considers to
be useful independently of backporting considerations (e.g. bringing the
Tom Tanner added the comment:
Any chance to get this into 2.7.10?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21114
___
___
Python-bugs-list
Tom Tanner added the comment:
Are you going to merge it into 2.7.10?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21718
___
___
Donald Stufft added the comment:
Now, I knew how to fix this, but the solution was not
an obvious one. I had to use truss to figure out where OpenSSL
was looking for certificates and the added the Mozilla cert
bundle from our egenix-pyopenssl package to make things work
again.
You also
On 04/05/2015 01:45 PM, Alexey Izbyshev wrote:
Hello!
I've hit a strange problem that I reduced to the following test case:
* Run several python processes in parallel that spin in the following loop:
while True:
if os.path.isfile(fname):
with open(fname, 'rb') as f:
f.read()
Cyd Haselton added the comment:
From previous post:
**
How does this sound?
* I'll clone the fork of the 3.4 branch I made in github, build and patch.
* Ryan will (as best as he can) grab said patches, regenerate them for the bug
tracker or forward port them to 3.5 (in
Hello!
I've hit a strange problem that I reduced to the following test case:
* Run several python processes in parallel that spin in the following
loop:
while True:
if os.path.isfile(fname):
with open(fname, 'rb') as f:
f.read()
break
* Then, run another process that creates a
On Mon, Apr 6, 2015 at 3:45 AM, Alexey Izbyshev izbys...@ispras.ru wrote:
The test case is attached, the main file is test.bat. Python is expected to
be in PATH. Stderr of readers is redirected to *.log. You may need to run
several times to hit the issue.
You have an interesting-looking
Gregory P. Smith added the comment:
This was fixed in 3.4.1:
https://hg.python.org/cpython/log/094615256a54/Lib/lib2to3/Grammar.txt
i'm leaving this open to update the devguide.
--
___
Python tracker rep...@bugs.python.org
Marc-Andre Lemburg added the comment:
On 05.04.2015 18:28, Donald Stufft wrote:
Donald Stufft added the comment:
Now, I knew how to fix this, but the solution was not
an obvious one. I had to use truss to figure out where OpenSSL
was looking for certificates and the added the Mozilla
I have a small little tool I'd like to make. It essentially takes piped input,
modifies the text in some way, and immediately prints the output. The problem
I'm having is that any output I pipe to the program seems to be buffered,
removing the desired effect.
From what I understand, I need
Antoine Pitrou added the comment:
Le 05/04/2015 21:26, Marc-Andre Lemburg a écrit :
But this is only an example of an application not working anymore
because the system's OpenSSL could not verify certificates.
In this case, no root CA certs were available. On older systems
with proper root
Marc-Andre Lemburg added the comment:
On 05.04.2015 21:36, Antoine Pitrou wrote:
And you want the python-dev community to care for that broken
situation by bearing the cost of additional maintenance and security
risk in implementing the new configuration options?
No, I want to be able to
Donald Stufft added the comment:
No, I want to be able to easily disable the newly added
checks in 2.7.9+ to get systems such as these behave the
same as with 2.7.8, since without this option, people
using these system are going to be forced to stick with
buggy 2.7.8 systems.
Why is the
R. David Murray added the comment:
I agree with Antti. If Raymond disagrees he can reopen :)
(There is a reason it is called *iter*tools. As Antti says, range is
documented as being a *sequence* type.)
--
nosy: +r.david.murray
resolution: - rejected
stage: - resolved
status: open
Marc-Andre Lemburg added the comment:
On 05.04.2015 21:48, Donald Stufft wrote:
Donald Stufft added the comment:
No, I want to be able to easily disable the newly added
checks in 2.7.9+ to get systems such as these behave the
same as with 2.7.8, since without this option, people
using
On 4/5/2015 1:45 PM, Alexey Izbyshev wrote:
Hello!
I've hit a strange problem that I reduced to the following test case:
* Run several python processes in parallel that spin in the following loop:
while True:
if os.path.isfile(fname):
with open(fname, 'rb') as f:
f.read()
R. David Murray added the comment:
Really these arguments make it sound like 2.7.9 never should have happened.
Given that it did, Nick has not addressed the question of why the vendors
maintaining this simple patch (given that it addresses what he sees as their
need) is not a viable option.
R. David Murray added the comment:
It looks to me like a patch that could be merged as a bug fix.
--
stage: - commit review
versions: +Python 2.7, Python 3.4, Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21718
I would like to distribute a python package with different code for
Python 2.* than for Python 3.*. (Mostly this is because of different
unicode string handling).
There is nothing in to setuptools or PyPi that directly supports
this scenario.
But perhaps there could be some script run at install
61 matches
Mail list logo
