user-pic

Ether

  • Commented on Pod::Readme v1.0.2 released
    Integration with Pod::Weaver would be nice -- as that is an existing framework for allowing one to parse and mutate existing pod documents. I could see Pod::Readme being useful for inserting content that is only useful in a README, rather...
  • Commented on A pre-release of Pod::Readme is available on CPAN
    What limitations are there as a result of not using a full POD parser? Are there certain syntax elements that are not recognized, a depth limitation to nested elements, etc?...
  • Commented on CPAN Testers & pre-requisite reporting
    > The "DEVREL" prefix will be appended as soon as there is *anything* in the chain I like this a lot, and it's similar to what I was thinking too. However, I realize now there's a problem here -- the...
  • Commented on Test::More has lots of crazy new development that's breaking my modules
    > I don't think CPAN Testers is doing the right thing by using broken Test::More's that aren't available for normal installations. I strongly disagree. What if these Test::More changes *were* production ready? Receiving these failing reports, before Test::More sees a...
  • Commented on If your core perl documentation uses =encoding, please test the new perldoc release
    However, `perldoc Moose` does not -- the rendering of the right-to-left portion of Yuval's name (in the AUTHORS section) is garbled (the bullet appears at the end of the line; the parentheses are misplaced). This may be due to my...
  • Commented on If your core perl documentation uses =encoding, please test the new perldoc release
    `perldoc Acme::LookOfDisapproval` and `perldoc Acme::ಠ_ಠ` both look good :)...
  • Commented on I hate unpacking sub calls with shift
    > This one is very good: No, it's not - it uses Devel::Declare, which is a giant ball of crack that is actively discouraged by its authors and everyone who understands the improvements made in 5.14 that make this ball...
  • Commented on Data::Dumper Debugging
    I'm running OSX 10.8 and I have: GNU bash, version 3.2.48(1)-release (x86_64-apple-darwin10.0)...
  • Commented on Rewriting Pod::Readme
    There is a MooX::Role::Pluggable, which may serve your needs. But it's also not terribly difficult to write this bit of code manually, using Module::Pluggable....
  • Commented on Single-page POD for a distribution
    We need someone to add a split-screen feature to $favourite_browser_here....
  • Commented on Rewriting Pod::Readme
    One other thing, for Robert -- unless you're doing some really funky things with Moose, I'd suggest using Moo instead, as it is lighter weight and will run faster in a toolchain environment....
  • Commented on Rewriting Pod::Readme
    I see some great ideas here! Something you might want to look at for inspiration is Mike Doherty's https://metacpan.org/pod/Dist::Zilla::Plugin::InstallGuide (which I use in my plugin bundle) that generates an INSTALL file that contains simple install instructions using various cpan clients...
  • Commented on Quacks who write software make us all look bad
    Heh, I happened to see the headline of your reddit post about 5 seconds before skimming b.p.o, and went "whoa, everybody's talking about this guy today" :)...
  • Commented on Planet Moose - August 2014
    *lol* at the easter egg :)...
  • Commented on Please don't use ::Tiny unless it meets the ::Tiny criteria, thanks!
    > Maybe make a Dist::Zilla plugin to test for it all? https://metacpan.org/pod/Dist::Zilla::Plugin::OnlyCorePrereqs can check for one part of it. [Test::MinimumVersion] can test for another....
  • Commented on Give your module a good SEE ALSO section
    Something to remember for all of Neil's excellent posts in this series - if you don't have any distributions of your own that you can patch, you can patch other people's distributions!...
  • Commented on Classify your RT tickets on CPAN Day!
    This is, IMO, a problem with a lot of distributions......
  • Commented on Curating CPAN sometimes means really deleting stuff
    > Games::Golf Interesting! From the name alone, I might have thought that this was for scoring the *real* game of golf - calculating handicaps, comparing users against par for each hole, etc....
  • Commented on Don't be afraid to rename your module / dist
    Thanks Neil! For authors of modules in the MooseX:: or MooX:: namespace: please note that this namespace ought to be used only for Moose *extensions*. If your module is simply a role that happens to use Moose to provide attributes...
  • Commented on The 'right' name for your CPAN distribution
    Great points, Neil! Also - if your distribution could be named better, why not perform that renaming on CPAN Day (August 16)? :)...
  • Commented on perlbrew on OSX
    > As always ... it was down to me doing something daft. So it is for all of us :)...
  • Commented on The ghost of CPAN Days past
    I have a Task-Kensho-* release planned soon. Challenge accepted. :)...
  • Commented on How to Run a Single Test via Dist::Zilla
    There is a Build.PL in the repository for that dist, so you should be able to simply: perl Build.PL && ./Build && ./Build test -- or just perl Build.PL && ./Build && perl -Mblib t/foo.t....
  • Commented on Moose MonkeyPatching With a Mock UserAgent
    Nice! I've definitely used method modifiers (either directly in in Moose, if it's a Moose class, or otherwise using Class::Method::Modifiers) for targeted mocking - it feels a bit ugly, but it does do the job! :)...
  • Commented on Conflict Resolution: local::lib and git's Perl
    This seems like a strange problem - e.g. I use perlbrew and local::lib extensively, and always have PERL5LIB set, but I've never had an issue with git commands....
  • Commented on Giving up on weekly neoCPANisms
    > a release that was pushed on time but indexed and put on CPAN after the deadline Werd. This upload broke my once-a-day and neocpanism-a-week chains: Request entered on: Sat, 31 May 2014 23:59:10 GMT Request completed: Sun, 01 Jun...
  • Commented on When a fat comma is confusing
    heh, I thought about having map_response and some of the other interfaces accept more parameters, so as to add multiple mappings at once, but I never implemented it because of "YAGNI" - figuring it would be pretty easy for the...
  • Commented on When a failure is not a failure
    tobyink is correct. Consider: $; perl -Mwarnings -le 'exit 1 ? 2 : 3' ; echo $? Useless use of a constant in void context at -e line 1. Useless use of a constant in void context at -e line...
  • Commented on Sick of being mocked by unit tests
    Nice post. I also loathe mocked objects nearly universally. Also, some implementations are problematic -- e.g. Test::MockObject on the CPAN has a number of implementation issues that cause me to pull its use out of any project I can. Here's...
  • Commented on Perl in a Developing Country
    Welcome! I look forward to reading more!...
Subscribe to feed Recent Actions from Ether

  • CPAN Testers commented on CPAN Testers & pre-requisite reporting

    Your assumption that there would be virtually no changes after the Metabase is incorrect. There would be several. Again we've had this discussion before and as Toby also points out, the problem dependency may be nothing to do with the distribution that is a development release. It is not a trivial task to check this in the client either.

    My intention, as Ether notes, is to use the Admin site to allow others to correctly attribute the report to the offending module. It's a slightlymore long-winded and manual process, but it will be more consistent when re-attributing reports.

  • Peter Rabbitson commented on CPAN Testers & pre-requisite reporting

    I still maintain that "oh, changing the set of test tags beyond the current 4 is too hard" is a dead-end strategy. In order to remain relevant the cpantesters infrastructure must allow for extra test-type additions anyway - the current set is too limited.

    In addition I do not believe (given I know and admire the skill of everyone involved) that the current stack is written so badly, that it will be a monumental effort to allow for "super-namespacing" of the test results. At worst it should be a couple day slog, perfect for a hackathon... if there only was an upcoming one ;)

    T…

  • Robert Rothenberg commented on A pre-release of Pod::Readme is available on CPAN

    @leon I am in the process of changing it from Moose to Moo.

    As for v5.10, I prefer using some of the features of v5.10 to simplify the code. If I get enough feedback from module authors asking for support of 5.8, I'll look into changing that. (Note: this module is intended for module authors, and shouldn't be necessary just to build a module.)

    @ether: Bugs in previous versions were always due to limitations of different POD parsers, which is why I gave up on trying to use one. The current version only cares about =begin/=end and =for elements, really, though it doesn't suppor…

  • Andreas Koenig commented on CPAN Testers & pre-requisite reporting

    Is this discussion probably just about limitations we have, as individuals and as a community? I see it that we have microcosmoses of people and modules and interactions between individual entities. Whenever some combination of those does not work we get some sort of problem and impact. And what we do about it is to watch carefully bad interactions so we can countersteer. More tags? What a brilliant idea if everybody could tag in advance what a release would break. But why release at all, then? If people could tag their software as broken in advance, why would they not fix their crap…

  • perlancar commented on Pod::Readme v1.0.2 released

    On an unrelated note to the post (but somewhat related to Ether's comment), is there a Pod::Weaver plugin to let me insert images more easily/conveniently? I've tried manually inserting "=begin HTML" "=end HTML", but Pod::Weaver will sometimes misplace the images to another =head1 section.

    Example: https://metacpan.org/pod/release/PERLANCAR/Progress-Any-0.18/lib/Progress/Any.pm (the images should be in the Description section). Compare with the source: ="https://github.com/perlancar/…

Subscribe to feed Responses to Comments from Ether

About blogs.perl.org

blogs.perl.org is a common blogging platform for the Perl community. Written in Perl and offering the modern features you’ve come to expect in blog platforms, the site is run by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.