Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #93139 > unrolled thread

Re: windows and file names > 256 bytes

Started byChris Angelico <rosuav@gmail.com>
First post2015-06-25 23:02 +1000
Last post2015-06-25 23:02 +1000
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: windows and file names > 256 bytes Chris Angelico <rosuav@gmail.com> - 2015-06-25 23:02 +1000

#93139 — Re: windows and file names > 256 bytes

FromChris Angelico <rosuav@gmail.com>
Date2015-06-25 23:02 +1000
SubjectRe: windows and file names > 256 bytes
Message-ID<mailman.64.1435237325.3674.python-list@python.org>
On Thu, Jun 25, 2015 at 9:06 PM, Mark Lawrence <breamoreboy@yahoo.co.uk> wrote:
>> 2. Is this a bug in Python? I would prefer if Python dealt with the gory
>> details of Windows' silly behavior.
>
>
> I don't see why Python should work around any particular limitation of any
> given OS.

Check out the multiprocessing module, and then tell me whether it's
better that Python paper over the OS differences or if you'd rather do
all that yourself. The biggest difference left between Windows and
POSIX is that on Windows, your main module has to be importable (which
doesn't hurt on POSIX). Python deals with all the mess of "can we
fork, or do we have to do it differently?".

ChrisA

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web