rango 0.1.pre → 0.1.0

data/vendor/rspec/Rakefile

@@ -1,145 +0,0 @@
-# -*- ruby -*-
-gem 'hoe', '>=2.0.0'
-require 'hoe'
-
-$:.unshift 'lib'
-
-require 'spec/version'
-require 'spec/rake/spectask'
-require 'spec/ruby'
-require 'cucumber/rake/task'
-
-Hoe.spec 'rspec' do
-  self.version = Spec::VERSION::STRING
-  self.summary = Spec::VERSION::SUMMARY
-  self.description = "Behaviour Driven Development for Ruby."
-  self.rubyforge_name = 'rspec'
-  self.developer('RSpec Development Team', 'rspec-devel@rubyforge.org')
-  self.extra_dev_deps << ["cucumber",">=0.3"] << ["bmabey-fakefs",">=0.1.1"] << ["syntax",">=1.0"] << ["diff-lcs",">=1.1.2"]
-  self.extra_dev_deps << ["heckle",">=1.4.3"] unless Spec::Ruby.version >= "1.9"
-  self.remote_rdoc_dir = "rspec/#{Spec::VERSION::STRING}"
-  self.rspec_options = ['--options', 'spec/spec.opts']
-  self.history_file = 'History.rdoc'
-  self.readme_file  = 'README.rdoc'
-  self.post_install_message = <<-POST_INSTALL_MESSAGE
-#{'*'*50}
-
-  Thank you for installing rspec-#{Spec::VERSION::STRING}
-
-  Please be sure to read History.rdoc and Upgrade.rdoc
-  for useful information about this release.
-
-#{'*'*50}
-POST_INSTALL_MESSAGE
-end
-
-['audit','test','test_deps','default','post_blog'].each do |task|
-  Rake.application.instance_variable_get('@tasks').delete(task)
-end
-
-task :post_blog do
-  # no-op
-end
-
-# Some of the tasks are in separate files since they are also part of the website documentation
-load 'resources/rake/examples.rake'
-load 'resources/rake/examples_with_rcov.rake'
-load 'resources/rake/failing_examples_with_html.rake'
-load 'resources/rake/verify_rcov.rake'
-
-task :cleanup_rcov_files do
-  rm_rf 'coverage.data'
-end
-
-
-if RUBY_VERSION =~ /^1.8/
-  task :default => [:cleanup_rcov_files, :features, :verify_rcov]
-else
-  task :default => [:spec, :features]
-end
-
-namespace :spec do
-
-  desc "Run all specs with rcov"
-  Spec::Rake::SpecTask.new(:rcov) do |t|
-    t.spec_files = FileList['spec/**/*_spec.rb']
-    t.spec_opts = ['--options', 'spec/spec.opts']
-    t.rcov = true
-    t.rcov_dir = 'coverage'
-    t.rcov_opts = ['--exclude', "features,kernel,load-diff-lcs\.rb,instance_exec\.rb,lib/spec.rb,lib/spec/runner.rb,^spec/*,bin/spec,examples,/gems,/Library/Ruby,\.autotest,#{ENV['GEM_HOME']}"]
-    t.rcov_opts << '--sort coverage --text-summary --aggregate coverage.data'
-  end
-  
-  desc "Run files listed in spec/spec_files.txt"
-  Spec::Rake::SpecTask.new(:focus) do |t|
-    if File.exists?('spec/spec_files.txt')
-      t.spec_files = File.readlines('spec/spec_files.txt').collect{|f| f.chomp}
-    end
-  end
-end
-
-desc "Run Cucumber features"
-if RUBY_VERSION =~ /^1.8/
-  Cucumber::Rake::Task.new :features do |t|
-    t.rcov = true
-    t.rcov_opts = ['--exclude', "features,kernel,load-diff-lcs\.rb,instance_exec\.rb,lib/spec.rb,lib/spec/runner.rb,^spec/*,bin/spec,examples,/gems,/Library/Ruby,\.autotest,#{ENV['GEM_HOME']}"]
-    t.rcov_opts << '--no-html --aggregate coverage.data'
-    t.cucumber_opts = %w{--format progress}
-  end
-else
-  task :features do
-    sh 'cucumber --profile no_heckle'
-  end
-end
-
-desc "Run failing examples (see failure output)"
-Spec::Rake::SpecTask.new('failing_examples') do |t|
-  t.spec_files = FileList['failing_examples/**/*_spec.rb']
-  t.spec_opts = ['--options', 'spec/spec.opts']
-end
-
-def egrep(pattern)
-  Dir['**/*.rb'].each do |fn|
-    count = 0
-    open(fn) do |f|
-      while line = f.gets
-        count += 1
-        if line =~ pattern
-          puts "#{fn}:#{count}:#{line}"
-        end
-      end
-    end
-  end
-end
-
-desc "Look for TODO and FIXME tags in the code"
-task :todo do
-  egrep /(FIXME|TODO|TBD)/
-end
-
-desc "verify_committed, verify_rcov, post_news, release"
-task :complete_release => [:verify_committed, :verify_rcov, :post_news, :release]
-
-desc "Verifies that there is no uncommitted code"
-task :verify_committed do
-  IO.popen('git status') do |io|
-    io.each_line do |line|
-      raise "\n!!! Do a git commit first !!!\n\n" if line =~ /^#\s*modified:/
-    end
-  end
-end
-
-namespace :update do
-  desc "update the manifest"
-  task :manifest do
-    system %q[touch Manifest.txt; rake check_manifest | grep -v "(in " | patch]
-  end
-end
-
-task :clobber => :clobber_tmp
-
-task :clobber_tmp do
-  cmd = %q[rm -r tmp]
-  puts cmd
-  system cmd if test ?d, 'tmp'
-end

data/vendor/rspec/Ruby1.9.rdoc

@@ -1,31 +0,0 @@
-= RSpec and Ruby 1.9
-
-RSpec runs on Ruby 1.9.1 with the following caveats.
-
-== Test::Unit
-
-RSpec/Test::Unit interop will run with the test-unit-1.2.3 gem, but you must install it.
-
-== Class Variables
-
-Due to changes in scoping rules, class variables within example groups are not
-supported in Ruby 1.9.
-
-    describe "a class variable" do
-      @@class_variable = "a class variable"
-  
-      it "can access class variables in examples in Ruby 1.8" do
-        with_ruby 1.8 do
-          @@class_variable.should == "a class variable"
-        end
-      end
-  
-      it "can NOT access class variables in examples in Ruby 1.9" do
-        with_ruby 1.9 do
-          lambda do
-            @@class_variable.should == "a class variable"
-          end.should raise_error(NameError)
-        end
-      end
-    end
-

data/vendor/rspec/TODO.txt

@@ -1,17 +0,0 @@
-== Refactoring
-
-** global predictate matchers should be stored in run_options
-* eliminate dependency on global options and configuration
-** the only place they should exist is in the Runner, which should manage them
-
-== Future
-
-* do SOMETHING with the website
-* separate the underlying framework from the DSL
-  * be able to do everything with classes and methods
-* tweak raise_error rdoc to show only one arg
-
-== rspec-2.0
-
-* rename top level namespace to Rspec and commands to 'rspec' and 'autorspec'
-  * continue to support Spec 'spec' and 'autospec' as aliases for a reasonable time

data/vendor/rspec/Upgrade.rdoc

@@ -1,199 +0,0 @@
-= Upgrade to rspec-1.2.9
-
-== What's new
-
-=== spec/spec.opts
-
-If you have a spec/spec.opts file, the spec command will now use that
-automatically as long as you don't include any options on the command line.
-
-=== let()
-
-Writing specs tends to follow a regular pattern of using local variables, discovering duplication, and then having to convert to local variables to instance variables by adding an "@" symbol. The let() method assigns the result of a lazy eval'd block as the return value of an instance method using
-the same name. This way you can go from this:
-
-    describe Subscription do
-      it "does something" do
-        subscription = Subscription.create :limit => 1
-        subscription...
-      end
-
-      it "does something else" do
-        subscription = Subscription.create :limit => 1
-        subscription...
-      end
-    end
-
-to this:
-
-    describe Subscription do
-      let(:subscription) { Subscription.create :limit => 1 }
-
-      it "does something" do
-        subscription...
-      end
-
-      it "does something else" do
-        subscription...
-      end
-    end
-
-=== its()
-
-If you're in the habit of writing one-liners using implicit subject, this new
-its() feature is for you. Here's the basic idea:
-
-    describe Array do
-      its(:length) { should == 0 }
-    end
-
-= Upgrade to rspec-1.2.3-1.2.7
-
-== What's Changed
-
-=== Matcher DSL
-
-Use Spec::Matchers.define instead of Spec::Matchers.create (which is now
-deprecated).
-
-=== Explicit Predicate Matchers are deprecated
-
-With the addition of the new Matcher DSL the old, confusing, and
-almost-nobody-uses-it explicit predicate matcher functionality's days are now
-numbered.
-
-If you're not familiar with this feature, don't worry about it. If you have anything
-that looks like this:
-
-    predicate_matchers[:swim] = :can_swim?
-
-Or this
-
-    config.predicate_matchers[:swim] = :can_swim?
-
-Change it to this:
-
-    Spec::Matchers.define :swim do
-      match do |potential_swimmer|
-        potential_swimmer.can_swim?
-      end
-    end
-
-== Custom Formatters
-
-If you have an custom formatter, the <tt>add_example_group</tt> method has
-been changed to <tt>example_group_started</tt>, and kept as an alias so your
-formatters will still work. Though not yet, <tt>add_example_group</tt> will be
-deprecated in a future minor release, and removed in a future major release,
-so we recommend you make this change now.
-
-= Upgrade to rspec-1.2.2
-
-== What's Changed
-
-=== <tt>require 'rubygems' unless ENV['NO_RUBYGEMS']</tt>
-
-After minor public outcry and confusion, we restored necessary references to
-rubygems in rspec. If you use a different mechanism for managing gems, just
-set a <tt>NO_RUBYGEMS</tt> environment variable (to any non-nil value).
-
-=== Proxies and locations
-
-This is probably only interesting to you if you use custom formatters.
-
-Formatters now receive Spec::Example::ExampleGroupProxy and
-Spec::Example::ExampleGroup objects with cohesive APIs for reporting. See the
-RDoc for those classes and Spec::Runner::Formatter::BaseFormatter for more
-information.
-
-== What's new
-
-=== The new matcher DSL works with test/unit (without the rest of rspec)
-
-We'll be separating this out to its own gem for rspec 2.0, but for now, just install
-rspec >= 1.2.1 and add the following to your <tt>test_helper</tt> file:
-
-    require 'spec/expectations'
-    class Test::Unit::TestCase
-      include Spec::Matchers
-    end
-
-This will add <tt>should()</tt> and <tt>should_not()</tt> to your objects, make all of
-rspec's built-in matchers available to your tests, INCLUDING rspec's DSL for
-creating matchers (see below, under Upgrade to rspec-1.2.0)
-
-=== debugger
-
-If you have ruby-debug installed, you can set a breakpoint by adding <tt>debugger()</tt>
-in your code:
-
-    # some code .....
-    debugger
-    # some more code ....
-
-... and using the <tt>--debugger</tt> or <tt>-u</tt> command line option.
-
-    spec path/to/file.rb --debugger
-
-= Upgrade to rspec-1.2.0
-
-== What's Changed
-
-=== WARNINGS
-
-* If you use the ruby command to run specs instead of the spec command, you'll
-  need to require 'spec/autorun' or they won't run. This won't affect you if
-  you use the spec command or the Spec::Rake::SpecTask that ships with RSpec.
-
-* require 'spec/test/unit' to invoke test/unit interop if you're using
-  RSpec's core (this is handled implicitly with spec-rails)
-
-* setup and teardown are gone - use before and after instead
-
-  * you can still use setup and teardown if you're using
-    Test::Unit::TestCase as the base ExampleGroup class (which is implicit
-    in rspec-rails)
-
-* The matcher protocol has been improved. The old protocol is still supported,
-  but we added support for two new methods that speak a bit more clearly:
-
-    failure_message          => failure_message_for_should
-    negative_failure_message => failure_message_for_should_not
-
-* All references to rubygems have been removed from within rspec's code.
-
-  * See http://gist.github.com/54177 for rationale and suggestions on
-    alternative approaches to loading rubygems
-
-== What's New
-
-=== Ruby 1.9
-
-RSpec now works with Ruby 1.9.1. See http://wiki.github.com/dchelimsky/rspec/ruby-191
-for useful information.
-
-=== Improved heckle integration
-
-RSpec works with heckle again! Gotta use heckle >= 1.4.2 for this to work
-though, and it only works with ruby-1.8.6 and 1.8.7 (heckle doesn't support
-1.9.1 yet).
-
-    [sudo] gem install heckle --version ">=1.4.2"
-    spec spec/game/mastermind.rb --heckle Game::Mastermind
-
-=== New Matcher DSL
-
-We've added a new DSL for generating custom matchers very simply and cleanly.
-We'll still support the simple_matcher method, so never fear if you're using
-that, but we recommend that you start developing your new matchers with this
-new syntax.
-
-    Spec::Matchers.create :be_a_multiple_of do |smaller|
-      match do |bigger|
-        bigger % smaller == 0
-      end
-    end
-
-    9.should be_a_multiple_of(3)
-
-See <tt>features/matchers/define_matcher.feature</tt> for more examples

data/vendor/rspec/bin/autospec

@@ -1,4 +0,0 @@
-#!/usr/bin/env ruby
-ENV['RSPEC'] = 'true'     # allows autotest to discover rspec
-ENV['AUTOTEST'] = 'true'  # allows autotest to run w/ color on linux
-system (RUBY_PLATFORM =~ /mswin|mingw/ ? 'autotest.bat' : 'autotest'), *ARGV

data/vendor/rspec/bin/spec

@@ -1,5 +0,0 @@
-#!/usr/bin/env ruby
-rspec_dir = File.expand_path(File.join(File.dirname(__FILE__), '..', 'lib'))
-$LOAD_PATH.unshift(rspec_dir) unless $LOAD_PATH.include?(rspec_dir)
-require 'spec/autorun'
-exit ::Spec::Runner::CommandLine.run

data/vendor/rspec/cucumber.yml

@@ -1,5 +0,0 @@
-default: --require features features -t ~@wip
-pending: --require features features-pending
-no_heckle: --require features features --exclude heckle
-focus: --require features features -t focus
-wip: --require features features -t @wip

data/vendor/rspec/examples/failing/README.txt

@@ -1,11 +0,0 @@
-"Why have failing examples?", you might ask.
-
-They allow us to see failure messages. RSpec wants to provide meaningful and
-helpful failure messages. The failures in this directory not only provide you
-a way of seeing the failure messages, but they provide RSpec's own specs a way
-of describing what they should look like and ensuring they stay correct.
-
-To see the types of messages you can expect, stand in the root directory and
-run:
-
-bin/spec examples/failing/*.rb

data/vendor/rspec/examples/failing/diffing_spec.rb

@@ -1,36 +0,0 @@
-describe "Running specs with --diff" do
-  it "should print diff of different strings" do
-    uk = <<-EOF
-RSpec is a
-behaviour driven development
-framework for Ruby
-EOF
-    usa = <<-EOF
-RSpec is a
-behavior driven development
-framework for Ruby
-EOF
-    usa.should == uk
-  end
-
-  class Animal
-    def initialize(name,species)
-      @name,@species = name,species
-    end
-
-    def inspect
-      <<-EOA
-<Animal
-name=#{@name},
-species=#{@species}
->
-      EOA
-    end
-  end
-
-  it "should print diff of different objects' pretty representation" do
-    expected = Animal.new "bob", "giraffe"
-    actual   = Animal.new "bob", "tortoise"
-    expected.should eql(actual)
-  end
-end