New submission from Vova:
At my workplace I have to use corporate Internet proxy server with
AD/domain/ntlm authorization. I use local cntlm proxy server to authorize
myself on corporate proxy. Programs are send requests to cntlm proxy without
any authorization information. Cntlm proxy
Paul Ianas added the comment:
Sure, it is your call. As said, this is rather an enhancement.
Still, if I were to decide, I would chose:
1. not to break the API = raise IndexError instead of ValueError in case hi
is invalid.
2. to protect against illegal values: as said, if hi 0 bisect_*
Robert Collins added the comment:
A few thoughts.
Adding a new public symbol seems inappropriate here: this is a performance
issue that is well predictable and we should cater for that (given difflibs
current performance).
I'll note in passing that both bzr and hg have much higher
New submission from Akira Li:
The patch for Issue #21075: fileinput.FileInput now reads bytes from standard
stream if binary mode is specified broke code that used
sys.stdin = sys.stdin.detach() with FileInput(mode='rb') in Python 3.3
I've attached the patch that makes FileInput to accept
Robert Collins added the comment:
Just to note that unittest2 tip (unreleased)had michaels proposed fix, which is
different to that here. I'm going to back that out before doing a release,
because they should be harmonisious.
--
nosy: +rbcollins
Robert Collins added the comment:
My take on this, FWIW, is that any methods in the under-test API - setUp,
tearDown, test_* and anything registered via addCleanup should all support the
same protocol as much as possible, whatever it is.
That is, raising a skip in setUp should skip the test.
Nick Coghlan added the comment:
While I agree with Robert's comments in general, the main question to be
resolved here is the scope of the expectedFailure decorator.
Yes, it's applied specifically to the test execution phase when writing the
code, but the question is how the following
Robert Collins added the comment:
I'd argue for
- An error - its not covered by the decorator.
- An error - the last two are not covered by the decorator.
- An error - the last two are not covered by the decorator.
- An error - the exception isn't a 'failure' [today - we should revisit this
New submission from David Barnett:
doctests includes special exception processing support (described in
https://docs.python.org/3/library/doctest.html#what-about-exceptions), but in
python3 it seems to print the fully-qualified class name even for exception
classes in the same module, which
Serhiy Storchaka added the comment:
The code
sys.stdin = sys.stdin.detach()
is incorrect because sys.stdin should be text stream, but detach() returns
binary stream.
--
nosy: +serhiy.storchaka
___
Python tracker rep...@bugs.python.org
Serhiy Storchaka added the comment:
Here are updated patches for 3.5 (using subprocess) and 3.4 (using os.popen)
which addresses Victor's comments.
--
Added file: http://bugs.python.org/file36998/uuid_netstat_getnode-3.5_2.patch
Added file:
James added the comment:
I've written several languages, I'm no novice but, I also know when to brush
up.Its just how I started, it looks like an opening for others.
-Original Message-
From: R. David Murray
Sent: Wednesday, October 22, 2014 6:25 AM
To: geek.mo...@gmail.com
Subject:
Akira Li added the comment:
It is incorrect that sys.stdin is *always* a text stream. It often is,
but not always.
There are cases when it is not e.g.,
$ tar zcf - stuff | gpg -e | ssh user@server 'cat - stuff.tar.gz.gpg'
tar's stdout is *not* a text stream.
gpg's stdin/stdout are *not*
Serhiy Storchaka added the comment:
It is incorrect that sys.stdin is *always* a text stream. It often is,
but not always.
There are cases when it is not e.g.,
$ tar zcf - stuff | gpg -e | ssh user@server 'cat - stuff.tar.gz.gpg'
tar's stdout is *not* a text stream.
gpg's
Akira Li added the comment:
This is not related to Python. Terms character, string, text, file
can have different meaning in different domains. In Python we use Python
terminology. There is no such thing as sys.stdin in Posix-compatible shell,
because Posix-compatible shell has no the sys
New submission from Antoine Pitrou:
I just noticed that access to the normal distutils docs has become difficult.
They are hidden as legacy while a link to the packaging user guide
(https://packaging.python.org/en/latest/) is prominently displayed.
The problem is that the packaging user guide
Ivan Pozdeev added the comment:
Here's the warnings patch. No sure if the `copy.copy' recipe is officially
supported.
--
nosy: +native_api
Added file: http://bugs.python.org/file37000/add-warnings.diff
___
Python tracker rep...@bugs.python.org
Sigz added the comment:
Ok seems you were right, I was not applying any locale, forcing to
locale.setlocale(locale.LC_ALL, 'en_US.utf8') resolved the issue.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22690
Changes by Sigz d...@sgzdev.net:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22690
___
___
Python-bugs-list mailing
R. David Murray added the comment:
I actually agree that this should be applied not only for backward
compatibility reasons, but because it is better duck typing. It unfortunately
leaves code still having to potentially deal with if python version is 3.4.1
or 3.4.2, but there is nothing that
R. David Murray added the comment:
I agree with Robert. I'd rather get notified of a failure in the cleanup...if
the test is an *expected* failure, then its cleanup should be designed to
succeed when the test fails; anything else would be a bug in the design of the
test, IMO.
--
R. David Murray added the comment:
See issue 21224 and issue 9740. It's not 100% clear to me from reading those
issues, but it *sounds* like the support is there, you just have to turn it on.
So I'm closing this issue as not a bug...either it already works (and you just
have to set your
Nick Coghlan added the comment:
The old distutils docs are actively wrong in some areas, which is why they have
been moved from their previous location.
They can't be deleted yet because they contain info that needs to be moved to
either the distutils module docs, the setuptools docs, or the
Antoine Pitrou added the comment:
The old distutils docs are actively wrong in some areas
Yet they are actively useful in others.
--
resolution: rejected -
status: closed - open
___
Python tracker rep...@bugs.python.org
R. David Murray added the comment:
It is not possible to work around it with ELLIPSIS. Look for the flag
'IGNORE_EXCEPTION_DETAIL', which is mentioned in the section you reference.
--
nosy: +r.david.murray
resolution: - not a bug
stage: - resolved
status: open - closed
Saimadhav Heblikar added the comment:
Would like to check if a tooltip would be appropriate for this?
If yes, I would like to work on it.
--
nosy: +sahutd
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22705
Nick Coghlan added the comment:
For reference, issue #19407 covered the PEP 453 docs updates.
I tried fixing them in place, and judged it utterly impractical to do so -
moving them out of the way, but keeping them available (including via existing
deep links) was the resulting compromise.
If
Martijn Pieters added the comment:
I'd say this is a bug in the library, not the documentation. The library varies
the output type, making it impossible to use `json.dump()` with a `io.open()`
object as the library will *mix data type* when writing. That is *terrible*
behaviour.
--
Antoine Pitrou added the comment:
Ok, can you stop closing this issue?
I tried fixing them in place, and judged it utterly impractical to do so
Why?
If you're prepared to help extract the needed data, great, but putting them
back where they were is *not* going to happen.
Why?
--
David Barnett added the comment:
But… that doesn't help. It completely changes the semantics of the doctests. I
have a bunch of doctests demonstrating different failures of the same exception
class, and with IGNORE_EXCEPTION_DETAIL running my doctests to verify they're
still correct is next
R. David Murray added the comment:
Not to 2.7, since that would be a new feature.
In Python we do not consider the content of an error message (as opposed to the
exception class itself) to be part of the API, so it is not surprising that
doctest does not really support checking it across
Terry J. Reedy added the comment:
The revised doc admits the problem: If *ensure_ascii* is False, some chunks
written to *fp* may be unicode instances. Unless fp.write() explicitly
understands unicode (as in codecs.getwriter) this is likely to cause an error.
Making text be unicode in 3.x is
Dmitry Kazakov added the comment:
I think the reason this patch hasn't been discussed well is that it only
changes the behavior for traceback.*_tb functions that only deal with
tracebacks. I commented on the review page that we don't have to change the
behavior of traceback.*_stack functions
R. David Murray added the comment:
More likely the lack of discussion is just that Serhiy is busy :)
Breaking code is to be avoided if possible. Can you give an example of the
cosmetic change?
I haven't fully reviewed the patch, but a more meaningful name than 'condition'
might make the
New submission from zodalahtathi:
Python 3.4 added a 'input' argument to the subprocess.check_output function to
send bytes to stdin, but it was surprisingly not added to other subprocess
helpers.
The same functionality should be added to subprocess.check_call and
subprocess.call.
New submission from Garry Smith:
Problem with print()
I did the following by accident while in the python console, print = 10, which
it let me do, to horror.after that I could not use the print() command without
getting the following error:-
Traceback (most recent call last):
File stdin,
Charles-François Natali added the comment:
Adding ioctl constants is fine.
However, I think that if we do this, it'd be great if we could also
expose this information in a module (since psutil inclusion was
discussed recently), but that's probably another issue.
--
Georg Brandl added the comment:
This is as expected; the new global name print overrides the builtin name
print.
(What you could also have done to remove your binding is del print, which
removes the global binding.)
--
nosy: +georg.brandl
resolution: - not a bug
status: open -
Serhiy Storchaka added the comment:
I agree with Martin and Lars, this issue is not so easy at looks at first
glance.
For ZIP files we should distinct two different operations.
1. Remove the entry from the central directory (and may be mark local file
header as invalid if it is possible).
R. David Murray added the comment:
call and check_call are designed as APIs that do *not* manage the standard
streams of the commands called. If you want to manage the streams, either use
check_output or Popen directly.
Internally, call and check call do *not* use communicate, and it is
Serhiy Storchaka added the comment:
Last patch is more complicated and needs more time to review.
I suppose the code would be more clear if split _extract_tb_or_stack_iter() to
parts. One generator just generates (filename, lineno, name, f.f_globals)
tuples. Then these tuples either handled
Michael Ohlrogge added the comment:
This is my first time posting here, so apologies if I'm breaking rules.
I'd like to put in a vote in favor of this patch to get the matching scores.
I am a researcher at Stanford University using this tool to match up about
100,000 different names of
zodalahtathi added the comment:
I think the 'stdin argument can be any file like or stream for all subprocess
functions' approach would be the best solution, because it is misleading to
differentiate behavior based on internal implementation details (the use of
communicate), when the function
Serhiy Storchaka added the comment:
Then I'm closing this issue.
--
resolution: - rejected
stage: - resolved
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22712
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Regular Expressions
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22594
___
___
Antoine Pitrou added the comment:
Thank you! The patch looks good to me, I'm going to apply it.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13918
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Regular Expressions
priority: normal - low
stage: needs patch - patch review
versions: +Python 3.5 -Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7940
Roundup Robot added the comment:
New changeset e5ad1f27fb54 by Antoine Pitrou in branch 'default':
Issue #22676: Make the pickling of global objects which don't have a __module__
attribute less slow.
https://hg.python.org/cpython/rev/e5ad1f27fb54
--
nosy: +python-dev
Antoine Pitrou added the comment:
Done. Thank you for your contribution!
--
resolution: - fixed
stage: patch review - resolved
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13918
Roundup Robot added the comment:
New changeset aee097e5a2b2 by Antoine Pitrou in branch 'default':
Issue #13918: Provide a locale.delocalize() function which can remove
https://hg.python.org/cpython/rev/aee097e5a2b2
--
nosy: +python-dev
___
Python
STINNER Victor added the comment:
+:const:'LC_NUMERIC`settings.
a space is missing before settings, no?
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13918
___
Antoine Pitrou added the comment:
Now applied. As Georg said, though, the definitive fix is to add a __module__
attribute to your global objects.
--
resolution: - fixed
stage: needs patch - resolved
status: open - closed
___
Python tracker
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Regular Expressions
versions: +Python 3.4, Python 3.5 -Python 3.1
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10076
___
Antoine Pitrou added the comment:
Ah, right, thank you.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13918
___
___
Python-bugs-list mailing
Georg Brandl added the comment:
And the first quote is wrong.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13918
___
___
Python-bugs-list
Michael Ohlrogge added the comment:
Another way the scores could be useful would be to write an algorithm that
would give you a number of possible answers based on the scores that you get.
In other words, for example, perhaps if one of the possible matches has a score
about .9, then it would
Changes by Berker Peksag berker.pek...@gmail.com:
--
nosy: +berker.peksag
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7559
___
___
Nick Coghlan added the comment:
No, I won't stop closing this issue, because reverting to advertising the
legacy installation and distribution docs through a top level docs home page
link is *never going to happen* (although I'll note again that direct links
into the legacy docs have been
Changes by Berker Peksag berker.pek...@gmail.com:
--
stage: patch review - resolved
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22592
___
___
Changes by Berker Peksag berker.pek...@gmail.com:
--
nosy: +berker.peksag
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22695
___
___
Antoine Pitrou added the comment:
Surely, if you think you are right, you can still wait for the discussion to
happen without aggressively trying to shut it down.
Besides, you are not the docs dictator, nor the distutils maintainer. We are a
community, this isn't your private territory.
If
Robert Collins added the comment:
Oh, I got a profile from the test case for my own interest.
6615 seconds ..
some highlights that jumped out at me
200010.1270.000 6610.0250.330 difflib.py:868(compare)
which means we're basically using ndiff, which is cubic rather than
Robert Collins added the comment:
Thanks for the review, updated patch here - I'll let this sit for a day or two
for more comments then commit it Monday.
--
Added file: http://bugs.python.org/file37002/issue7559.patch
___
Python tracker
Terry J. Reedy added the comment:
I was originally thinking of displaying 'option-help' beside a read-only text
widget containing the value, just under the enable key-value pairs. But I can
imagine that tooltips attached to the label (on the left) might be a better
alternative. This would
Terry J. Reedy added the comment:
For Idle preferences, a Help text could list options that do not take effect
immediately. For extensions, there should be an indication in an extension's
option-help (#22705).
--
___
Python tracker
New submission from Van Ly:
The target points to within '__import__()' but should point to 'import()'
method function.
For example,
# 'import statement' entry at index for 'i' on the following page
python-2.7.5-docs-html/genindex-I.html
# points to
Vova added the comment:
The issue http://bugs.python.org/issue21224 is about http server
implementations. The issue http://bugs.python.org/issue9740 is more relevant
for what I talking about, but not exactly.
Look, in this line
67 matches
Mail list logo
