MIME-Version: | 1.0 |
X-Spam-Status: | No, score=-3.699 tagged_above=-99.9 required=10 tests=[AWL=-1.000, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham |
X-Spam-Flag: | NO |
content-type: | text/plain; charset="utf-8"; format="flowed" |
Reply-To: | jim.avera@gmail.com |
Message-ID: | <542AF559.3010007@gmail.com> |
X-Received: | by 10.68.216.35 with SMTP id on3mr71697295pbc.34.1412101467983; Tue, 30 Sep 2014 11:24:27 -0700 (PDT) |
X-Virus-Scanned: | Debian amavisd-new at bestpractical.com |
X-Spam-Score: | -3.699 |
Received: | from localhost (localhost [127.0.0.1]) by hipster.bestpractical.com (Postfix) with ESMTP id EF67824062C for <cpan-bug+File-Path@hipster.bestpractical.com>; Tue, 30 Sep 2014 14:24:35 -0400 (EDT) |
Received: | from hipster.bestpractical.com ([127.0.0.1]) by localhost (hipster.bestpractical.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z5RdYFcdcva4 for <cpan-bug+File-Path@hipster.bestpractical.com>; Tue, 30 Sep 2014 14:24:35 -0400 (EDT) |
Received: | from la.mx.develooper.com (x1.develooper.com [207.171.7.70]) by hipster.bestpractical.com (Postfix) with SMTP id B6EB4240612 for <bug-File-Path@rt.cpan.org>; Tue, 30 Sep 2014 14:24:34 -0400 (EDT) |
Received: | (qmail 27244 invoked by alias); 30 Sep 2014 18:24:33 -0000 |
Received: | from mail-pd0-f181.google.com (HELO mail-pd0-f181.google.com) (209.85.192.181) by la.mx.develooper.com (qpsmtpd/0.28) with ESMTP; Tue, 30 Sep 2014 11:24:31 -0700 |
Received: | by mail-pd0-f181.google.com with SMTP id z10so5623450pdj.40 for <bug-File-Path@rt.cpan.org>; Tue, 30 Sep 2014 11:24:28 -0700 (PDT) |
Received: | from ?IPv6:2602:30a:2ccd:6950:a582:383d:990d:db72? ([2602:30a:2ccd:6950:a582:383d:990d:db72]) by mx.google.com with ESMTPSA id g13sm15901003pat.45.2014.09.30.11.24.26 for <bug-File-Path@rt.cpan.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Sep 2014 11:24:27 -0700 (PDT) |
Authentication-Results: | hipster.bestpractical.com (amavisd-new); dkim=pass header.i=@gmail.com |
Delivered-To: | cpan-bug+File-Path@hipster.bestpractical.com |
Subject: | Please document that File::Path::rmtree may not be used with threads |
User-Agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
Return-Path: | <jim.avera@gmail.com> |
X-RT-Mail-Extension: | file-path |
X-Original-To: | cpan-bug+File-Path@hipster.bestpractical.com |
X-Spam-Check-BY: | la.mx.develooper.com |
Dkim-Signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=TR10jp+10BCLVYOjcbvswBiNdShHzuKkKbzFDvw+chU=; b=VwwxnxGdaYEyBtUROCBwxTfAbd5FUMgLFgl7faXKpSm33E0v2M3l9dFmRopGYBCAvm jeOKVNBZwNyR38vYCVhqmJLNPU3VoDCGqMvURTjOAssoX5V9A3xNaNcaoJFPRfuqkcaV hnM+Rq1wKpOsHE+Wv23xuGajH3uf0J4LUmHzNmv72woC6OeFzdeaxXqmSNlZqnvlzRXV P3vv8n4q89Y/9RTTvokZRP0SvrzXW6wtjx1fsqAZ4c7AvNA9+/DyLUvr5LtdCdRnljim AsSDhhh8n40A0Sd4TSbrifqMe4OeqO8PINek/2HR7eq/ut1VS0i1lAHHmcAof+nK7/tD Y9yQ== |
Date: | Tue, 30 Sep 2014 11:24:25 -0700 |
X-Spam-Level: | |
To: | bug-File-Path@rt.cpan.org |
Content-Transfer-Encoding: | 7bit |
From: | Jim Avera <jim.avera@gmail.com> |
X-RT-Original-Encoding: | iso-8859-1 |
X-RT-Interface: | |
Content-Length: | 967 |
File::Path::rmtree (v2.08) changes the working directory, which makes it
incompatible with Perl threads (the cwd is process-global, shared by
concurrent threads).
PLEASE document this clearly in the pod to save people hours of
unnecessary debugging.
This was reported/requested last March in bug #94209. That bug received
no comment from the maintainers. Presumably this means nobody has
bandwidth to re-implement rmtree, which is perfectly understandable.
But the request to at least document the limitation remains valid. I
spent many long days debugging a multi-threaded app and would very much
like to have been spared that useless exercise.
Documenting the limitation would save many people lots of work.
Thank you.
P.S. bug#94209 has a comment "already been reported into perl RT without
any reply" and referencing URL
https://rt.perl.org/Public/Bug/Display.html?id=112008 but clicking that
link gives error "Could not load ticket 112008".