pry-rescue 1.1.1 → 1.2.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 60a747dabc7b9f689e6e152f6dc96375ba765301
+  data.tar.gz: 8580701fafd6da9467f07d6de7e9c8f31cce95b1
+SHA512:
+  metadata.gz: 049f1c260a868d3beb71810d508b2625d6c98e6de8e0302e93de84b478c1c8a32fbb1e04c2670a167f91d086f0c44d5dccb5066f089a092bdd9517f5c9fc950d
+  data.tar.gz: 1fc6745f1fd1c7c39ec18fb7521d1cf3c800e6bfb43a936620ae90c723492c64436387f7739d8d9e45af53c664b6b7e6821a91d9ab5cd09c0eaa261ad6b797ab

data/.travis.yml

@@ -0,0 +1,5 @@
+language: ruby
+rvm:
+  - 1.9.3
+  - 2.0.0
+  - rbx-19mode

data/Gemfile

@@ -1,2 +1,2 @@
-source :rubygems
+source 'https://rubygems.org'
 gemspec

data/README.md

@@ -1,11 +1,14 @@
-**pry-rescue** - super-fast debugging for ruby. (See [Pry to the
-rescue!](http://cirw.in/blog/pry-to-the-rescue))
+# pry-rescue
 
-Introduction
-============
+Super-fast debugging for Ruby. (See [Pry to the rescue!](http://cirw.in/blog/pry-to-the-rescue))
+<a href="https://travis-ci.org/ConradIrwin/pry-rescue">
+<img src="https://secure.travis-ci.org/ConradIrwin/pry-rescue.png?branch=master" alt="Build status">
+</a>
+
+## Introduction
 
 pry-rescue is an implementation of "break on unhandled exception" for Ruby. Whenever an
-exception is raised, but not rescued, pry-rescue will automatically open pry for you:
+exception is raised, but not rescued, pry-rescue will automatically open Pry for you:
 
 ```ruby
 $ rescue examples/example2.rb
@@ -21,10 +24,9 @@ from /home/conrad/0/ruby/pry-rescue/examples/example2.rb:22:in `gamma`
 [1] pry(main)>
 ```
 
-Installation
-============
+## Installation
 
-You can install `pry-rescue` with rubygems as normal, and I strongly recommend you also
+You can install `pry-rescue` with RubyGems as normal, and I strongly recommend you also
 install `pry-stack_explorer`. See [Known bugs](#known-bugs) for places that won't work.
 
 ```
@@ -40,20 +42,18 @@ group :development do
 end
 ```
 
-Usage
-=====
+## Usage
 
-For simple ruby scripts, just run them with the `rescue` executable instead of the `ruby`
+For simple Ruby scripts, just run them with the `rescue` executable instead of the `ruby`
 executable.
 
 ```
 rescue <script.rb> [arguments..]
 ```
 
-Rails
------
+### Rails
 
-For rails, use `rescue rails` in place of `rails`, for example:
+For Rails, use `rescue rails` in place of `rails`, for example:
 
 ```
 rescue rails server
@@ -65,20 +65,19 @@ If you're using `bundle exec` the rescue should go after the exec:
 bundle exec rescue rails server
 ```
 
-Then whenever an unhandled exception happens inside rails, a pry console will open on
-stdout. This is the same terminal that you see the rails logs on, so if you're
+Then whenever an unhandled exception happens inside Rails, a Pry console will open on
+stdout. This is the same terminal that you see the Rails logs on, so if you're
 using something like [pow](https://pow.cx) then you will run into difficulties.
 
 You might also be interested in
 [better_errors](https://github.com/charliesome/better_errors) which opens consoles in your
 browser on unhandled exceptions, and [pry-rails](https://github.com/rweng/pry-rails) which
-adds some rails specific helpers to pry, and replaces `rails console` by pry.
+adds some Rails specific helpers to Pry, and replaces `rails console` by Pry.
 
-Rspec
------
+### RSpec
 
 If you're using [RSpec](https://rspec.org) or
-[respec](https://github.com/oggy/respec), you can open a pry session on
+[respec](https://github.com/oggy/respec), you can open a Pry session on
 every test failure using `rescue rspec` or `rescue respec`:
 
 ```ruby
@@ -101,8 +100,7 @@ Unfortunately using `edit -c` to edit `_spec.rb` files does not yet reload the
 code in a way that the `try-again` command can understand. You can still use
 `try-again` if you edit code that is not in spec files.
 
-Minitest
---------
+### Minitest
 
 Add the following to your `test_helper.rb` or to the top of your test file.
 
@@ -114,8 +112,7 @@ require 'pry-rescue/minitest'
 Then, when you have a failure, you can use `edit`, `edit -c`, and `edit-method`, then
 `try-again` to re-run the tests.
 
-Rack
-----
+### Rack
 
 If you're using Rack, you should use the middleware instead (though be careful to only
 include it in development!):
@@ -124,15 +121,13 @@ include it in development!):
 use PryRescue::Rack if ENV["RACK_ENV"] == 'development'
 ```
 
-Pry commands
-============
+## Pry commands
 
-`pry-rescue` adds two commands to pry. `cd-cause` and `try-again`. In combination with
+`pry-rescue` adds two commands to Pry. `cd-cause` and `try-again`. In combination with
 `edit --method` these can let you fix the problem with your code and verify that the fix
 worked without restarting your program.
 
-cd-cause
---------
+### cd-cause
 
 If you've run some code in Pry, and an exception was raised, you can use the `cd-cause`
 command:
@@ -173,11 +168,10 @@ from examples/example.rb:5:in `test`
 
 To get back from `cd-cause` you can either type `<ctrl+d>` or `cd ..`.
 
-try-again
----------
+### try-again
 
 Once you've used Pry's `edit` or command to fix your code, you can issue a `try-again`
-command to re-run your code. For rails and rack, this re-runs the request, for minitest
+command to re-run your code. For Rails and rack, this re-runs the request, for minitest
 and rspec, it re-runs the current test, for more advanced users this re-runs the
 `Pry::rescue{ }` block.
 
@@ -195,11 +189,9 @@ From: examples/example.rb @ line 4 Object#test:
 foo
 ```
 
-Advanced usage
-==============
+## Advanced usage
 
-Block form
-----------
+### Block form
 
 If you want more fine-grained control over which parts of your code are rescued, you can
 also use the block form:
@@ -233,11 +225,10 @@ from examples/example.rb:7:in `rescue in test`
 [1] pry(main)>
 ```
 
-Rescuing an exception
----------------------
+### Rescuing an exception
 
-Finally. If you're doing your own exception handling, you can ask pry to open on an exception that you've caught.
-For this to work you must be inside a Pry::rescue{ } block.
+Finally. If you're doing your own exception handling, you can ask Pry to open on an exception that you've caught.
+For this to work you must be inside a `Pry::rescue{ }` block.
 
 ```ruby
 def test
@@ -249,14 +240,14 @@ end
 Pry::rescue{ test }
 
 ```
-Peeking
-=======
+
+## Peeking
 
 Sometimes bugs in your program don't cause exceptions. Instead your program just gets
 stuck. Examples include infinite loops, slow network calls, or tests that take a
-suprisingly long time to run.
+surprisingly long time to run.
 
-In this case it's useful to be able to open a pry console when you notice that your
+In this case it's useful to be able to open a Pry console when you notice that your
 program is not going anywhere. To do this, send your process a `SIGQUIT` using `<ctrl+\>`.
 
 ```ruby
@@ -275,12 +266,10 @@ From: ./examples/loop.rb @ line 10 Object#r
 pry (main)>
 ```
 
-Advanced peeking
-----------------
+### Advanced peeking
 
 You can configure which signal pry-rescue listens for by default by exporting the
-`PRY_PEEK`
-environment variable that suits your use-case best:
+`PRY_PEEK` environment variable that suits your use-case best:
 
 ```
 export PRY_PEEK=""    # don't autopeek at all
@@ -292,7 +281,7 @@ export PRY_PEEK=EXIT  # peek on program exit
 ```
 
 If it's only important for one program, then you can also set the environment variable in
-ruby before requiring pry-rescue
+Ruby before requiring pry-rescue:
 
 ```ruby
 ENV['PRY_PEEK'] = '' # disable SIGQUIT handler
@@ -300,7 +289,7 @@ require "pry-rescue"
 ```
 
 Finally, you can enable peeking into programs that do not include pry-rescue by
-configuring ruby to always load one (or several) of these files:
+configuring Ruby to always load one (or several) of these files:
 
 ```
 export RUBYOPT=-rpry-rescue/peek/int   # peek on SIGINT (<ctrl-c>)
@@ -312,26 +301,24 @@ export RUBYOPT=-rpry-rescue/peek/exit  # peek on program exit
 
 These last examples relies on having pry-rescue in the load path (i.e. at least in the
 gemset, or Gemfile of the program). If that is not true, you can use absolute paths. The
-hook files do not require the whole of pry-rescue, nor is any of pry itself loaded until
+hook files do not require the whole of pry-rescue, nor is any of Pry itself loaded until
 you trigger the signal.
 
 ```
 export RUBYOPT=-r/home/cirwin/src/pry-rescue/lib/pry-rescue/peek/usr2
 ```
 
-Known bugs
-==========
+## Known bugs
 
-* ruby 2.0, 1.9.3, 1.9.2 – no known bugs
-* ruby 1.9.1 — not supported
-* ruby 1.8.7 — occasional incorrect values for self
-* ree 1.8.7 — no known bugs
-* jruby 1.7 (1.8 mode and 1.9 mode) — no known bugs
-* jruby 1.6 (1.8 mode and 1.9 mode) — incorrect value for self in NoMethodErrors
-* rbx (1.8 mode and 1.9 mode) – does not catch some low-level errors (e.g. ZeroDivisionError)
+* Ruby 2.0, 1.9.3, 1.9.2 – no known bugs
+* Ruby 1.9.1 — not supported
+* Ruby 1.8.7 — occasional incorrect values for self
+* REE 1.8.7 — no known bugs
+* JRuby 1.7 (1.8 mode and 1.9 mode) — no known bugs
+* JRuby 1.6 (1.8 mode and 1.9 mode) — incorrect value for self in NoMethodErrors
+* Rubinius (1.8 mode and 1.9 mode) – does not catch some low-level errors (e.g. ZeroDivisionError)
 
-Meta-fu
-=======
+## Meta-fu
 
 Released under the MIT license, see LICENSE.MIT for details. Contributions and bug-reports
 are welcome.

data/Rakefile

@@ -1,3 +1,5 @@
+require 'rspec/core/rake_task'
+
 task :default => :test
 task :spec => :test
 
@@ -17,10 +19,7 @@ task :sintax do
   sh 'bin/rescue examples/syntax-err.rb'
 end
 
-desc "Run tests"
-task :test do
-  sh 'rspec spec'
-end
+RSpec::Core::RakeTask.new(:test)
 
 task :build do
   sh 'gem build *.gemspec'

data/lib/pry-rescue/core_ext.rb

@@ -33,7 +33,7 @@ class << Pry
   #   end
   #
   def rescued(e=$!)
-    if e.instance_variable_get(:@rescue_bindings)
+    if e.instance_variable_defined?(:@rescue_bindings)
       PryRescue.enter_exception_context(e)
     else
       stack = ''
@@ -73,7 +73,7 @@ class << Pry
   def enable_rescuing!(block=nil)
     Interception.listen(block) do |exception, binding|
       bindings = binding.respond_to?(:callers) ? binding.callers : [binding]
-      unless exception.instance_variable_get(:@rescue_bindings)
+      unless exception.instance_variable_defined?(:@rescue_bindings)
         exception.instance_variable_set(:@rescue_bindings, bindings)
         exception.instance_variable_set(:@rescue_cause, $!)
       end

data/lib/pry-rescue/minitest.rb

@@ -1,24 +1,45 @@
 require 'pry-rescue'
-# TODO: it should be possible to do all this by simply wrapping
-# MiniTest::Unit::TestCase in recent versions of minitest.
-# Unfortunately the version of minitest bundled with ruby seems to
-# take precedence over the new gem, so we can't do this and still
-# support ruby-1.9.3
-class MiniTest::Unit::TestCase
-  alias_method :run_without_rescue, :run
-
-  def run(runner)
-    Pry::rescue do
-      run_without_rescue(runner)
+
+# Minitest 5 handles all unknown exceptions, so to get them out of
+# minitest, we need to add Exception to its passthrough types
+if defined? Minitest::Test
+
+  class Minitest::Test
+    alias_method :run_without_rescue, :run
+
+    def run
+      Minitest::Test::PASSTHROUGH_EXCEPTIONS << Exception
+      Pry::rescue do
+        run_without_rescue
+      end
     end
   end
-end
 
-class << MiniTest::Unit.runner; self; end.class_eval do
-  alias_method :puke_without_rescue, :puke
+else
+
+  # TODO: it should be possible to do all this by simply wrapping
+  # MiniTest::Unit::TestCase in recent versions of minitest.
+  # Unfortunately the version of minitest bundled with ruby seems to
+  # take precedence over the new gem, so we can't do this and still
+  # support ruby-1.9.3
+  
+  class MiniTest::Unit::TestCase
+    alias_method :run_without_rescue, :run
 
-  def puke(suite, test, e)
-    Pry::rescued(e)
-    puke_without_rescue(suite, test, e)
+    def run(runner)
+      Pry::rescue do
+        run_without_rescue(runner)
+      end
+    end
   end
+
+  class << MiniTest::Unit.runner; self; end.class_eval do
+    alias_method :puke_without_rescue, :puke
+
+    def puke(suite, test, e)
+      Pry::rescued(e)
+      puke_without_rescue(suite, test, e)
+    end
+  end
+
 end

data/pry-rescue.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |s|
   s.name          = 'pry-rescue'
-  s.version       = '1.1.1'
+  s.version       = '1.2.0'
   s.summary       = 'Open a pry session on any unhandled exceptions'
   s.description   = 'Allows you to wrap code in Pry::rescue{ } to open a pry session at any unhandled exceptions'
   s.homepage      = 'https://github.com/ConradIrwin/pry-rescue'
@@ -15,6 +15,7 @@ Gem::Specification.new do |s|
 
   s.add_development_dependency 'pry-stack_explorer' # upgrade to regular dep?
 
+  s.add_development_dependency 'rake'
   s.add_development_dependency 'rspec'
   s.add_development_dependency 'yard'
   s.add_development_dependency 'redcarpet'

metadata

@@ -1,8 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: pry-rescue
 version: !ruby/object:Gem::Version
-  version: 1.1.1
-  prerelease: 
+  version: 1.2.0
 platform: ruby
 authors:
 - Conrad Irwin
@@ -11,118 +10,118 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-05-10 00:00:00.000000000 Z
+date: 2013-10-28 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: pry
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: interception
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0.3'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0.3'
 - !ruby/object:Gem::Dependency
   name: pry-stack_explorer
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: rspec
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: yard
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: redcarpet
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: capybara
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
 description: Allows you to wrap code in Pry::rescue{ } to open a pry session at any
@@ -138,6 +137,7 @@ extensions: []
 extra_rdoc_files: []
 files:
 - .gitignore
+- .travis.yml
 - Gemfile
 - LICENSE.MIT
 - README.md
@@ -183,27 +183,26 @@ files:
 - spec/spec_helper.rb
 homepage: https://github.com/ConradIrwin/pry-rescue
 licenses: []
+metadata: {}
 post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.23
+rubygems_version: 2.0.3
 signing_key: 
-specification_version: 3
+specification_version: 4
 summary: Open a pry session on any unhandled exceptions
 test_files: []
 has_rdoc: