On Fri, 9 Aug 2013 02:41:21 -0400, "Andreas Koenig via RT"
<bug-DBD-CSV@rt.cpan.org> wrote:
Show quoted text> Queue: DBD-CSV
> Ticket <URL:
https://rt.cpan.org/Ticket/Display.html?id=87684 >
>
> Sorry for the unspecified term 'irritating', I posted this in a bit of a hurry. What I was trying to say was:
>
> (1) that a testing setup that scans my /tmp/ directory, or any other of
> my directories should always be justified. Testing the ability to scan
> several directories can also be done by generating several directories
> and scan those, this would be less introsive and more to the point of
> testing. There is no inherent reason to scan my /tmp/ directory, so
> I'm irritated when a testing software does it.
The testing of /tmp/ can be changed - I will document that, by setting
(temporarily) the env variable that designate what should be used as
tmp. Usually that is something like $TMP or $TMPDIR.
There are several reasons to use $TMP. You might or might not agree
with any of these reasons being justification, but given that we want
to run on all supported OS's (Linux, Unix, MacOSX, HP-UX, AIX, VMS, and
Windows to name a few) we chose - after a lot of discussion with people
using those non-standard OS's, to rely on File::Spec->tmpdir () as
1. It is used quite extensive is other modules
2. It returns something guaranteed to be usable
3. It works on all OS's. Transparantly
If we create our own folder, and take the absolute path of that, the
functionality that we want to test isn't tested.
Again, if you do not want this test to be run using /tmp on the single
moment that you install the module (remember that this is not used
unless specified by *you* during actual use of the module), set $TMPDIR
tmpdir
Returns a string representation of the first writable directory
from a list of possible temporary directories. Returns the
current directory if no writable temporary directories are found.
The list of directories checked depends on the platform; e.g.
File::Spec::Unix checks $ENV{TMPDIR} (unless taint is on) and /tmp.
$tmpdir = File::Spec->tmpdir ();
Show quoted text> (2) if a testing software can have extremely different behaviour
> depending on the content of my /tmp/ directory, I would expect
> that this is communicated to the tester in form of a warning or
> a question to answer or an option to activate it, not as a
> sentence in the Changes file.
The *behavior* of the tests didn't change other than that the tests now
work on *all* supported OS's instead of just the ones that I had access
to. The *only* impact is that on some OS's the tests will take longer
if that folder is stuffed with a lot of files.
The content is not used at all.
Show quoted text> (3) I have plenty of seemingly hanging tests for DBD-CSV-0.41. Maybe
> this test or this new functionality has a bug or maybe my /tmp/
> directory is huge. We will only find out if the test stops scanning
> my /tmp/ directory. Please consider this for the next release.
set %TMPDIR% before running the tests
Show quoted text> Apart from that I have not posted for quite a while on PerlMonks.
> Maybe you can pont me to the posting?
Chatterbox
Aug 07 21:30:55 <cbstream> [Lady_Aleena] Which is the preferred CSV parser, Text or DBD CSV? I have an actual CSV file I would like to parse.
Aug 07 21:31:55 <cbstream> [Lady_Aleena] This thing has actual commas and a lot of quotes, and the first line is the headings.
Aug 07 21:36:02 <cbstream> [Lady_Aleena] My data files are all pipe separated values with no quotes so I use my own little fuction to parse mine normally. I haven't tried using a module in many years.
Aug 07 21:39:07 <cbstream> [Lady_Aleena] I think I need more caffiene. I forgot Text::CSV was hard to use.
Aug 07 21:55:03 <cbstream> [Lady_Aleena] Now I remember why I rolled my own parser for sep values files.
Aug 07 21:57:07 <cbstream> [Lady_Aleena] There are no headings saying "Putting your data into a hash".
Aug 07 22:06:52 <cbstream> [Lady_Aleena] /me gets something to eat.
Aug 07 22:25:29 <cbstream> [Lady_Aleena] /me gives up.
Aug 07 22:29:47 <cbstream> [Lady_Aleena] For me it figures Outlook 2003 can't make a usable CSV file. When it made the file, it didn't ignore line breaks in some fields, so put parts of fields on different lines. (face palm)
Aug 07 22:33:22 <cbstream> [Lady_Aleena] I can't parse it then, since neither Text nor DBD CSV goes from file to aoh or hoh in the documentation.
Aug 07 22:44:11 <cbstream> [Lady_Aleena] MLX, I need to figure out how to make it so the first line of the CSV file is read as the headings.
Aug 07 22:44:11 <cbstream> [Lady_Aleena] I think.
Aug 07 22:53:26 <cbstream> [space_monk] @Lady_Aleena: you can use Text:CSV to read your pipe separated data - just change the separator character when creating an instance
Aug 07 22:55:34 <cbstream> [Lady_Aleena] space_monk, my pipe separated files are a breeze to parse with my home rolled function, but parsing the csv created by Outlook 2003 with all its quirks is difficult since the documentation to the various CSV modules is incomplete.
Aug 07 23:00:11 <cbstream> [Lady_Aleena] Also, there isn't any special characters used at the end of each record.
Aug 08 08:21:57 <TuxCM-> [Lady_Aleena] late, but maybe you read backlog. "Which is the preferred CSV parser, Text or DBD CSV?" - Technically [mod://DBD::CSV] is not a parser: is is a DBD for [mod://DBI] to enable a database interface over CSV files. It uses [mod://Text::CSV_XS] to parse, but can be forced to use [mod://Text::CSV]
Aug 08 08:22:31 <TuxCM-> [Lady_Aleena] late, but maybe you read backlog. "Which is the preferred CSV parser, Text or DBD CSV?" - Technically [mod://DBD::CSV] is not a parser: is is a DBD for [mod://DBI] to enable a database interface over CSV files. It uses [mod://Text::CSV_XS] to parse, but can be forced to use [mod://Text::CSV]
Aug 08 08:22:34 <cbstream> [Tux] [Lady_Aleena] late, but maybe you read backlog. "Which is the preferred CSV parser, Text or DBD CSV?" - Technically [
http://search.cpan.org/perldoc?DBD%3A%3ACSV |DBD::CSV] is not a parser: is is a DBD for [
http://search.cpan.org/perldoc?DBI |DBI] to enable a database interface over CSV files. It uses [
http://search.cpan.org/perldoc?Text%3A%3ACSV_XS |Text::CSV_XS] t
Aug 08 08:27:35 <TuxCM-> [Lady_Aleena] "I can't parse it then, since neither Text nor DBD CSV goes from file to aoh or hoh" - read again, then use <c>getline_all ()</c> for AoA or <c>getline_hr_all ()</c> for AoH. The latter needs some setup
Aug 08 08:27:37 <cbstream> [Tux] [Lady_Aleena] "I can't parse it then, since neither Text nor DBD CSV goes from file to aoh or hoh" - read again, then use <c>getline_all ()</c> for AoA or <c>getline_hr_all ()</c> for AoH. The latter needs some setup
Show quoted text> Thanks,
--
H.Merijn Brand
http://tux.nl Perl Monger
http://amsterdam.pm.org/
using perl5.00307 .. 5.19 porting perl5 on HP-UX, AIX, and openSUSE
http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/
http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
RT for rt.cpan.org