anatoly techtonik added the comment:
Now I get it. That's much better. Thanks. =)
After rereading the description with this new info I spot that __main__ is
called a module, which is not true, because it is only a module name. It makes
sense to enclose it in quotes in title as well.
anatoly techtonik added the comment:
Reopening for Python 3. Does anybody still use context diffs nowadays?
--
status: closed -> open
versions: +Python 3.3 -Python 2.7, Python 3.2
___
Python tracker
<http://bugs.python.org/iss
anatoly techtonik added the comment:
Thanks. I am glad OS TZ support finally issue took off. =)
--
___
Python tracker
<http://bugs.python.org/issue7582>
___
___
anatoly techtonik added the comment:
> The reasons for rejecting this still apply.
Which specifically are valid for 3.3?
--
___
Python tracker
<http://bugs.python.org/iss
anatoly techtonik added the comment:
Eric, you're refering to argument:
> -1 Even if diff.py is not exaclty a diff replacement, it still makes
> sense to emulate what's in people's minds.
Could you explain it in your own words, because I don't posess the skills to
anatoly techtonik added the comment:
I agree that reading the source doesn't make it clear how to extend or use PDB,
so I've changed the title. High level overview is required.
I think an example would really help there. For instance a simple execution
scroller - analogue of `pytho
New submission from anatoly techtonik :
http://docs.python.org/py3k/library/2to3.html
should mention the practice of running 2to3 in setup.py for codebase
compatible with both Python 2 and Python 3.
--
assignee: docs@python
components: Documentation
messages: 166108
nosy: docs
New submission from anatoly techtonik :
This scenario fails:
python setup.py install
python3 setup.py install
Because it seems like code once built for Python 2 is not rebuild when
installing for Python 3.
--
assignee: eric.araujo
components: Distutils, Distutils2
messages: 166109
anatoly techtonik added the comment:
Damn it. I've run 2to3 during setup.py phase and went smoothly, but when I run
examples the package fails.
It should at least warn about this "import new". It should not be that hard to
catch.
--
n
New submission from anatoly techtonik :
issue6964 is closed, so this is a reminder that discussion over the actual
issue is not finished yet.
--
components: 2to3 (2.x to 3.x conversion tool)
messages: 166111
nosy: techtonik
priority: normal
severity: normal
status: open
title
anatoly techtonik added the comment:
You're mistaken. issue6964 is not about deleting `new` module in Python 3, it
is about the 2to3 tool skipping this fact without warning.
--
___
Python tracker
<http://bugs.python.org/is
anatoly techtonik added the comment:
>From the user point of view that's the same as saying for optparse:
Bottom line: move over to the argparse module *before* running 2to3.
--
resolution: invalid ->
___
Python tracker
<http://b
anatoly techtonik added the comment:
Bottom line: The fact that 2to3 isn't capable to fix "import new" automatically
doesn't mean it should not warn that this code should be fixed manually.
--
___
Python tracker
<http://bug
anatoly techtonik added the comment:
My request is that after running 2to3 my code still doesn't work in Python 3.
--
resolution: wont fix ->
status: closed -> open
___
Python tracker
<http://bugs.python.
anatoly techtonik added the comment:
Florent: It is the same. "new" module just doesn't need replacement, because
its functionality is in the language, therefore it is no different saying.
--
___
Python tracker
<http://bugs.pyt
anatoly techtonik added the comment:
Still not documented..
--
___
Python tracker
<http://bugs.python.org/issue11776>
___
___
Python-bugs-list mailing list
Unsub
anatoly techtonik added the comment:
Another 4 complains about missing references:
http://stackoverflow.com/questions/1015307/python-bind-an-unbound-method
--
___
Python tracker
<http://bugs.python.org/issue11
anatoly techtonik added the comment:
> Please don't reopen issues.
"Please don't ask for such silly stuff". You can understand the reason why this
issue was opened, so why do you keep closing it if the "issue is not resolved"?
The scope of this issue nev
anatoly techtonik added the comment:
Why not to follow the convention and add underscore _ to the names to remove
the ambiguity and future reports and confusion about that thees functions are
not documented?
--
status: closed -> pending
___
Pyt
anatoly techtonik added the comment:
Looks like a regression - I can't remember such messages in Python 2.
--
nosy: +techtonik
___
Python tracker
<http://bugs.python.org/is
anatoly techtonik added the comment:
Clearly regressing. In Python 2 it was IOError exception:
>>> import urllib
>>> urllib.urlretrieve('missing')
Traceback (most recent call last):
File "", line 1, in
File "C:\pp\lib\urllib.py", line 93, i
New submission from anatoly techtonik:
After build options in setup.py is edited, command `python setup.py install`
doesn't remove build directory and uses its cached content. This behavior is
non-obvious and leads to errors.
The proposal is to calculate hash from build configuration, sa
anatoly techtonik added the comment:
This is still an issue for Windows.
--
nosy: +techtonik
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issue8
New submission from anatoly techtonik:
Currently distutils builds files in a temporary directory named 'build' in
current dir if not specified otherwise. It will be pythonic to name this
directory to be __build__ be default to distinguish it from project specific
directories and cl
anatoly techtonik added the comment:
RDM> 'build' is pretty much universally understood to be something that can be
blown away
That's not true anymore in 2012. Why follow the bad practice?
I also want to know what open source software project are you referring to.
From my
anatoly techtonik added the comment:
Another difference from C sources that it is very convenient to use Python
packages directly from source. In this case this unrelated 'build' dir will be
the source of confusion if user previously tried to install the package.
--
statu
anatoly techtonik added the comment:
Oh, sorry. I am just testing Python 3.3 and there are so many issues that
hardly can test and fill them all.
--
___
Python tracker
<http://bugs.python.org/issue8
anatoly techtonik added the comment:
That's not an argument. I am asking about it in general.
Another wart of Python.
--
___
Python tracker
<http://bugs.python.org/is
New submission from anatoly techtonik:
Windows BYTE type is unsigned char, but ctypes defines it as signed.
{{{
BYTE
A byte (8 bits).
This type is declared in WinDef.h as follows:
typedef unsigned char BYTE;
typedef unsigned char BYTE;
}}}
http://msdn.microsoft.com/en-us/library/windows
New submission from anatoly techtonik:
>>> import ctypes.wintypes
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.2/ctypes/wintypes.py", line 20, in
class VARIANT_BOOL(ctypes._SimpleCData):
ValueError: _type_ 'v'
anatoly techtonik added the comment:
Perhaps the patch already there - see http://www.themacaque.com/?p=826
--
___
Python tracker
<http://bugs.python.org/issue16
anatoly techtonik added the comment:
It is ok with http://pypi.python.org/pypi, but not with http://pypi.python.org,
for example. Complaining that http://pypi.python.org is not found in .pypirc
--
___
Python tracker
<http://bugs.python.
New submission from anatoly techtonik:
Renamed urllib.urlretrieve changed behaviour in Py3k, which leads to
ZeroDivisionErrors in applications that use block_size parameter for
calculations. Previously, block size was constant. Now it varies making it
impossible to exactly calculate value
New submission from anatoly techtonik:
http://hg.python.org/cpython/file/tip/PC/winsound.c
No need to maintain this in C. It doesn't seem like a critical part of code.
Will there be significant performance penalty?
--
components: Library (Lib), ctypes
messages: 174838
nosy: tech
Changes by anatoly techtonik :
--
assignee: -> docs@python
components: +Documentation
nosy: +docs@python
versions: +Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4
___
Python tracker
<http://bugs.python.org/issu
anatoly techtonik added the comment:
I strongly disagree with your summary.
It's a new behavior for the old renamed module that clearly breaks existing
code ported with 2to3.
The 95% of callable usage is to get the estimated download progress (to draw
progress bar or time calcula
anatoly techtonik added the comment:
Please note that changes to urlretrieve to return block size 0 in callback
breaks existing PyPI apps, such as http://pypi.python.org/pypi/wget
It would be nice if you revert this part from
http://hg.python.org/cpython/rev/53715804dc71
Also if you change
Changes by anatoly techtonik :
--
versions: +Python 3.4
___
Python tracker
<http://bugs.python.org/issue10050>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from anatoly techtonik:
os.path.split('c:foo') gives ('c:', 'foo') on Windows and ('', 'c:foo') on
Linux, which is not documented. IIUC, the behavior change in os module is not
possible, so a documentation note will be appreci
anatoly techtonik added the comment:
Historically os.path.split() on Windows is able to grok UNIX paths easily.
Don't you think that Python language reference for the os.path should include
less vague definition of Windows, UNIX-style and old-style MacOS paths it works
anatoly techtonik added the comment:
User story: as a Python programmer working with different systems, I'd like to
know how os.path module threats paths on these systems.
--
___
Python tracker
<http://bugs.python.org/is
New submission from anatoly techtonik:
Windows.
Python 3:
>>> import os.path as osp
>>> osp.split('//hostname/foo/')
('//hostname/foo/', '')
Python 2:
>>> osp.split('//hostname/foo/')
('//hostname/foo', '
anatoly techtonik added the comment:
I don't know about the differences. An expert is required.
--
___
Python tracker
<http://bugs.python.org/issue16413>
___
___
anatoly techtonik added the comment:
Does that mean that Py3's split() uses splitunc() instead of splitdrive()?
--
___
Python tracker
<http://bugs.python.org/is
anatoly techtonik added the comment:
Ok, so how to fix the regression?
--
___
Python tracker
<http://bugs.python.org/issue16424>
___
___
Python-bugs-list mailin
anatoly techtonik added the comment:
I see nothing wrong with reimplementation with different underlying lib as long
as behavior stays the same and lib2to3 converts code correctly.
The API that block size if constant and non-zero is broken with Python 3.3. I
thought that API breaks are only
anatoly techtonik added the comment:
I agree that new implementation doesn't prevent me from estimating the
progress, but it does make the callback code worse, not better. Either by
closure or by global variable, but it makes callback stateful.
To fix this issue either blocks_number para
anatoly techtonik added the comment:
Tested on Windows. Test is attached.
--
keywords: +patch
Added file: http://bugs.python.org/file27976/test_register.py.diff
___
Python tracker
<http://bugs.python.org/issue13
anatoly techtonik added the comment:
Better test case.
--
Added file: http://bugs.python.org/file27977/test_register.py.diff
___
Python tracker
<http://bugs.python.org/issue13
anatoly techtonik added the comment:
Fix.
--
Added file: http://bugs.python.org/file27978/register.py.diff
___
Python tracker
<http://bugs.python.org/issue13
New submission from anatoly techtonik:
Given:
1. there is no .pypirc
2. users enters credentials to register command
3. user refuses to create .pypirc
Outcome:
password is not being stored and subsequent (upload) command doesn't get it.
Attached is the test case.
--
ass
anatoly techtonik added the comment:
Fix is attached.
--
Added file: http://bugs.python.org/file27980/register.py.2.diff
___
Python tracker
<http://bugs.python.org/issue16
anatoly techtonik added the comment:
So, if upload command never accepted repository by section name I am +1 for
closing this issue (and opening a new one if symlink workaround is required).
--
nosy: +techtonik
___
Python tracker
<h
anatoly techtonik added the comment:
I'd say this one worthy to be backported.
--
nosy: +techtonik
status: pending -> open
___
Python tracker
<http://bugs.python.org/i
anatoly techtonik added the comment:
pyunit_time.patch is invalid - missing space on the last line.
--
nosy: +techtonik
___
Python tracker
<http://bugs.python.org/issue4
New submission from anatoly techtonik:
It is very annoying. Take this as an example. 'patch' is a module (library)
that is meant to be used from other programs. Therefore it can not (should not)
setup handlers for itself.
>>> import patch
>>> patch.PatchSet().par
anatoly techtonik added the comment:
Forgot to mention that bundled NullHandler doesn't work in Python 2.7 and from
what I can see it is not covered with tests for this version.
Traceback (most recent call last):
File "", line 1, in
File "patch.py", line 124,
anatoly techtonik added the comment:
Nevermind the last message - I was specifying NullHandler as a class, not as an
instance.
--
___
Python tracker
<http://bugs.python.org/issue16
anatoly techtonik added the comment:
More specifically, you need to copy NullHandler code if you want to run it with
Python 2.x < 2.7
--
nosy: +techtonik
___
Python tracker
<http://bugs.python.org/issu
anatoly techtonik added the comment:
I'd say this is a pretty valid issue with "won't fix" or "workaround available"
resolution.
The question - is the same behavior preserved for Python 3?
--
resolution: invalid -> wont
anatoly techtonik added the comment:
Nice conflict case for explaining why perfect API is not here.
Because ', ' is now used as an item separator inline and separator for items
that span multiple lines, we get trailing whitespace. If ',' is used, items
will collide. To r
New submission from anatoly techtonik:
Awesome json tool doesn't work anymore in Python 3 (needs tests?).
http://stackoverflow.com/questions/352098/how-to-pretty-print-json-script
C:\Python27>python -m json.tool stdlibx.json
{
"distutils": [
"Doc/distutils&q
Changes by anatoly techtonik :
--
components: +Library (Lib)
title: regression: -m json.tool module -> regression: -m json.tool module is
broken
___
Python tracker
<http://bugs.python.org/issu
anatoly techtonik added the comment:
Would you mind providing some counter-arguments?
--
___
Python tracker
<http://bugs.python.org/issue16333>
___
___
Python-bug
anatoly techtonik added the comment:
Trailing whitespace produce visual warnings in diff comparison tools. If you
have to read docs on how fix every piece of code that produces readable JSON to
avoid this warnings, it is a very-very bad user experience.
The argument that by default the output
anatoly techtonik added the comment:
+1 for all branches.
Is that handling of booleans PEPified somewhere?
--
nosy: +techtonik
___
Python tracker
<http://bugs.python.org/issue4
anatoly techtonik added the comment:
',' makes lists less readable, directly the opposite of what the *indent*
option is for. The *separators* variable is a insufficient solution, because it
was not designed to work with indents.
Therefore the original solution to strip trailing
anatoly techtonik added the comment:
> ',' used by default only when indentation used. It increases readability.
Do you mean that when indentation is used, the separator only appears on line
ends? Otherwise I can see how,is,that,more readable, than, that.
> Of course, this
anatoly techtonik added the comment:
On Tue, Nov 27, 2012 at 12:15 AM, Ezio Melotti wrote:
> I'm not sure the documentation should be changed. While boolean values
> are accepted, user should prefer True/False, so the fact that you can pass
> other things shouldn't be do
New submission from anatoly techtonik:
http://docs.python.org/2/library/ctypes.html#ctypes.Structure._anonymous_
"An optional sequence that lists the names of unnamed (anonymous) fields".
If you feed it a string, such as _offset, it will print a very interesting
error:
...
anatoly techtonik added the comment:
s/A_OFFSET_UNION/_OFFSET_UNION/
--
___
Python tracker
<http://bugs.python.org/issue16566>
___
___
Python-bugs-list mailin
anatoly techtonik added the comment:
The union definition for the curious:
class _OFFSET(Structure):
_fields_ = [
('Offset', DWORD),
('OffsetHigh', DWORD)]
class _OFFSET_UNION(Union):
_anonymous_ = '
anatoly techtonik added the comment:
ctypes should throw proper exception if a string is used instead of sequence.
It doesn't do this.
--
resolution: invalid ->
status: closed -> open
___
Python tracker
<http://bugs.python.
anatoly techtonik added the comment:
I agree with you on a generic case, where "Special cases aren't special enough
to break the rules.", but this special case in ctypes and _anonymous_ context
is where the rule "Although practicality beats purity." should apply. O
anatoly techtonik added the comment:
> The reason is that people might rely on exact output and it's not nice to
> break their code in a bugfix release.
This code has a very bad smell. Between supporting people who did that and
teaching them a lesson I choose the latter, bu
anatoly techtonik added the comment:
The problem with policy and 'common sense' is that not everybody can feel that
'common sense', especially when there is no time to go deep into the issue.
Policy is a quick and good 42 no matter that the matter is. The problem that
anatoly techtonik added the comment:
+1
--
___
Python tracker
<http://bugs.python.org/issue16549>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from anatoly techtonik:
A common usage pattern is to prevent clean up in tearDown() if the test failed.
However, it requires a hack:
http://stackoverflow.com/questions/4414234/getting-pythons-unittest-results-in-a-teardown-method.
Would be nice to have an officially documented
anatoly techtonik added the comment:
Or call tearDown() with some parameter that it's able to retrieve.
--
___
Python tracker
<http://bugs.python.org/is
anatoly techtonik added the comment:
addSuccessCleanup is not the best name as it assumes that some cleanup is being
added, which is confusing.
Additional consideration that the need to leave the test results is a user run
time preference, which may only be actual when debugging or working on
anatoly techtonik added the comment:
On Tue, Dec 4, 2012 at 3:43 PM, Michael Foord wrote:
>
> Well, addSuccessCleanup *would* be an api for adding a cleanup - one that
> is only called on success. So the cleanup is skipped on failure or error,
> which was the original use case.
>
New submission from anatoly techtonik:
If tarfile.next() is used before .extractall(), the latter fails to extract
files that were accessed.
--
components: Library (Lib)
messages: 177065
nosy: techtonik
priority: normal
severity: normal
status: open
title: tarfile.extractall() doesn&#
anatoly techtonik added the comment:
Attached is patch with test. Test needs valid extractable .tar file. The
testtar.tar that is currently present fails to unpack on Windows because of too
long filenames inside.
--
keywords: +patch
Added file: http://bugs.python.org/file28232/16631
anatoly techtonik added the comment:
issue16601 is about restarting iterations from zero if interrupted. This one is
that extractall() should not use public iteration API at all.
--
___
Python tracker
<http://bugs.python.org/issue16
anatoly techtonik added the comment:
Can anybody write a sum up on this?
--
versions: +Python 3.4
___
Python tracker
<http://bugs.python.org/issue1191964>
___
___
New submission from anatoly techtonik:
This critical bug is one of the reasons that non-English speaking communities
doesn't adopt Python as broadly as it happens in English world compared to
other technologies (PHP etc.).
# -*- coding: utf-8 -*-
import os
os.mkdir(u'Р
anatoly techtonik added the comment:
In Python 3 it fails with UnicodeEncodeError in
"C:\Python33\lib\encodings\cp437.py", while Vista's 'dir' command shows
everything correctly in the same console, so somebody definitely overlooked
that aspect.
This bug is clearl
anatoly techtonik added the comment:
>
> - Do you have a full traceback of the failing os.walk() in Python3.3?
>
Traceback (most recent call last):
File "test.py", line 9, in
print(dirs)
File "C:\Python33\lib\encodings\cp437.py", line 19, in encode
anatoly techtonik added the comment:
I attach tests.py file used to run the tests. Results are in python2.out.txt
and python3.out.txt also attached.
> What are the results of os.stat(b'Русское имя') and os.stat(b'Русское имя')
> on Python 2.7 and Python 3.3+?
b&#
Changes by anatoly techtonik :
Added file: http://bugs.python.org/file28288/tests.py
___
Python tracker
<http://bugs.python.org/issue16656>
___
___
Python-bugs-list mailin
Changes by anatoly techtonik :
Added file: http://bugs.python.org/file28289/python2.out.txt
___
Python tracker
<http://bugs.python.org/issue16656>
___
___
Python-bug
Changes by anatoly techtonik :
Added file: http://bugs.python.org/file28290/python3.out.txt
___
Python tracker
<http://bugs.python.org/issue16656>
___
___
Python-bug
anatoly techtonik added the comment:
There is one more problem - when I redirect the output with:
> py test_unicode_fname.py > test.log 2>&1
In Python 2.7 the traceback is at the end of file, in Python 3.3 it is at the
beginning. Therefore I just copied data from the screen, whe
Changes by anatoly techtonik :
Added file: http://bugs.python.org/file28305/py27fname.log
___
Python tracker
<http://bugs.python.org/issue16656>
___
___
Python-bugs-list m
Changes by anatoly techtonik :
Added file: http://bugs.python.org/file28306/py33fname.log
___
Python tracker
<http://bugs.python.org/issue16656>
___
___
Python-bugs-list m
New submission from anatoly techtonik:
This following recipe from Optik examples should be added to documentation. It
is extremely helpful when porting to optparse from getopt or other option
parsing schemes.
--
assignee: docs@python
components: Documentation
messages: 177447
nosy
Changes by anatoly techtonik :
Added file: http://bugs.python.org/file28307/pass_through.py
___
Python tracker
<http://bugs.python.org/issue16678>
___
___
Python-bug
anatoly techtonik added the comment:
It allows to port options to and from optparse incrementally.
--
___
Python tracker
<http://bugs.python.org/issue16
New submission from anatoly techtonik:
Tested on Windows. When Python output is redirected with:
> py test_unicode_fname.py > test.log 2>&1
In Python 2.7 the traceback is at the end of file, in Python 3.3 it is at the
beginning. In should be in the middle, and it appears
anatoly techtonik added the comment:
haypo didn't understood the main user story for this ticket and closed it, so I
reopen it with simplified user story.
"""As a developer, I want Python os.listdir('.') function return all
directories in current direct
501 - 600 of 977 matches
Mail list logo
