This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jaraco
Recipients eric.smith, giampaolo.rodola, jafo, jaraco, lemburg, loewis, nnorwitz, r.david.murray, swarren
Date 2009-09-02.20:18:34
SpamBayes Score 2.5467575e-06
Marked as misclassified No
Message-id <1251922717.12.0.883117380874.issue1578269@psf.upfronthosting.co.za>
In-reply-to
Content
The deviance between the Unix and Windows symlink functions is apparent
in the signature, though not explicitly-defined in any formal
documentation.  Perhaps the following could be included as formal
documentation.  Should this documentation be added to os.rst, or would
another place be better?

The Windows version takes an additional, optional parameter,
target_is_directory, which defaults to False.

On Windows, a symlink represents a file or a directory, and does not
morph to the target dynamically.  For this reason, when creating a
symlink on Windows, if the target is not already present, the symlink
will default to being a file symlink.  If target_is_directory is set to
True, the symlink will be created as a directory symlink.  This
parameter is ignored if the target exists (and the symlink is created
with the same type as the target).
History
Date User Action Args
2009-09-02 20:18:37jaracosetrecipients: + jaraco, lemburg, loewis, nnorwitz, jafo, eric.smith, giampaolo.rodola, swarren, r.david.murray
2009-09-02 20:18:37jaracosetmessageid: <1251922717.12.0.883117380874.issue1578269@psf.upfronthosting.co.za>
2009-09-02 20:18:35jaracolinkissue1578269 messages
2009-09-02 20:18:34jaracocreate