Message 253670 - Python tracker

Message253670

Author	eryksun
Recipients	eryksun, jan parowka, markroseman, martin.panter, terry.reedy
Date	2015-10-29.09:53:45
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1446112426.22.0.266131764612.issue24765@psf.upfronthosting.co.za>
In-reply-to

Content
On Windows, how about creating a junction (_winapi.CreateJunction in 3.5, or the shell's mklink /j) from ~\.idlerc to %APPDATA%\idle? If ~\.idlerc already exists, it could be moved to %APPDATA%\idle before creating the junction. New code would directly use %APPDATA%\idle, but old code would continue to use ~\.idlerc. Creating junctions requires no special privilege, but IDLE would need write access to the user's home directory. If write access is denied, at least newer IDLE versions that use %APPDATA% would work. On Linux, a symbolic link could be created from ~/.idlerc to [$XDG_CONFIG_HOME\|~/.config]/idle.

Content

On Windows, how about creating a junction (_winapi.CreateJunction in 3.5, or the shell's mklink /j) from ~\.idlerc to %APPDATA%\idle? If ~\.idlerc already exists, it could be moved to %APPDATA%\idle before creating the junction. New code would directly use %APPDATA%\idle, but old code would continue to use ~\.idlerc.

Creating junctions requires no special privilege, but IDLE would need write access to the user's home directory. If write access is denied, at least newer IDLE versions that use %APPDATA% would work.

On Linux, a symbolic link could be created from ~/.idlerc to [$XDG_CONFIG_HOME|~/.config]/idle.

History
Date	User	Action	Args
2015-10-29 09:53:46	eryksun	set	recipients: + eryksun, terry.reedy, markroseman, martin.panter, jan parowka
2015-10-29 09:53:46	eryksun	set	messageid: <1446112426.22.0.266131764612.issue24765@psf.upfronthosting.co.za>
2015-10-29 09:53:46	eryksun	link	issue24765 messages
2015-10-29 09:53:45	eryksun	create