[issue1185] py3k: Completely remove nb_coerce slot

[Martin v. Löwis]

Changes by Martin v. Löwis:


--
keywords:  -py3k

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue478407] Need Windows os.link() support

[Sean Reifschneider]

Changes by Sean Reifschneider:


--
keywords: +patch
superseder:  -> Add os.link() and os.symlink() support for Windows


Tracker <[EMAIL PROTECTED]>


___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1578269] Add os.link() and os.symlink() support for Windows

[Sean Reifschneider]

Sean Reifschneider added the comment:

swarren: According to the wikipedi article on junction points:

   They can only be used on folders, not files.
   They are being replaced by symbolic links.

The latter I take to mean junction points are being phased out, but I
couldn't find any information one way or another on it.

http://en.wikipedia.org/wiki/NTFS_junction_point

--
nosy: +jafo

_
Tracker <[EMAIL PROTECTED]>

_
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1186] optparse documentation: -- being collapsed to - in HTML

[Michael Hoffman]

New submission from Michael Hoffman:

See  where
it says 'either "-" or "-" can be option arguments'. One of these should
be --. The same error occurs several times on the same page.

Not a problem in the Optik docs at
.

--
components: Documentation
messages: 56074
nosy: gward, hoffman
severity: normal
status: open
title: optparse documentation: -- being collapsed to - in HTML
versions: Python 2.5

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1578269] Add os.link() and os.symlink() support for Windows

[Stephen Warren]

Stephen Warren added the comment:

Hmm. I just tested Accurev - whatever it does, it works for files too.
That said, it could be making hard-links, which I guess could be different.

Additionally, the sysinternals "junction" utility doesn't find any
junction points when probing the link files.

I'll see if I can find out how they implemented it...

_
Tracker <[EMAIL PROTECTED]>

_
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1186] optparse documentation: -- being collapsed to - in HTML

[Guido van Rossum]

Guido van Rossum added the comment:

This is only a problem with the 2.5 latex docs.

--
assignee:  -> fdrake
nosy: +fdrake, gvanrossum

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1185] py3k: Completely remove nb_coerce slot

[Guido van Rossum]

Guido van Rossum added the comment:

Can you redo the patch while keeping the slot *position* (though not the
name or type)?  The wasted space is minimal (4-8 bytes per type or class
object) and it means a lot for third party code if the positional struct
initialization never breaks due to insertion or removal of a slot. 
Since everyone has a zero here anyway, I propose to name the slot
nb_reserved and make its type int.

--
nosy: +gvanrossum

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1578269] Add os.link() and os.symlink() support for Windows

[Stephen Warren]

Stephen Warren added the comment:

It seems that Accurev uses junction points for directories, and
hard-links for files. That's probably a little to disparate to implement
in Python?

Also, I tried sysinternals' junction.exe and whilst it allows one to
create junction points that point at files, you can't actually read the
file via the junction point - so it does seem that they only work for
directories:-(

Oh well, lets hope whatever new Vista API exists works better...

_
Tracker <[EMAIL PROTECTED]>

_
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1187] pipe fd handling issues in subprocess.py on POSIX

[Andrew Nissen]

New submission from Andrew Nissen:

Revision 53293 appears to have missed some of the logic inherent in the
previous code.  There also appears to be problems with the way that the
dup2 calls are made that can result in a behavior different then
intended under a number of circumstances.

fix_fileno.py demonstrates the improper behavior

--
components: Library (Lib)
files: fix_fileno.py
messages: 56079
nosy: anissen
severity: minor
status: open
title: pipe fd handling issues in subprocess.py on POSIX
type: behavior
versions: Python 2.4

__
Tracker <[EMAIL PROTECTED]>

__import os
import subprocess

STDIN		= '/tmp/stdin.test'
STDOUT		= '/tmp/stdout.test'
STDERR		= '/tmp/stderr.test'

os.close(0)
os.close(1)
os.close(2)

stdin  = open(STDIN,  'w')
stdin.close()

stdout = open(STDOUT, 'w')
stderr = open(STDERR, 'w')
stdin  = open(STDIN,  'r')

CALL_CMD	= ['/bin/cat', '/etc/rc.local']
CALL_ARGS	= { 'stdin'	: stdin,
		'stdout'	: stdout,
		'stderr'	: stderr,
		'close_fds'	: True,
		  }

subprocess.call(CALL_CMD, **CALL_ARGS)

stdin.close()
stdout.close()
stderr.close()
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1187] pipe fd handling issues in subprocess.py on POSIX

[Andrew Nissen]

Andrew Nissen added the comment:

This patch (subprocess.fix_fileno.udiff) made against subprocess.py
(Revision 55604)appears to give the desired behavior

__
Tracker <[EMAIL PROTECTED]>

__

subprocess.fix_fileno.udiff
Description: Binary data
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1185] py3k: Completely remove nb_coerce slot

[Guido van Rossum]

Guido van Rossum added the comment:

Thanks Neil!

--
resolution:  -> accepted
status: open -> closed

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1185] py3k: Completely remove nb_coerce slot

[Neil Schemenauer]

Neil Schemenauer added the comment:

I made the changes as suggest by Guido.  Commited as SVN rev 58226. 
Thanks for the patch.

--
nosy: +nas

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1134] Parsing a simple script eats all of your memory

[Neil Schemenauer]

Neil Schemenauer added the comment:

It looks to me like fp_readl is no longer working as designed and the
patch is not really the right fix.  The use of "decoding_buffer" is
tricky and I think the conversion to bytes screwed it up.  It might be
clearer to have a separate "decoding_overflow" struct member that's used
for overflow rather than overloading "decoding_buffer".

--
nosy: +nas

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1578269] Add os.link() and os.symlink() support for Windows

[Sean Reifschneider]

Sean Reifschneider added the comment:

If the file links are on the same volume, it's probably using hard
links.  Symbolic links can cross file-systems, of course.  So it sounds
like the Junction Points aren't going to work to replace symlinks, and
they'll be Vista only.

_
Tracker <[EMAIL PROTECTED]>

_
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1189] Documentation for tp_as_number tp_as_sequence tp_as_mapping

[Amaury Forgeot d'Arc]

New submission from Amaury Forgeot d'Arc:

This patch adds documentation for all the fields in the tp_as_number,
tp_as_sequence and tp_as_mapping structures.
It may not be complete, but is still better than the XXX in the current
docs.
This is my first contribution to the doc, feel free to amend it!

This patch describes the python3.0 situation, which is simpler since the
removal of coercion. It can serve as a start for 2.6 as well; a second
patch about coercion will follow.

PS: it's really a pleasure to use the new ReST format.

--
components: Documentation
files: numbermethods-py3k.diff
messages: 56087
nosy: amaury.forgeotdarc
severity: normal
status: open
title: Documentation for tp_as_number tp_as_sequence tp_as_mapping
versions: Python 3.0

__
Tracker <[EMAIL PROTECTED]>

__

numbermethods-py3k.diff
Description: Binary data
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1188] universal newlines doesn't identify CRLF during tell()

[Philip Jenvey]

Philip Jenvey
 added the comment:

make that against r58227

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1188] universal newlines doesn't identify CRLF during tell()

[Philip Jenvey]

Changes by 
Philip Jenvey
:


--
type:  -> behavior

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1188] universal newlines doesn't identify CRLF during tell()

[Philip Jenvey]

New submission from 
Philip Jenvey
:

tell() will skip the next LF (after a CR sets f_skipnextlf) when 
universal newline support is enabled; essentially doing part of the work 
of read(). However it does not identify CRLF as a newline, as read() 
would, e.g.:

>>> open('/tmp/crlf', 'wb').write('CRLF\r\nEOF')
>>> fp = open('/tmp/crlf', 'U')
>>> fp.read()
'CRLF\nEOF'
>>> fp.newlines # correct when read()ing
'\r\n'
>>> fp = open('/tmp/crlf', 'U')
>>> fp.readline()
'CRLF\n'
>>> fp.newlines
>>> fp.tell()
6L
>>> fp.newlines # tell() skipped ahead..
>>> fp.readline()
'EOF'
>>> fp.newlines # ..but never identified CRLF
>>> 

The following patch makes tell() mark CRLF as a newline in this case, 
and ensures so with an added test to test_univnewlines.py. It's against 
trunk, r28227

--
components: Library (Lib)
files: univnewline_tell-r58227.diff
messages: 56085
nosy: pjenvey
severity: normal
status: open
title: universal newlines doesn't identify CRLF during tell()
versions: Python 2.6

__
Tracker <[EMAIL PROTECTED]>

__

univnewline_tell-r58227.diff
Description: Binary data
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1189] Documentation for tp_as_number tp_as_sequence tp_as_mapping

[Martin v. Löwis]

Changes by Martin v. Löwis:


--
keywords: +patch

__
Tracker <[EMAIL PROTECTED]>

__
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com