New submission from vladimir :
This program:
class t( object):
def __init__(self,ime,param1=[],param2=[]):
print "+++init+++"
print "ime = ",ime
print "param1 = ", param1
print "param
vladimir added the comment:
On Sat, Aug 28, 2010 at 12:34 AM, Georg Brandl wrote:
changes parameter value. It' would be understandable, as exmple in
documentation with acumulating value of L, that changing parameter in side
class affect default
value in next call. But this is out of
vladimir added the comment:
On Sat, Aug 28, 2010 at 10:24 PM, Benjamin Peterson
wrote:
>
> Benjamin Peterson added the comment:
>
> Rest assured: it's expected behavior.
>
> Thank you for your cooperation.
--
Added file: http://bugs.pytho
New submission from Vladimir :
I have problem to run pyc file on one machine with Ubuntu Server 18.04.4 LTS.
This is my source code of the file:
#!/root/PycharmProjects/Project/venv/bin/python3.7
print("Hi")
When I compile it in python console with commands:
import
New submission from Vladimir:
After update python2.7-pyopenssl-0.13.1-1 to python2.7-pyopenssl-0.14-1 i have
this error on opening deluge. Packpage downgrade solv problem.
OS: Archlinux
/usr/lib/python2.7/site-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could
not open display
New submission from Vladimir Feinberg :
I have a request related to the rejected proposal
(https://bugs.python.org/issue43255) to introduce a ceildiv operator.
I frequently find myself wishing for a ceildiv function which computes
`ceil(x/y)` for integers `x,y`. This comes up all the time
Vladimir Feinberg added the comment:
Mark, I will say I'm pretty sympathetic to the feature-bloat avoidance
perspective here, and if the outcome here is to improve docs, that's still
a win, I think.
That said, since this thread will become precedent, and I think
`math.ceildiv` is t
New submission from Vladimir Vinogradenko :
If an exception occurs in ProcessPoolExecutor work item, all the exception
frame local variables are not garbage collected (or are garbage collected too
lately) because they are referenced by the exception's traceback.
Attached file is a test
Vladimir Konjkov added the comment:
look this
http://www.mail-archive.com/python-bugs-list%40python.org/msg07749.html
it's for python-2.3.5 under qnx4.25.
about pyport.h under qnx4.25:
I include "unix.h" instead of definition of function
openpty()+forkpty() in pyport.h, op
Vladimir Konjkov added the comment:
However, I don't understand this entire point: What do you mean by
"using TCGETA requires that struct termio be defined"? How is TCGETA
defined to produce such a dependency? TCGETA is a
Vladimir Konjkov added the comment:
addition
TCGETA is a constant. That's right!
under QNX4 TCGETA defined as MACRO in . That's right!
in Modules/termios.c there's
#include
That's right too!
What's problem after all?
Problem is that MACRO definition of TCGETA need size
New submission from Vladimir M. :
The page at (http://docs.python.org/reference/datamodel.html) says:
"In x * y, if one operator is a sequence that implements sequence repetition".
Obviuosly, it should be changed to:
"In x * y, if one operand is a sequence that implements sequ
New submission from Vladimir Rutsky :
There is a typo in urllib module documentation: missing space after dot at
sentence end. Please see attached path for details.
--
assignee: docs@python
components: Documentation
files: urllib-typo-space-after-dot.patch
keywords: patch
messages
Changes by Vladimir Dmitriev :
--
components: Library (Lib), Windows
files: mime content types.reg
nosy: vldmit
priority: normal
severity: normal
status: open
title: UnicodeDecodeError in mimetypes.guess_type on Windows
type: behavior
versions: Python 2.7
Added file: http
New submission from Vladimir Dmitriev :
Windows 7, Python 2.7
Some windows applications (QuickTime) add content-types to Windows registry
with non-ascii names. mimetypes in unaware of that and fails with
UnicodeDecodeError:
>>> mimetypes.guess_type('test.js')
Traceback (mo
Vladimir Iofik added the comment:
Here is a better patch.
--
nosy: +vj
Added file: http://bugs.python.org/file19332/9291a.patch
___
Python tracker
<http://bugs.python.org/issue9
Vladimir Iofik added the comment:
UnicodeDecodeException is thrown because 'ctype' is already a string,
so it is first implicitly decoded by default encoder (which is 'ascii') and
then reencoded back. I see no reason in all these actions, so I simply removed
them. I think
New submission from Vladimir Rutsky :
There is a typo in argparse module documentation:
"The ``nargs`` keyword argument associates a different number of command-line
arguments with a single action.." (two dots at end).
Patch based on official http://svn.python.org/projects/python/bra
New submission from Vladimir Rutsky :
In Python 2.7 and 3 branch at
http://svn.python.org/projects/python/branches/py3k/ file
Doc/library/argparse.rst has incorrectly formatted list at line 648:
> * ``'store'`` - This just stores the argument's value. This is the defaul
New submission from Vladimir Rutsky :
There is missed dot at end of sentence in argparse module documentation. Please
see attached patch for details.
Patch based on official http://svn.python.org/projects/python/branches/py3k/
repository, but typo is also noted in Python 2.7 documentation
New submission from Vladimir K :
The following code (see attached file) was intended to remove chr(13) from
end-of-lines under Windows to make the file Unix-compliant but it always
appends chr(13) before chr(10).
I'm under Windows XP.
--
components: IO, Windows
files: chr13remo
New submission from Vladimir Rutsky :
I think there is a typo in threading documentation:
> In any situation where the size of the resource size is fixed,
> you should use a bounded semaphore.
- "size of the resource size", see attached patch for proposed fix.
(Based
New submission from Vladimir Rutsky :
This is code from recent trace.py
(http://svn.python.org/view/python/branches/release27-maint/Lib/trace.py?view=markup):
trace.py:169:
# Ignore a file when it contains one of the ignorable paths
for d in self._dirs:
# The
Changes by Vladimir Rutsky :
Added file: http://bugs.python.org/file20369/test.cmd
___
Python tracker
<http://bugs.python.org/issue10896>
___
___
Python-bugs-list mailin
Changes by Vladimir Rutsky :
Added file: http://bugs.python.org/file20370/test.out
___
Python tracker
<http://bugs.python.org/issue10896>
___
___
Python-bugs-list mailin
Vladimir Rutsky added the comment:
Workaround for people on Windows who don't wan't to modify trace.py:
to get clean trace of only your project calls add to ignore list python path
with mix of character cases. For me worked out this string:
python -m trace --ignore-dir=c:\pyth
Vladimir Rutsky added the comment:
SilentGhost, thanks for the patch! I can confirm, that adding os.path.normcase
fixes issues with different cases of files.
I believe there also may be issue with FAT's long file name mangling, like
"C:\PROGRA~1\python26\" instead of &q
Vladimir Rutsky added the comment:
Sorry I was wrong - patch don't fix original issue.
Case should be normalized not only for directories provided through
--ignore-dir, but also for directories obtained from __file__. In my tests on
Windows Ignore.names(self, filename, modulename) rec
Vladimir Konjkov added the comment:
willing you implement thread support for qnx6, or may be qnx4?
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue175>
_
__
Vladimir Konjkov added the comment:
For _XOPEN_SOURCE and _XOPEN_SOURCE_EXTENDED
look this
http://opengroup.org/onlinepubs/007908775/xcurses/implement.html
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/iss
Vladimir Konjkov added the comment:
there is script
Misk/find_recursionlimit.py
that can help to find real recursion limit
for QNX4 for one recursion used ~900 kb of stack thus 1Mb sufficient
for default recursion limit = 1000.
_
Tracker <[EMAIL PROTEC
Change by Vladimir Matveev :
--
nosy: +v2m
___
Python tracker
<https://bugs.python.org/issue46965>
___
___
Python-bugs-list mailing list
Unsubscribe:
Vladimir Matveev added the comment:
- introducing dedicated opcodes for each kind of awaited call is definitely an
option. In fact first implementation used it however as Dino has mentioned it
was more of a logistical issue (there were several spots that produced .pyc
files so compiler
New submission from Vladimir Ryabtsev :
This is regarding the page https://docs.python.org/3.7/library/sqlite3.html.
I believe this section on the very bottom of the page has been kept here for
pretty long time, during that both SQLite and the sqlite3 module evolved and
improved. Now the
New submission from Vladimir Matveev :
Calling methods and lookup up attributes when receiver is `super()` has extra
cost comparing to regular attribute lookup. It mainly comes from the need to
allocate and initialize the instance of the `super` which for zero argument
case also include
Change by Vladimir Matveev :
--
keywords: +patch
pull_requests: +23696
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/24936
___
Python tracker
<https://bugs.python.org/issu
Vladimir Matveev added the comment:
>Currently, super() is decoupled from the core language. It is just a builtin
>that provides customized attribute lookup. This PR makes super() more tightly
>integrated with the core language, treating it as if it were a keyword and
>part of
New submission from Vladimir Ryabtsev :
There are code snippets on the package's page
(https://docs.python.org/3.10/library/abc.html) like this:
class C(ABC):
@classmethod
@abstractmethod
def my_abstract_classmethod(cls, ...):
...
Here, the author probably want
Vladimir Matveev added the comment:
Apologies for the delay in reply: in more concrete numbers for IG codebase
enabling this optimization resulted in 0.2% CPU win.
--
___
Python tracker
<https://bugs.python.org/issue43
Change by Vladimir Ryabtsev :
--
pull_requests: +22974
pull_request: https://github.com/python/cpython/pull/24145
___
Python tracker
<https://bugs.python.org/issue38
Change by Vladimir Ryabtsev :
--
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.10 -Python 3.7
___
Python tracker
<https://bugs.python.org/i
Vladimir Ryabtsev added the comment:
The issue won't be fixed, but other useful changes applied.
--
resolution: -> wont fix
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
New submission from Vladimir Feinberg :
Python's standard logger provides an exception() method, which is to be called
from except blocks to log out exception traces by pulling from sys.exc_info().
Per https://github.com/python/cpython/blob/3.9/Lib/logging/__init__.py#L617 ,
logger.exce
Vladimir Feinberg added the comment:
I agree with both the duplicate classification and am glad the fix works in
3.10. Thanks all for the responses.
Given the issue can be triggered with a fairly benign setup (pandas triggers
such an error, and logger.exception is idiomatic), I do think
Vladimir Feinberg added the comment:
A simple catch may not work (the very first TracebackException is the one
that gets the RecursionError during initialization of its __context__), but
one thing I was thinking about was walking the __context__ pointers and
nulling out anything past the
Vladimir Feinberg added the comment:
Oh, yes, I suppose, that'll truncate to just the first TracebackException.
On Mon, Feb 1, 2021 at 4:38 PM Irit Katriel wrote:
>
> Irit Katriel added the comment:
>
> I meant to catch the exception in the constructor’s recursive call, a
Vladimir Feinberg added the comment:
Yep, you're right. I'd be happy to (but I've never done it before, so
please give me some time).
On Tue, Feb 2, 2021 at 12:35 AM Irit Katriel wrote:
>
> Irit Katriel added the comment:
>
> It should truncate at the call that
Change by Vladimir Feinberg :
--
keywords: +patch
pull_requests: +23256
stage: resolved -> patch review
pull_request: https://github.com/python/cpython/pull/24460
___
Python tracker
<https://bugs.python.org/issu
New submission from Vladimir Matveev :
Currently async functions are more expensive to use comparing to their sync
counterparts. A simple microbenchmark shows that difference could be quite
significant:
```
import time
def f(a):
if a == 0:
return 0
return f(a - 1)
async def
Change by Vladimir Matveev :
--
keywords: +patch
pull_requests: +21255
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22196
___
Python tracker
<https://bugs.python.org/issu
Vladimir Matveev added the comment:
If I understand proposed shape of API correctly - it was not supposed to return
exception via "result" so contract for new `PyGen_Send` function is something
like:
Return value | result
Vladimir Matveev added the comment:
Also should it be specific to generators/coroutines and accept PyGenObject* or
should it try to handle multiple cases and expose the result for them in
uniform way, i.e.
```
if (PyGen_CheckExact(gen) || PyCoro_CheckExact(gen)) {
// use coroutine
Vladimir Matveev added the comment:
I guess `PyIter_Send` would imply that this function should work for all inputs
(like in https://bugs.python.org/msg377007) which also sounds reasonable.
--
___
Python tracker
<https://bugs.python.
Vladimir Matveev added the comment:
so to summarize:
Proposed function signature:
```
PySendResult PyIter_Send(PyObject *obj, PyObject *arg, PyObject **result);
```
For generators/coroutines function will delegate to specialized implementation
that does not raise StopIteration exception
For
Vladimir Matveev added the comment:
Sounds like a good middleground to start: add ``PySendResult `` and
`PySendResult PyGen_Send(PyGenObject*, PyObject* PyObject**)` specific to
generators and coroutines. Subsequent changes could introduce `PySendResult
PyIter_Send(PyObject*, PyObject
Vladimir Matveev added the comment:
Yes, it should be
--
___
Python tracker
<https://bugs.python.org/issue41756>
___
___
Python-bugs-list mailing list
Unsub
Vladimir Matveev added the comment:
Serhiy, AFAIR PyIter_Send in my PR appear only as a rename from placeholder
`Name_TBD` and it still was specific to PyGenObjects. Do you mean something
that was listed in https://bugs.python.org/msg377007
Vladimir Matveev added the comment:
No, I don't think so but I can definitely make one. A few questions first:
- having PySendResult as a result type of PyIterSend seems ok, however prefix
for each concrete value (PYGEN_*) is not aligned with the prefix of the
function itself (Py
Change by Vladimir Matveev :
--
pull_requests: +21473
stage: resolved -> patch review
pull_request: https://github.com/python/cpython/pull/22443
___
Python tracker
<https://bugs.python.org/issu
Change by Vladimir Matveev :
--
pull_requests: +21639
pull_request: https://github.com/python/cpython/pull/22663
___
Python tracker
<https://bugs.python.org/issue41
Change by Vladimir Matveev :
--
pull_requests: +21649
stage: resolved -> patch review
pull_request: https://github.com/python/cpython/pull/22677
___
Python tracker
<https://bugs.python.org/issu
New submission from Vladimir Matveev :
https://bugs.python.org/issue41756 has introduced PyIter_Send as a common
entrypoint for sending values however currently fast path that does not use
StopIteration exception is only available for generators/coroutines. It would
be quite nice if this
Change by Vladimir Matveev :
--
keywords: +patch
pull_requests: +21739
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22780
___
Python tracker
<https://bugs.python.org/issu
Change by Vladimir Matveev :
--
type: -> performance
___
Python tracker
<https://bugs.python.org/issue42085>
___
___
Python-bugs-list mailing list
Unsubscrib
Change by Vladimir Matveev :
--
keywords: +patch
pull_requests: +21817
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22875
___
Python tracker
<https://bugs.python.org/issu
New submission from Vladimir Matveev :
`TaskWakeupMethWrapper` looks like a more limited version of `PyCFunction` so
it can be replaced with one.
Pros: remove a bunch of code, use better calling convention
Cons: now `wakeup` object will expose slightly more properties but I'm not sure
wh
Vladimir Ryabtsev added the comment:
I see no point in researching the version of sqlite, since Python does not
allow user to specify it, you just use the compiled version that comes with
Python distribution.
10 years now to the commit that introduced that piece of text:
https://github.com
Vladimir Ryabtsev added the comment:
May by I was wrong above and it uses system's Sqlite... But anyway it does not
cancel the fact that this section contradicts to another one.
--
___
Python tracker
<https://bugs.python.org/is
Vladimir Ryabtsev added the comment:
Also the footnote requires some minor corrections (formatting and style). I
suggest the following wording:
To get loadable extension support, your Python must be compiled with
``-–enable-loadable-sqlite-extensions`` option in ``PYTHON_CONFIGURE_OPTS``.
I
New submission from Vladimir Ryabtsev :
A new section has been added to the page as a result of
https://bugs.python.org/issue37826. The change:
https://github.com/python/cpython/commit/dcfe111eb5602333135b8776996332a8dcf59392
The wording it uses (in the beginning of section 8.5), defines
Change by Vladimir Ryabtsev :
--
pull_requests: +22071
pull_request: https://github.com/python/cpython/pull/23159
___
Python tracker
<https://bugs.python.org/issue38
Change by Vladimir Ryabtsev :
--
keywords: +patch
pull_requests: +22072
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/23160
___
Python tracker
<https://bugs.python.org/issu
Vladimir Ryabtsev added the comment:
1. Such understanding of a tutorial is debatable. Tutorial is just a material
for learning written with some system in mind, which is more interesting to
read than dry reference material. A tutorial, generally dpeaking, may be both
for beginners and for
Vladimir Ryabtsev added the comment:
> I can not find confusion caused by this tutorial section
Inada, have you read the very first message in this ticket? It explains why
this wording may cause confusion (and it did in me), and describes the problem
part. A link for your convenience:
ht
Vladimir Ryabtsev added the comment:
We have automatic chaining, so you don't need to use "from X" unless you want
to have some control on the traceback message. Even without knowing of this
syntax (and without using "from exc"), a user will get a traceback message
Vladimir Ryabtsev added the comment:
Also, the choice of the exception type in the example looks not very apt: you
raise "IOError" but the traceback message says "OSError" (which is due to
strange design decision "IOError = OSError"). For the tutorial, I would
Vladimir Ryabtsev added the comment:
All right, you won. I hope beginner users will be happy :)
I removed my proposal paragraph about __cause__ and __context__ and kept only
changes about exception type (https://bugs.python.org/issue42179#msg380435
Change by Vladimir Matveev :
--
pull_requests: +22267
pull_request: https://github.com/python/cpython/pull/23374
___
Python tracker
<https://bugs.python.org/issue42
Changes by Vladimir Rutsky :
--
nosy: +rutsky
___
Python tracker
<http://bugs.python.org/issue13857>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Vladimir Chebotarev :
--
pull_requests: +13537
pull_request: https://github.com/python/cpython/pull/7243
___
Python tracker
<https://bugs.python.org/issue29
Change by Vladimir Matveev :
--
keywords: +patch
pull_requests: +10365
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35306>
___
_
Change by Vladimir Matveev :
--
keywords: +patch
pull_requests: +10367
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Vladimir Matveev :
--
keywords: +patch
pull_requests: +10371
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue31446>
___
_
Vladimir Matveev added the comment:
I can give it a try.
--
nosy: +v2m
___
Python tracker
<https://bugs.python.org/issue14094>
___
___
Python-bugs-list mailin
Change by Vladimir Matveev :
--
keywords: +patch
pull_requests: +10488
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Vladimir Matveev :
--
nosy: +v2m
___
Python tracker
<https://bugs.python.org/issue35568>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Vladimir Matveev :
--
keywords: +patch
pull_requests: +10606
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35568>
___
_
Change by Vladimir Matveev :
--
keywords: +patch, patch
pull_requests: +10606, 10607
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Vladimir Matveev :
--
keywords: +patch, patch, patch
pull_requests: +10606, 10607, 10608
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
New submission from Vladimir Perić :
In Python 3.7.1 on Windows 10 ssl library function call
ssl.create_default_context(ssl.Purpose.SERVER_AUTH) raises an ssl error:
File "C:\Python37\lib\ssl.py", line 471, in _load_windows_store_certs
self.load_verify_locations(cadata=certs)
ss
Vladimir Perić added the comment:
Same outcome in Python 3.7.2.
See first comment for detailed explanation of issue.
--
___
Python tracker
<https://bugs.python.org/issue35
Vladimir Perić added the comment:
Public Certificate file cert.pem is attached.
Version of ssl lib in pythons on my machine:
Python 3.7.2 (tags/v3.7.2:9a3ffc0492, Dec 23 2018, 23:09:28) [MSC v.1916 64 bit
(AMD64)] on win32
Type "help", "copyright", "credits" or
Vladimir Perić added the comment:
Thank you all for this expeditive help. Sorry for taking your time.
I will remove bad certificates from my machine.
Thanks again.
I will try to close this one.
--
stage: -> resolved
status: open ->
New submission from Vladimir Filippov:
These 4 symbols were encoded incorrectly to EBCDIC (codec cp500): "![]|".
Correct table of conversation for these symbols described in
https://www.ibm.com/support/knowledgecenter/SSZJPZ_11.3.0/com.ibm.swg.im.iis.ds.parjob.adref.
Vladimir Filippov added the comment:
According to
ftp://ftp.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/EBCDIC/CP037.TXT symbols [
and ] have other codes (instead of 0xAD and 0xBD):
0xBA0x005B #LEFT SQUARE BRACKET
0xBB0x005D #RIGHT SQUARE BRACKET
Looks like
ftp://ftp.unicode.org
New submission from Vladimir Surjaninov :
If we are writing xml with CDATA section and leaving non-empty indentation and
new-line parameters, a parent node of the section will contain useless
indentation, that will be parsed as a text.
Example:
>>>doc = minidom.Document(
Change by Vladimir Surjaninov :
--
keywords: +patch
pull_requests: +12465
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue36407>
___
_
Vladimir Magamedov added the comment:
Seems like this fix is incomplete. It contains this check:
sock.type == socket.SOCK_STREAM
But sock.type is not only a type (at least in Linux and FreeBSD), it also may
contain SOCK_NONBLOCK and SOCK_CLOEXEC flags. So I'm hitting the same pr
Vladimir Semenenko added the comment:
After they marked the issue as "resolved" earlier this year I tested a
subsequent 3.x release in Windows 7 and Vista (I don't have 10). The issue
was still there.
I don't have a workaround. I am forced to stay with 2.7.3.
On Dec 8,
Vladimir Chebotarev added the comment:
Hi.
I guess this issue has to be reopen because Alexey erroneously broke adding
empty paths to `sys.path` along with his patch.
Official embeddable Pythons do contain a blank line in its ._pth, and this
allowed users to import modules from script
1 - 100 of 171 matches
Mail list logo
