From mhennemeyer at googlemail.com  Tue Dec  2 04:25:11 2008
From: mhennemeyer at googlemail.com (Matthias Hennemeyer)
Date: Tue, 2 Dec 2008 10:25:11 +0100
Subject: [rspec-devel] Where to start?
Message-ID: <BD3A7877-0946-4B0B-8BA6-00F337B49B63@googlemail.com>

Hi,
i want to restart rspec development.
Is there actually any particularly important area?
Is eg performance still an issue?
Would you point me somewhere?
Thanks
Matthias

From dchelimsky at gmail.com  Tue Dec  2 09:49:39 2008
From: dchelimsky at gmail.com (David Chelimsky)
Date: Tue, 2 Dec 2008 08:49:39 -0600
Subject: [rspec-devel] Where to start?
In-Reply-To: <BD3A7877-0946-4B0B-8BA6-00F337B49B63@googlemail.com>
References: <BD3A7877-0946-4B0B-8BA6-00F337B49B63@googlemail.com>
Message-ID: <57c63afe0812020649q19a91910l46ddd252316c7fbf@mail.gmail.com>

On Tue, Dec 2, 2008 at 3:25 AM, Matthias Hennemeyer
<mhennemeyer at googlemail.com> wrote:
> Hi,
> i want to restart rspec development.
> Is there actually any particularly important area?
> Is eg performance still an issue?
> Would you point me somewhere?

Hey Matthias,

Thanks in advance.

Performance and Ruby 1.9 compatibility are two key things I want to
focus on in the coming weeks/months.

One problem we have with 1.9 is the new scoping rules that make it so that this:

module Foo
  module Bar
    class Baz
    end
  end
end

module Foo
  module Bar
    describe "something" do
      it "does something" do
        baz = Baz.new
      end
    end
  end
end

blows up on Baz.new. You have to say Foo::Bar::Baz.new to get it to
work. I'd really like to figure out a way to discover the module scope
in which #describe is declared and include that module within the
ExampleGroup.

There are others as well.

And there are 240+ open tickets at
http://rspec.lighthouseapp.com/projects/5645, so feel free to find any
that interest you and patch away.

Cheers,
David

> Thanks
> Matthias
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
>

From mhennemeyer at googlemail.com  Thu Dec  4 10:44:52 2008
From: mhennemeyer at googlemail.com (Matthias Hennemeyer)
Date: Thu, 4 Dec 2008 16:44:52 +0100
Subject: [rspec-devel] Where to start?
In-Reply-To: <57c63afe0812020649q19a91910l46ddd252316c7fbf@mail.gmail.com>
References: <BD3A7877-0946-4B0B-8BA6-00F337B49B63@googlemail.com>
	<57c63afe0812020649q19a91910l46ddd252316c7fbf@mail.gmail.com>
Message-ID: <34840F1B-3682-4CC4-BCB5-7C2DB6E39357@googlemail.com>

I've created a ticket:
http://rspec.lighthouseapp.com/projects/5645/tickets/625-describe-with-ruby-19-should-include-an-enclosing-module-into-the-blocks-scope




Am 02.12.2008 um 15:49 schrieb David Chelimsky:

> On Tue, Dec 2, 2008 at 3:25 AM, Matthias Hennemeyer
> <mhennemeyer at googlemail.com> wrote:
>> Hi,
>> i want to restart rspec development.
>> Is there actually any particularly important area?
>> Is eg performance still an issue?
>> Would you point me somewhere?
>
> Hey Matthias,
>
> Thanks in advance.
>
> Performance and Ruby 1.9 compatibility are two key things I want to
> focus on in the coming weeks/months.
>
> One problem we have with 1.9 is the new scoping rules that make it  
> so that this:
>
> module Foo
>  module Bar
>    class Baz
>    end
>  end
> end
>
> module Foo
>  module Bar
>    describe "something" do
>      it "does something" do
>        baz = Baz.new
>      end
>    end
>  end
> end
>
> blows up on Baz.new. You have to say Foo::Bar::Baz.new to get it to
> work. I'd really like to figure out a way to discover the module scope
> in which #describe is declared and include that module within the
> ExampleGroup.
>
> There are others as well.
>
> And there are 240+ open tickets at
> http://rspec.lighthouseapp.com/projects/5645, so feel free to find any
> that interest you and patch away.
>
> Cheers,
> David
>
>> Thanks
>> Matthias
>> _______________________________________________
>> rspec-devel mailing list
>> rspec-devel at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-devel
>>
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel


From mhennemeyer at googlemail.com  Thu Dec  4 10:50:08 2008
From: mhennemeyer at googlemail.com (Matthias Hennemeyer)
Date: Thu, 4 Dec 2008 16:50:08 +0100
Subject: [rspec-devel] Where to start?
In-Reply-To: <57c63afe0812020649q19a91910l46ddd252316c7fbf@mail.gmail.com>
References: <BD3A7877-0946-4B0B-8BA6-00F337B49B63@googlemail.com>
	<57c63afe0812020649q19a91910l46ddd252316c7fbf@mail.gmail.com>
Message-ID: <B5173983-4AEB-4EE6-8C6C-3525AAD1DC30@googlemail.com>

Ahh!
Lighthouse: How can I delete a ticket that i have created accidentally  
by hitting enter while editing?





From dchelimsky at gmail.com  Thu Dec  4 10:51:56 2008
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 4 Dec 2008 09:51:56 -0600
Subject: [rspec-devel] Where to start?
In-Reply-To: <B5173983-4AEB-4EE6-8C6C-3525AAD1DC30@googlemail.com>
References: <BD3A7877-0946-4B0B-8BA6-00F337B49B63@googlemail.com>
	<57c63afe0812020649q19a91910l46ddd252316c7fbf@mail.gmail.com>
	<B5173983-4AEB-4EE6-8C6C-3525AAD1DC30@googlemail.com>
Message-ID: <57c63afe0812040751u4edc3f1due2670a89efa45255@mail.gmail.com>

On Thu, Dec 4, 2008 at 9:50 AM, Matthias Hennemeyer
<mhennemeyer at googlemail.com> wrote:
> Ahh!
> Lighthouse: How can I delete a ticket that i have created accidentally by
> hitting enter while editing?

You can't, but I will :)

From aslak.hellesoy at gmail.com  Sun Dec  7 12:18:48 2008
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Sun, 7 Dec 2008 18:18:48 +0100
Subject: [rspec-devel] Tagging cucumber issues with cucumber?
Message-ID: <8d961d900812070918x33d3bbd1td237458a779af94a@mail.gmail.com>

Someone is tagging the cucumber tickets in Lighthouse with the 'cucumber'
tag. Why? They are already in the cucumber project.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-devel/attachments/20081207/fb0271c0/attachment.html>

From aslak.hellesoy at gmail.com  Sun Dec  7 12:34:59 2008
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Sun, 7 Dec 2008 18:34:59 +0100
Subject: [rspec-devel] Tagging cucumber issues with cucumber?
In-Reply-To: <8d961d900812070918x33d3bbd1td237458a779af94a@mail.gmail.com>
References: <8d961d900812070918x33d3bbd1td237458a779af94a@mail.gmail.com>
Message-ID: <8d961d900812070934q1885e10by386992c0eeff7acc@mail.gmail.com>

On Sun, Dec 7, 2008 at 6:18 PM, aslak hellesoy <aslak.hellesoy at gmail.com>wrote:

> Someone is tagging the cucumber tickets in Lighthouse with the 'cucumber'
> tag. Why? They are already in the cucumber project.
>

I just removed the cucumber tags for all tickets in the cucumber project
(thanks to a lighthouse-api one-liner).

Aslak
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-devel/attachments/20081207/1fecf256/attachment.html>

From dchelimsky at gmail.com  Sun Dec  7 12:52:26 2008
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 7 Dec 2008 11:52:26 -0600
Subject: [rspec-devel] Tagging cucumber issues with cucumber?
In-Reply-To: <8d961d900812070934q1885e10by386992c0eeff7acc@mail.gmail.com>
References: <8d961d900812070918x33d3bbd1td237458a779af94a@mail.gmail.com>
	<8d961d900812070934q1885e10by386992c0eeff7acc@mail.gmail.com>
Message-ID: <57c63afe0812070952n59a96915m1c7402df3457f077@mail.gmail.com>

On Sun, Dec 7, 2008 at 11:34 AM, aslak hellesoy
<aslak.hellesoy at gmail.com> wrote:
>
>
> On Sun, Dec 7, 2008 at 6:18 PM, aslak hellesoy <aslak.hellesoy at gmail.com>
> wrote:
>>
>> Someone is tagging the cucumber tickets in Lighthouse with the 'cucumber'
>> tag. Why? They are already in the cucumber project.
>
> I just removed the cucumber tags for all tickets in the cucumber project
> (thanks to a lighthouse-api one-liner).

Funny. It may have been easy for you, but the result is the tickets
changing with messages saying "no changes were found." Close, but not
quite there :)

>
> Aslak
>
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
>

From ben at benmabey.com  Sun Dec  7 12:53:57 2008
From: ben at benmabey.com (Ben Mabey)
Date: Sun, 07 Dec 2008 10:53:57 -0700
Subject: [rspec-devel] Tagging cucumber issues with cucumber?
In-Reply-To: <8d961d900812070918x33d3bbd1td237458a779af94a@mail.gmail.com>
References: <8d961d900812070918x33d3bbd1td237458a779af94a@mail.gmail.com>
Message-ID: <493C0DB5.6060403@benmabey.com>

aslak hellesoy wrote:
> Someone is tagging the cucumber tickets in Lighthouse with the 
> 'cucumber' tag. Why? They are already in the cucumber project.

Sorry, I tagged the latest batch I entered with "cucumber".  I saw it as 
an option and I figured someone wanted to to be tagged with that for a 
reason.
-Ben

From aslak.hellesoy at gmail.com  Sun Dec  7 13:10:14 2008
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Sun, 7 Dec 2008 19:10:14 +0100
Subject: [rspec-devel] Tagging cucumber issues with cucumber?
In-Reply-To: <57c63afe0812070952n59a96915m1c7402df3457f077@mail.gmail.com>
References: <8d961d900812070918x33d3bbd1td237458a779af94a@mail.gmail.com>
	<8d961d900812070934q1885e10by386992c0eeff7acc@mail.gmail.com>
	<57c63afe0812070952n59a96915m1c7402df3457f077@mail.gmail.com>
Message-ID: <8d961d900812071010v7b89b6hdc1bcc2c909f49ae@mail.gmail.com>

On Sun, Dec 7, 2008 at 6:52 PM, David Chelimsky <dchelimsky at gmail.com>wrote:

> On Sun, Dec 7, 2008 at 11:34 AM, aslak hellesoy
> <aslak.hellesoy at gmail.com> wrote:
> >
> >
> > On Sun, Dec 7, 2008 at 6:18 PM, aslak hellesoy <aslak.hellesoy at gmail.com
> >
> > wrote:
> >>
> >> Someone is tagging the cucumber tickets in Lighthouse with the
> 'cucumber'
> >> tag. Why? They are already in the cucumber project.
> >
> > I just removed the cucumber tags for all tickets in the cucumber project
> > (thanks to a lighthouse-api one-liner).
>
> Funny. It may have been easy for you, but the result is the tickets
> changing with messages saying "no changes were found." Close, but not
> quite there :)
>

At least there is nothing left tagged with cucumber:
http://rspec.lighthouseapp.com/projects/16211-cucumber/tickets?q=tagged%3A%22cucumber%22

(But there is still a big cucumber in the cloud...)

Oh well


>
> >
> > Aslak
> >
> > _______________________________________________
> > rspec-devel mailing list
> > rspec-devel at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-devel
> >
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-devel/attachments/20081207/c2803360/attachment.html>

From undees at gmail.com  Thu Dec 18 19:43:51 2008
From: undees at gmail.com (Ian Dees)
Date: Thu, 18 Dec 2008 16:43:51 -0800
Subject: [rspec-devel] RSpec gems outdated on RubyForge?
Message-ID: <ad4f9af90812181643q3ea01966jfd45ca1d06560c4d@mail.gmail.com>

Hi, all.

Has anyone had trouble updating RSpec to the latest?  On MacPorts
(latest ruby and rb-rubygems packages):

$ sudo gem update rspec
Updating installed gems
Updating rspec
Successfully installed rspec-1.1.4
Gems updated: rspec

Aren't we up to 1.1.11?  Has anyone else had this problem?

Thanks in advance for any advice.

Sincerely,

Ian

From luislavena at gmail.com  Thu Dec 18 21:39:45 2008
From: luislavena at gmail.com (Luis Lavena)
Date: Fri, 19 Dec 2008 00:39:45 -0200
Subject: [rspec-devel] RSpec gems outdated on RubyForge?
In-Reply-To: <ad4f9af90812181643q3ea01966jfd45ca1d06560c4d@mail.gmail.com>
References: <ad4f9af90812181643q3ea01966jfd45ca1d06560c4d@mail.gmail.com>
Message-ID: <71166b3b0812181839v32e687a3t873bc3a21359f021@mail.gmail.com>

On Thu, Dec 18, 2008 at 10:43 PM, Ian Dees <undees at gmail.com> wrote:
> Hi, all.
>
> Has anyone had trouble updating RSpec to the latest?  On MacPorts
> (latest ruby and rb-rubygems packages):
>
> $ sudo gem update rspec
> Updating installed gems
> Updating rspec
> Successfully installed rspec-1.1.4
> Gems updated: rspec
>
> Aren't we up to 1.1.11?  Has anyone else had this problem?
>
> Thanks in advance for any advice.
>

Looks like latest release pushed to rubyforge is 1.1.10:

http://rubyforge.org/projects/rspec/

-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From undees at gmail.com  Thu Dec 18 21:50:09 2008
From: undees at gmail.com (Ian Dees)
Date: Thu, 18 Dec 2008 18:50:09 -0800
Subject: [rspec-devel] RSpec gems outdated on RubyForge?
In-Reply-To: <ad4f9af90812181643q3ea01966jfd45ca1d06560c4d@mail.gmail.com>
References: <ad4f9af90812181643q3ea01966jfd45ca1d06560c4d@mail.gmail.com>
Message-ID: <ad4f9af90812181850g28f481dbv829e58afcff703d@mail.gmail.com>

Blurg.  RubyGems was somehow finding an old copy of the 1.1.4 gem file
buried in a directory somewhere (even when run with "-v '= 1.1.11'");
when I deleted that, I could finally get 1.1.11.

On Thu, Dec 18, 2008 at 4:43 PM, Ian Dees <undees at gmail.com> wrote:
> Hi, all.
>
> Has anyone had trouble updating RSpec to the latest?  On MacPorts
> (latest ruby and rb-rubygems packages):
>
> $ sudo gem update rspec
> Updating installed gems
> Updating rspec
> Successfully installed rspec-1.1.4
> Gems updated: rspec
>
> Aren't we up to 1.1.11?  Has anyone else had this problem?
>
> Thanks in advance for any advice.
>
> Sincerely,
>
> Ian
>

From dchelimsky at gmail.com  Thu Dec 18 21:51:41 2008
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 18 Dec 2008 20:51:41 -0600
Subject: [rspec-devel] RSpec gems outdated on RubyForge?
In-Reply-To: <71166b3b0812181839v32e687a3t873bc3a21359f021@mail.gmail.com>
References: <ad4f9af90812181643q3ea01966jfd45ca1d06560c4d@mail.gmail.com>
	<71166b3b0812181839v32e687a3t873bc3a21359f021@mail.gmail.com>
Message-ID: <57c63afe0812181851y153a6dbg1f573fc929bfc950@mail.gmail.com>

On Thu, Dec 18, 2008 at 8:39 PM, Luis Lavena <luislavena at gmail.com> wrote:
> On Thu, Dec 18, 2008 at 10:43 PM, Ian Dees <undees at gmail.com> wrote:
>> Hi, all.
>>
>> Has anyone had trouble updating RSpec to the latest?  On MacPorts
>> (latest ruby and rb-rubygems packages):
>>
>> $ sudo gem update rspec
>> Updating installed gems
>> Updating rspec
>> Successfully installed rspec-1.1.4
>> Gems updated: rspec
>>
>> Aren't we up to 1.1.11?  Has anyone else had this problem?
>>
>> Thanks in advance for any advice.
>>
>
> Looks like latest release pushed to rubyforge is 1.1.10:
>
> http://rubyforge.org/projects/rspec/

That is incorrect. Click through to the download page and you'll see
1.1.11 as well, but for some reason 1.1.10 is listed as more recent.

I'll be releasing 1.2 sometime in the next few weeks. In the mean
time, I guess you have to explicitly ask for 1.1.11 when you install
it :(

>
> --
> Luis Lavena
> AREA 17
> -
> Perfection in design is achieved not when there is nothing more to add,
> but rather when there is nothing more to take away.
> Antoine de Saint-Exup?ry
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel

From dchelimsky at gmail.com  Wed Dec 31 17:44:11 2008
From: dchelimsky at gmail.com (David Chelimsky)
Date: Wed, 31 Dec 2008 16:44:11 -0600
Subject: [rspec-devel] Ruby 1.9 and constant lookup rules
Message-ID: <57c63afe0812311444k65203703tacad8a5c11504dbd@mail.gmail.com>

Hey all,

I've been working on getting rspec to run with Ruby 1.9. One
significant problem is that 1.9 changes constant lookup rules, so:

module Foo
  module Bar
    describe Thing do

      class Something; end
      def helper_method; end

      it "does not automatically get access to the context of Foo::Bar"
      it "does not automatically get access to Something"
      it "does not automatically get access to helper_method"

    end
  end
end

Matthias Hennemeyer offered up a patch to resolve this:

  http://rspec.lighthouseapp.com/attachments/68441/0001-Main-describe-with-Ruby-1.9-should-include-an-encl.patch

I've merged this into the master branch and cleaned things up a bit,
but it only supports top-level calls to #describe. I've been working
on a solution to extract the code in Matthias' patch so that it is
accessible from the top level and nested describe calls, but as I'm
doing this, I grow concerned w/ performance impacts. For this to work,
for every level of nesting there needs to be another call to
instance_eval (at least that's how it works in the current solution).

Anybody have any thoughts about this? Or perhaps a different solution
(like having method_missing delegate to the group)?

David