This queue is for tickets about the File-Path CPAN distribution.

Report information
The Basics
Id:
39949
Status:
resolved
Worked:
10 minutes
Users:
RICHE: 10 minutes
Priority:
Low/Low
Queue:

People
Owner:
RICHE [...] cpan.org
Requestors:
dmitry.bolshakov [...] bridge-quest.com
Cc:
AdminCc:

BugTracker
Severity:
(no value)
Broken in:
(no value)
Fixed in:
2.10_001



Received: from x1.develooper.com (x1.develooper.com [63.251.223.170]) by diesel.bestpractical.com (Postfix) with SMTP id D4D9A63CDEB for <bug-File-Path@rt.cpan.org>; Fri, 10 Oct 2008 09:53:55 -0400 (EDT)
Received: (qmail 28343 invoked from network); 10 Oct 2008 13:53:54 -0000
Received: from x16.dev (10.0.100.26) by x1.dev with QMQP; 10 Oct 2008 13:53:54 -0000
Received: from mail44.opentransfer.com (HELO mail44.opentransfer.com) (76.162.254.44) by 16.mx.develooper.com (qpsmtpd/0.43rc1) with SMTP; Fri, 10 Oct 2008 06:53:49 -0700
Received: (qmail 23615 invoked by uid 399); 10 Oct 2008 13:53:45 -0000
Received: from unknown (HELO ?192.168.14.4?) (80.249.179.82) by mail44.opentransfer.com with SMTP; 10 Oct 2008 13:53:45 -0000
Delivered-To: cpan-bug+File-Path@diesel.bestpractical.com
Subject: in cygwin and windows rmtree does not report any error if directory does not exist
MIME-Version: 1.0
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
X-Spam-Status: No, hits=-2.6 required=8.0 tests=BAYES_00
Return-Path: <dmitry.bolshakov@bridge-quest.com>
X-Spam-Check-BY: 16.mx.develooper.com
X-Original-To: bug-File-Path@rt.cpan.org
Date: Fri, 10 Oct 2008 17:53:20 +0400
X-Spam-Level: *
Message-Id: <48EF5E50.7020909@bridge-quest.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
To: bug-File-Path@rt.cpan.org
Content-Transfer-Encoding: 7bit
From: Dmitry Bolshakov <dmitry.bolshakov@bridge-quest.com>
X-RT-Original-Encoding: utf-8
Content-Length: 776
$ uname -a CYGWIN_NT-5.1 bolshakovxp 1.5.25(0.156/4/2) 2008-06-12 19:34 i686 Cygwin $ perl -v This is perl, v5.10.0 built for cygwin-thread-multi-64int (with 6 registered patches, see perl -V for more detail) $ perl -MFile::Path -e "print \$File::Path::VERSION" 2.04 ----- Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\bdimych>perl -v This is perl, v5.10.0 built for MSWin32-x86-multi-thread (with 5 registered patches, see perl -V for more detail) C:\Documents and Settings\bdimych>perl -MFile::Path -e "print $File::Path::VERSION" 2.04 ----- use File::Path; use Data::Dumper; rmtree "aaaaa", {error => \my $err}; print Dumper $err; <STDIN>; outputs $VAR1 = []; -- With best regards Dmitry Bolshakov
MIME-Version: 1.0
In-Reply-To: <48EF5E50.7020909@bridge-quest.com>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <48EF5E50.7020909@bridge-quest.com>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-30755-1430575875-1157.39949-0-0@rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 938
Created PR https://github.com/dland/File-Path/pull/5 On Fri Oct 10 09:54:09 2008, dmitry.bolshakov@bridge-quest.com wrote:
Show quoted text
> $ uname -a > CYGWIN_NT-5.1 bolshakovxp 1.5.25(0.156/4/2) 2008-06-12 19:34 i686 Cygwin > > $ perl -v > This is perl, v5.10.0 built for cygwin-thread-multi-64int > (with 6 registered patches, see perl -V for more detail) > > $ perl -MFile::Path -e "print \$File::Path::VERSION" > 2.04 > > ----- > > Microsoft Windows XP [Version 5.1.2600] > (C) Copyright 1985-2001 Microsoft Corp. > > C:\Documents and Settings\bdimych>perl -v > > This is perl, v5.10.0 built for MSWin32-x86-multi-thread > (with 5 registered patches, see perl -V for more detail) > > C:\Documents and Settings\bdimych>perl -MFile::Path -e "print > $File::Path::VERSION" > 2.04 > > ----- > > use File::Path; > use Data::Dumper; > rmtree "aaaaa", {error => \my $err}; > print Dumper $err; > <STDIN>; > > outputs > > $VAR1 = []; > >
MIME-Version: 1.0
In-Reply-To: <48EF5E50.7020909@bridge-quest.com>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <48EF5E50.7020909@bridge-quest.com>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-10114-1435333751-303.39949-0-0@rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 109
This issue has been resolved in dev release http://search.cpan.org/~riche/File-Path/Path.pm version 2.10_001.
MIME-Version: 1.0
In-Reply-To: <48EF5E50.7020909@bridge-quest.com>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <48EF5E50.7020909@bridge-quest.com>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-16333-1438036249-908.39949-0-0@rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 1584
I have read through this full thread a few times, and I find myself feeling pretty firmly opposed to this change. There is already a mechanism for determining whether any of the requested deletions failed, and it has been there for some time. (I am thinking, here, of the return value and the error reference.) Users already could have inspected if if they cared to, and if they did not, that is their choice, even if we would not make it the same way. If we were to change perl's core "mkdir" to warn on failure, rather than stick to its existing behavior, users would scream bloody murder. That's not the kind of change that the perl core makes lightly. File::Path is so important a piece of core ā€” and indeed was fundamentally core-only until v5.10 ā€” that I think it should try to stick to the same level of backward compatibility. But it may well be that I haven't quite grasped the motivation here. It sounds like, "users might be surprised that nothing got deleted, or why nothing got deleted," but the tools for checking this already exist, and are already documented. They're maybe not the interface we'd provide if we were starting afresh, but we're not. We're supporting decades of code with coders and maintainers who will (justifiably) scream bloody murder if we change their programs to emit warnings where they already understand the behavior. If I have misunderstood, and there is a greater issue at play, please let me know. Otherwise, the complaints here are just the tip of an iceberg, and we should avoid it by avoiding these new warnings. -- rjbs
MIME-Version: 1.0
In-Reply-To: <48EF5E50.7020909@bridge-quest.com>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <48EF5E50.7020909@bridge-quest.com>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-16333-1438036597-861.39949-0-0@rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 59
Whoops, I have responded to the wrong ticket. :-) -- rjbs
MIME-Version: 1.0
In-Reply-To: <48EF5E50.7020909@bridge-quest.com>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <48EF5E50.7020909@bridge-quest.com>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-19738-1438036982-1760.39949-0-0@rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 11
re-closing.


This service runs on Request Tracker, is sponsored by The Perl Foundation, and maintained by Best Practical Solutions.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.