* James E Keenan [2017-04-12T22:15:22]
> For me the most interesting aspect of this fifth round is that 29
> distributions which appeared in order-of-battle-20170409.txt (the
> previous round focusing on no-dot) no longer appear in
> order-of-battle-20170412.txt. That is, their no-dot problems --
* Chad Granum [2016-12-13T11:35:19]
> ok, thanks for trying that, I will look into it when I have time and if
> nothing else at least explain why it behaves like it does. If it is a bug I
> will fix it.
This has remained a problem for me, so this morning I had a run through it, and
I still think
* Ricardo Signes [2016-12-18T09:08:23]
> When you call cmp_deeply($have, $want), objects found in $want are either
> Test::Deep::Cmp objects or not. If they are, they do their special test
> magic. If they are not, they are more or less compared to the data in $have
> withou
I've filed a PR against Test-Deep:
https://github.com/rjbs/Test-Deep/pull/52
addresses
https://github.com/rjbs/Test-Deep/issues/50
The idea is:
When you call cmp_deeply($have, $want), objects found in $want are either
Test::Deep::Cmp objects or not. If they are, they do their special te
* Chad Granum [2016-12-13T11:13:56]
> I would like to see the results when you use
> Test2::Tools::Subtest::subtest_streamed() which is the actual equivalent to
> Test::More::subtest().
Thanks for the pointer. I have tried this and got identical ("bad") results to
Test2::API::run_subtest:
~$
I've hit a nasty (to me) difference between Test2::API::run_subtest and
Test::Builder::subtest. Shout out to Matthew Horsfall for helping localize the
problem. Here's my trivial reproducer:
#!perl
use strict;
use warnings;
use Test::More;
use Test2::API;
my $code = sub {
if (for
* Chad Granum [2016-11-30T10:30:38]
> I do have implementation commentary however:
Thanks, greatly appreciated!
> * You should not be obtaining a context inside your subtest (specifically
> line 18
So, I've moved it to after the eval. I (think that I) need it inside the
subtest so that the ev
Often, I have a test like this:
subtest "do things with an api" => sub {
my $result = $api_client->do_first_thing;
is(
$result->documents->first->title,
"The Best Thing",
);
...
};
Sometimes, the result comes back with zero documents. ->first throws an
exception
* Chad Granum [2016-03-19T13:03:34]
> RJBS and I have spoken, and feel it is time to set a release date for
> Test2/Test-Builder. We have agreed that doing it at the QAH in Rugby is a
> good time. The plan is to release Test2 and the new Test::Builder as stable
> either at the end of the first day
* Ricardo Signes [2015-11-23T18:12:22]
> * make a set of GitHub issues for the punch list, tagged as such
https://github.com/Test-More/test-more/issues?q=is%3Aopen+is%3Aissue+label%3ATest-Stream
> * make GitHub issues for other topics to review, also tagged
More to come soon.
--
Wow, the last update on this was in April! Then stuff came up. Has all the
stuff that came up gone down? I hope so.
I think that there is not one person who wants the up-in-the-air-ness of
Test-Builder-on-Test-Stream to last longer than it has to. I sure don't. Now
that it seems like there is
* bulk88 [2015-04-25T23:56:23]
> Because of the rjbs post that supposedly (someone else should confirm this)
> minitest does not use Test::*, new Test::Simple can use all the XS it wants.
Re-confirmation welcome! For the record: My first check was scanning all the
tests run by the minitest make
* bulk88 [2015-04-25T17:57:19]
> Since Test::Stream::Context's core design uses weaken() everywhere, that
> means new Test::Simple always requires XS building (for Scalar::Util), which
> means it will never run on miniperl, and hence, new Test::Simple will never
> be in Perl core, is my understand
* Paul Johnson [2014-07-20T18:59:51]
> Hours worked:
>
> Total 25:00
Thanks, Paul, +1!
--
rjbs
signature.asc
Description: Digital signature
* David Cantrell [2014-06-26T09:19:00]
> I understand that Test::Builder::Tester is the way to go these days -
> and it's distributed with Test::Builder, so incompatibilities should
> never* happen.
Test::Tester is really nice and easy to use.
Test::Builder::Tester is awful and often requires th
* Paul Johnson [2014-05-20T17:50:35]
> In accordance with the terms of my grant from TPF this is the monthly
> report for my work on improving Devel::Cover covering April 2014.
Thanks, Paul, +1.
--
rjbs
signature.asc
Description: Digital signature
* Eirik Berg Hanssen [2014-01-31T10:17:53]
> Yeah; just name the package accordingly, and, screwy or not, it'll still
> work:
>
> package t::lib::MyPackage;
> sub import { print "import() was called\n" }
This is my advice as well as my custom.
--
rjbs
signature.asc
Description: Digital si
* Torbjørn Lindahl [2014-01-30T19:59:04]
> It seems t/lib is a common place to put modules used to support testing,
> how about having Test::More push that path to @INC if -d 't/lib' ? It would
I suggest this alternative:
use t::lib::MyPackage;
;)
--
rjbs
signature.asc
Description: Digita
Once Test::Simple 1.001002 is release, I will upload Test-Class 0.40, which
makes it pass its tests with 0.98 and previous as well as 1.001001 and later.
0.99 is broken.
You can test it here:
https://dl.dropboxusercontent.com/u/88746/perl/Test-Class-0.40.tar.gz
--
rjbs
signature.asc
Descr
* David Cantrell [2013-10-31T07:49:16]
> Thankyou for being careful, but I don't think you've got anything to
> worry about.
That was my thinking too, although I've seen problems with cases other than you
describe. Still, with Test::Builder, better overcautious than not. :-)
(My rule of thumb
NOW WITH MORE DIGITS!
We released 0.99 recently. There was a regression. We need a new release. To
sync up with the 1.005001 versioning, we are moving to X.YYYZZZ-style. I think
the longer-term goal will be to use Perlified semantic versions. For now, I'm
just dealing with important bugfixes,
Test-Simple has built up a nice set of changes in the two years since its last
release. Some of these are adjustments to changes in core for which
Test-Simple was patched in blead. Test-Simple 0.98_06 integrates (or replaces)
those fixes, and has other fixes of its own.
Please test your code wit
* Leon Timmermans [2013-09-17T11:26:40]
> Just as I expected, "make it a wiki" means it gets warnocked again.
>
> Can we please make a decision, or if we must first come to an agreement on
> how to make it?
Allow me to offer this:
https://github.com/Perl-Toolchain-Gang/ExtUtils-MakeMaker/pull
* Leon Timmermans [2013-09-18T19:21:44]
> Or both just setting $Test::Harness::switches = ''…
Yes. I was cleaning out ~/tmp on the flight over here and I found this dzil
plugin:
package inc::STFUEUMM;
use Moose;
extends 'Dist::Zilla::Plugin::MakeMaker';
use namespace::autoclean;
afte
* Ovid [2013-09-18T04:19:28]
> As I said in my previous email on July 7th: backwards-incompatible changes to
> the backwards-compatibility layer (Test::Harness) are not a good idea. The
> proper response is to have people impacted by this issue switch to
> TAP::Harness, as was suggested several ye
* Paul Johnson [2013-09-02T06:37:20]
> And I'm not really sure what a 50¢ explanation is, so I hope I've
> guessed correctly.
Perfect, thanks!
--
rjbs
signature.asc
Description: Digital signature
* Paul Johnson [2013-08-31T19:02:48]
> In accordance with the terms of my grant from TPF this is the monthly
> report for my work on improving Devel::Cover covering August 2013.
+1, thanks, Paul!
> 5.18.1 breaks Devel::Cover.
I'm very sorry to have been part of the problem, here. I've made a c
* Paul Johnson [2013-08-31T19:01:09]
> In accordance with the terms of my grant from TPF this is the monthly
> report for my work on improving Devel::Cover covering July 2013.
+1,
Thanks, Paul!
> The rest of the work this month was spent on p5cover. This is the project to
> get test coverage of
* Paul Johnson [2013-08-31T18:59:11]
> In accordance with the terms of my grant from TPF this is the monthly
> report for my work on improving Devel::Cover covering June 2013.
+1, thanks Paul.
--
rjbs
signature.asc
Description: Digital signature
* Eric Wilhelm [2013-07-04T17:33:45]
> # from Leon Timmermans on Thursday 04 July 2013:
> >> ewilhelm : We should keep the original change, but update EUMM to
> >>restore -w
> >
> >I'm not sure that's what he meant.
>
> Yeah no. I said get rid of Test::Harness.
>
> TAP::Harness provides a cle
* Leon Timmermans [2013-07-04T14:04:21]
> By what process? Define consensus? Given Andy is the official
> maintainer and Ovid is the effective maintainer, I don't think they
> need our consensus a priori.
06perms.txt says:
Test::Harness,ANDYA,m
Test::Harness,MSCHWERN,c
Test::Harness,OVID,c
I just submitted:
https://github.com/Perl-Toolchain-Gang/Test-Harness/pull/16
...to document two undocumented changes. First, the removal of "turn on -w by
default with no easy way to turn it off" and secondly the reversion of that.
These commits are, respectively:
https://github.com/Perl
* Paul Johnson [2013-06-23T18:43:41]
> In accordance with the terms of my grant from TPF this is the monthly
> report for my work on improving Devel::Cover covering May 2013.
Thanks, Paul! Looks good. I look forward to putting some of this work to good
use myself!
--
rjbs
signature.asc
Desc
* Paul Johnson [2013-05-01T16:40:17]
> In accordance with the terms of my grant from TPF this is the monthly
> report for my work on improving Devel::Cover covering April 2013.
> [...]
> This month I released Devel::Cover 1.02 but, apart from that, almost all of my
> work on Devel::Cover was eithe
* Paul Johnson [2013-05-01T16:38:26]
> In accordance with the terms of my grant from TPF this is the monthly
> report for my work on improving Devel::Cover covering March 2013.
+1, thanks, Paul!
--
rjbs
signature.asc
Description: Digital signature
* Adrian Howard [2013-04-27T20:09:09]
> On 27 April 2013 15:19, Ricardo Signes wrote:
> > Test::Exception fails, which breaks a lot of my basic toolchain from
> > installing.
>
> T::E 0.32 just uploaded that kills the false failure.
Thanks! With that, the next problem
* "Michael G. Schwern" [2013-04-25T13:35:49]
> 0.98_05 is a release candidate for 0.99. I would say this is the last
> stable release of Test::More before 1.5.0 but hahahaha I won't say that.
> https://metacpan.org/release/MSCHWERN/Test-Simple-0.98_05/
Test::Exception fails, which breaks a lot o
* Paul Johnson [2013-03-07T17:38:54]
> In accordance with the terms of my grant from TPF this is the monthly
> report for my work on improving Devel::Cover covering February 2013.
Great, thanks, +1!
> Finally, David Golden politely observed that the coverage reporting for ||=
> operators in his
* Paul Johnson [2013-02-11T15:53:10]
> I'm pleased to be able to report that we've agreed to continue with the second
> half of the grant.
Excellent!
> I'd like to publicly thank Ricardo Signes and Florian Ragwitz for their help
> and support in managing the first h
* James E Keenan [2013-01-02T22:39:21]
> On 1/2/13 9:36 AM, Paul Johnson wrote:
> >Last week I mentioned the pull requests I had received. I this week I merged
> >a pull request from Steffen Schwigon adding some important modules to
> >cpancover.com. I'm always happy to add modules that people w
* Paul Johnson [2013-01-02T09:36:45]
> In accordance with the terms of my grant from TPF this is the report for
> weeks 30-32 of my work on improving Devel::Cover.
> [...]
> Total 8:50
Thanks, Paul. Interesting report, and good luck!
+1
--
rjbs
signature.asc
Description: Digital signat
* Paul Johnson [2012-09-07T10:36:52]
> In accordance with the terms of my grant from TPF this is the monthly
> report for my work on improving Devel::Cover covering August 2012.
+1, thanks very much, Paul!
--
rjbs
signature.asc
Description: Digital signature
* Paul Johnson [2012-08-01T11:48:43]
> In accordance with the terms of my grant from TPF this is the monthly
> report for my work on improving Devel::Cover covering July 2012.
Thanks Paul, +1.
--
rjbs
signature.asc
Description: Digital signature
* Paul Johnson [2012-07-12T13:36:26]
> > Feature request: some way of easily seeing just my dists.
>
> >>TODO
>
> I can't promise when I'll get around to it, but I do have plans for
> extending cpancover. However, this work is fairly well decoupled from
> the core of Devel::Cover, so if anyone
* Paul Johnson [2012-06-15T06:07:44]
> In accordance with the terms of my grant from TPF this is the monthly
> report for my work on improving Devel::Cover covering May 2012.
Thanks, Paul! Looks good to me.
--
rjbs
signature.asc
Description: Digital signature
> David Golden writes:
> > I plan to expand further on this idea of separation at the QA
> > Hackathon in the spring (if I don't start working on it sooner). I'd
> > like to get all CPAN clients able to use an index completely separate
> > from a given repository, where the index could, for examp
Sorry for the long delay. Lately I'm task-switching at a slow pace. Also, I'm
quoting you out of order.
* Michael G Schwern [2011-11-30T17:16:47]
> RJBS wrote,
> > The only case when the programmer needs to know about the Mouse
> > underpinnings is when hacking on the dist itself, not not ever
* Michael G Schwern [2011-11-30T15:22:51]
> On 2011.11.30 7:20 AM, Ricardo Signes wrote:
> > re: "internal use"
> >
> > What does "internal" define here? What are the boundaries of the space to
> > which TB2::Mouse use is internal?
>
>
re: "internal use"
What does "internal" define here? What are the boundaries of the space to
which TB2::Mouse use is internal?
In what scenarios do I have to write something that uses it?
If I do that, am I likely using Mouse sugar?
--
rjbs
Please stop cc'ing my personal email address on this mailing list mail. I'm
already a subscriber. It just pollutes my "personal mail from friends"
folders.
--
rjbs
* "Philippe Bruhat (BooK)" [2011-11-03T20:25:25]
> Here are some news about the Perl QA Hackathon 2012.
I have very little to offer other than: Good luck, this all sounds fantastic,
and I hope I can make it! As others have said, the very expensive venue sounds
very nice, but even if somebody wa
* Michael G Schwern [2011-10-29T05:20:07]
> [ What if subtests stop indenting? ]
Sorry, I'm quite late to the party.
I really like the isolated planning of subtests, and the visual indenting, and
(least of the three) the potential for building a better visualizer that works
with the subtest orga
* David Golden [2011-08-22T22:23:42]
> On Mon, Aug 22, 2011 at 7:07 PM, Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 wrote:
> > To the usual suspects on this list, especially the ones who could not attend
> > the last times: when do you have time around April? (Traditionally, the QA
> > hackathon is from Saturday to Monday
* Andy Armstrong [2011-04-11T14:54:13]
> On 11 Apr 2011, at 19:45, Ricardo Signes wrote:
> > Thanks, but I'm afraid I wasn't clear about what I was looking for. I need
> > to know how to get from the airport to the hotels or thereabouts. Using
> > the address stri
* Leon Timmermans [2011-04-10T12:33:49]
> On Sun, Apr 10, 2011 at 5:26 PM, Ricardo Signes
> wrote:
> > Could some friendly Netherlands resident please reply or update the wiki
> > with helpful directions? Thanks!
>
> Google Maps worked fine for me, I've added li
The QA hackathon wiki suggests that directions to the hotels can be found at
http://2011.qa-hackathon.org/qa2011/wiki?node=Accommodation but I do not see
any, and Google Maps wants to give me directions to Kerkweg and can't find a
Kerkstraat.
Could some friendly Netherlands resident please reply
* Ovid [2011-02-17T07:43:16]
> > It would be nice if this was a custom comparator for Test::Deep, then you
> > would be apply the "almost" to lists of arbitrarily complex items and also
> > conduct that test at any level of the data structure (including nesting if
> > you feeling really fruity),
>
* Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 [2011-01-21T15:40:37]
> this year's prospective date for the QA hackathon in Amsterdam is 16-18
> April.
> Please reply until Monday morning European time whether this is suitable for
> you, or you would rather have a different date.
Those dates are great for me. My only hop
Tonight I uploaded Test::Deep 0.108. The changes made are very small, and
should not affect anyone other than some edge cases in which it should be
faster.
Many of the open bugs relate to unfortunately named exports like "blessed" and
"isa," and to behavior that should probably change but would
I've recently uploaded my new Moose-based system for writing reusable test
behavior. I'm very happy with it so far and hope that it can be useful to
others, too. I have written about the system and how it works, with links to
further material, here:
http://rjbs.manxome.org/rubric/entry/1858
This morning I released Test::Deep 0.107
http://search.cpan.org/~rjbs/Test-Deep-0.107/
It has a very small number of changes pulled entirely from the RT queue. I
will continue to make small releases over the next few weeks to try to clear
out the queue. When I feel I've dealt with the bugs t
* Michael Peters [2010-02-02T11:13:26]
> Maybe have the option to UTF8 stdout/stderr and just send the
> characters and let the display handle it. But I don't think it
> should be the default. Unicode is tricky and lots of unicode
> characters can be combined in ways that look identical to humans
* Shawn H Corey [2010-01-03T07:22:01]
> Leo Lapworth wrote:
> > Maybe someone could get a grant to hire someone/a company with design skills
> > to come up with a better logo than the onion?
>
> I always thought that something to do with pearls would be nice.
The problems with pearls include: (a
* Pedro Figueiredo [2010-01-03T07:06:19]
> On Sun, Jan 3, 2010 at 11:40 AM, chromatic wrote:
> >
> > If the design of perl.org had been up to me, I'd have spent much more time
> > promoting the Perl brand instead of the proprietary brand of a privately
> > held corporation.
>
> For better or for
* Leo Lapworth [2010-01-03T06:21:21]
> Almost every person (of a dozen non-techies & .net developers in my office)
> I showed the Onion to were confused by it. They thought it was a 'sad' thing
> about making you cry, or just irrelevant. With the camel they thought it was
> a 'nice' image, e.g. th
* Jonathan Swartz [2009-07-31T14:57:04]
> Justin Devuyst kindly pointed me to
>
> Module::Install::AuthorTests
>
> which appears to have the desired behavior if one is using
> Module::Install (which I happen to be). Thanks again.
...as long as you're looking at AuthorTests, have a look at i
* David Golden [2009-06-30T14:46:47]
> Well, if you're doing interface design, one of the first things that
> comes to mind is that the name of the test should come first, not
> last.
...I basically liked everything you had to say here:
> test "label goes here" => is( $have, $want ) => diag
* Ovid [2009-06-30T10:21:24]
> The latest developer release of Test::More allows subtests. Subtests are
> great in that they solve a lot of problems in advanced Perl testing, but they
> have required a change in Test::Builder. Previously you could do stuff like
> this:
I updated my Test:: librar
* Ovid [2009-04-06T10:52:33]
> >
> > I thought it might be nice to give the group a description, but really just
> > diagging a description should be good enough for me. I can wait for TAP 15
> > with preludes, envelopes, and the SWAK marker.
>
> Actually, you do a get description:
>
> plan
* Ovid [2009-04-06T04:35:41]
> Wondering if anyone's played with nested TAP yet and has any
> comments/requests/questions? Lot's of people have asked for it, so it would
> be good to make sure we've got it right before it's pushed out the door.
I've given it a bit of a look-over, and I think it'
* Michael G Schwern [2009-03-31T18:22:50]
> > What if display types could be provided informationally in the TAP stream.
> > The stream could include:
> >
> > want: foo bar
> > have: foo bar
> > presentation: Some::Plugin
> >
> > With the plugin installed, the presentation layer could fix
I'm mostly sending this email because I had an idea, and it's late, and I don't
want to forget.
Today it occured to me that many Test:: extensions are more about better
diagnostic output than better test comparison.
This stinks:
want: foo bar
have: foo bar
So you write some plugin that doe
* Salve J Nilsen <[EMAIL PROTECTED]> [2008-10-28T14:54:07]
> David Cantrell said:
> >On Mon, Oct 27, 2008 at 01:40:03PM +0100, Salve J Nilsen wrote:
> >
> >>I think _some_ kind of shaming should be allowed. Carrots are good, but
> >>sticks work too when applied in a respectable fashion.
> >
> >They
* Andy Lester <[EMAIL PROTECTED]> [2008-10-28T13:03:24]
> >has-test-pod and has-test-pod-coverage ones (if you find that any of my
> >modules meet those metrics, please file a bug report.)
>
> Oh, come on Eric, I'm proud of TP (which is really brian's) and TPC!
>
Hey, I love those modules... bu
* Andy Armstrong <[EMAIL PROTECTED]> [2008-09-19T05:24:40]
>
> I'd lean towards epoch for easier comparison on SQLite.
I tend to use epoch in SQLite, too, but it's worth nothing that iso8601 is much
easier for humans, and SQLite can compare either one pretty well, as 8601
strings are sortable. T
* "David E. Wheeler" <[EMAIL PROTECTED]> [2008-09-03T13:27:08]
> http://cpantesters.perl.org/author/DWHEELER.rss
Now that there's a new maintainer, I should send another email... this file,
for me is so large (6,680,062 bytes) that my RSS reader times out trying to
retrieve it.
Ugh.
--
rjbs
* Eric Wilhelm <[EMAIL PROTECTED]> [2008-08-21T12:46:59]
> # from Ovid
> >1. YAML is prettier.
> >2. JSON, unlike YAML, is stable.
> >
> >Let's not forget that the debated requirement for diagnostics is that
> > the generators and consumers speak the same language
>
> Does it have to be just one
* Ovid <[EMAIL PROTECTED]> [2008-08-21T12:28:52]
> Let's not forget that the debated requirement for diagnostics is that the
> generators and consumers speak the same language, not that the *consumer*
> emit anything in particular. If you prefer the appearance of YAML to JSON,
> have the consumer
* Ovid <[EMAIL PROTECTED]> [2008-08-21T05:36:11]
> Both of us found this much cleaner. However, this might have unexpected
> consequences. It also highlights the issue of Test::Harness's long-standing
> practice of stripping the .t extension from filenames. Why? If we want other
> extensions, strip
* chromatic <[EMAIL PROTECTED]> [2008-08-20T13:59:14]
> Aren't these two separate concerns, human versus machine readability? The
> latter rarely respects ambiguity.
Yes.
Right now, there seem to be two pro-YAML arguments.
(1) It's easier to for humans read.
Sure. I will admit that. It is e
* Jeffrey Thalhammer <[EMAIL PROTECTED]> [2008-08-20T12:42:49]
> But there is some debate about whether the MANIFEST and other
> metafiles should be put in the source code repository. My gut feeling
> is that MANIFEST is a generated file, therefore it does not go in the
> repository. Instea
* Michael G Schwern <[EMAIL PROTECTED]> [2008-08-18T12:26:54]
> YAML types can be little more than local tags which only have meaning to that
> particular document.
>
> name: !customer Evil Business Guy Made Of Butter
Yeah, that's neat and everything, but there aren't any Perl implementations
* Ovid <[EMAIL PROTECTED]> [2008-08-18T11:17:25]
> Oh, definitely agreed. I cannot assert that non-Perl implementations of JSON
> are any better, but JSON is simple enough that I'm pretty damned sure they
> are. However, YAML is so problematic that I *CAN* state that non-Perl
> versions are often
* David Golden <[EMAIL PROTECTED]> [2008-08-18T09:27:57]
> What's the latest consensus on the "best" pure-perl JSON module? And
> ditto for JSON via XS?
JSON and JSON::XS, most likely. Certainly JSON::XS.
--
rjbs
* Ovid <[EMAIL PROTECTED]> [2008-08-18T06:50:00]
> JSON is fairly well implemented and new implementations are trivial. This is
> not true for YAML. Trying to define a minimum standard of YAML for extended
> TAP is a quagmire. With JSON, we can punt and just point to a fairly
> well-established
> > On Aug 6, 2008, at 20:12, Michael G Schwern wrote:
> > >So I encourage folks to use "have" and "want" in the future. I'll
> > >be using them in Test::Builder2.
Test.php updated and released.
--
rjbs
* "David E. Wheeler" <[EMAIL PROTECTED]> [2008-08-07T00:31:27]
> On Aug 6, 2008, at 20:12, Michael G Schwern wrote:
>
> >So I encourage folks to use "have" and "want" in the future. I'll
> >be using them in Test::Builder2.
>
> Good call. Change committed to pgtap and Test.Builder.
and PyTAP,
His email is bustified.
http://rafb.net/p/vD8hRk81.html
FWIW, I get the same results.
--
rjbs
* brian d foy <[EMAIL PROTECTED]> [2008-06-10T12:27:29]
> I'd like to see the metircs that only talk about the quality of the
> distribution, and leave everything else alone. If it's something I can
> fix by doing something to the distribution itself, measure it. If it's
> anything else, leave it o
* Michael G Schwern <[EMAIL PROTECTED]> [2008-04-11T07:01:19]
> Here's the descriptive way to specify how the diagnostic keys work.
>
> 1) We reserve every key which begins with a lower case letter
> 2) We say nothing about anything else
> 3) All keys are optional
I thought this had been the re
* David Golden <[EMAIL PROTECTED]> [2008-03-31T10:07:57]
> On Mon, Mar 31, 2008 at 9:36 AM, Andy Armstrong <[EMAIL PROTECTED]> wrote:
> > I'm getting in on Thursday night - so I'll be around. Just planning to
> > wander around taking pictures but could be persuaded by something more
> > structur
After having this task languish in my todo for years, at least, I have finally
reduced my goal to the important 90% and applied some JFDI.
Pod::Coverage::TrustPod acts like Pod::Coverage::CountParents, but accepts
non-whitespace lines inside "Pod::Coverage" POD targets as "trustme"
instructions.
* Michael G Schwern <[EMAIL PROTECTED]> [2008-03-26T04:15:47]
>> Not trying to cause repo-wars, but I think I'll need to use git
>> actively for something before I really start to grok it.
>
> I had the same thoughts. My concern is that we'll be spending time futzing
> with git rather than hackin
First, ExtUtils::FakeMaker is now Module::Faker. Schwern suggested that
ExtUtils should no longer be used, and gave excellent reasoning, summed up
here:
http://www.perlfoundation.org/perl5/index.cgi?extutils
So, that's done. There haven't been any changes worth mentioning, yet, in its
docume
Lately, we're doing a lot of work on some for-now internal tools that operate
on CPAN archives as a whole. They're sort of like CPAN::Mini and
CPAN::Mini::Inject, writ large.
Doing stuff like unpacking an entire CPAN mirror to analyse its contents and
prereqs is a real drag, though. We also nee
* Eric Wilhelm <[EMAIL PROTECTED]> [2008-02-25T12:53:03]
> # from Ricardo SIGNES
> # on Monday 25 February 2008 04:59:
>
> >Basically, it lets you say "author_tests('xt')" in your Makefile.PL
> > (using Module::Install) to have a directory (or direct
I thought I'd relay my journal post here:
http://use.perl.org/~rjbs/journal/35746
Basically, it lets you say "author_tests('xt')" in your Makefile.PL (using
Module::Install) to have a directory (or directory tree) of tests run only by
the module's authors.
--
rjbs
* Miguel Pignatelli <[EMAIL PROTECTED]> [2008-01-08T10:10:00]
> Is there a possibility of getting involved in the phalanx project?.
> I'm a regular Perl user trying to improve his knowledge and being able
> to help the community.
Absolutely. A very simple way to do this is to pick a distribution
* Andy Armstrong <[EMAIL PROTECTED]> [2007-12-10T11:52:33]
> On 10 Dec 2007, at 16:49, Ovid wrote:
> >Seems Ricardo Signes likes this idea, too:
> >
> > http://use.perl.org/~Ovid/journal/35076
>
>
> Who? :)
:'(
I like this idea so much that if you poi
* David Cantrell <[EMAIL PROTECTED]> [2007-08-03T16:21:44]
> David Golden thought that this might be more useful as a web thing than
> done by email by the CPAN testers, so I hacked something up:
> http://cpandeps.cantrell.org.uk/
That's pretty cool, even if it is a foul, disgusting hack.
--
r
1 - 100 of 152 matches
Mail list logo
