padrino start doesn't work when using 'pry'
fix reloader issue with some gems that redefine Class#name (like pry)
Signed-off-by: David A. Cuadrado <email@example.com>
Yep, we reverted back to name because some libs redefine also to_s ... so suggestions?
Propose a new fix for #807 and #808
make sure we can always use the original class name
@DAddYE Should we still merge this or is the commit you put in fix it as well?
this issue is critic... you should release a version to fix this as soon as possible.
@dcu Does our version solve it 5c2623e or do we still need this?
according to @DAddYE it was .to_s before changing it to .name. his change only reverts back to the original(to_s) behaviour which, I understand, doesn't work because some libs override Class|Module#to_s
I think I explain well in the commit comments why that change won't work
my commit guarantees that it will always work in all cases
OK, let's just apply your change. Does that work @DAddYE
OK, well I applied your version here: 865d67c. Does that look OK @dcu? Thanks for your help in all this. I plan to release a new version soon.
you should start doing faster release cycles. if you don't want to do a 0.10.7 why dont you release 0.10.6.1 ?
@daddye What do you think? Perhaps we should release either what we have as 0.10.7 or do as dcu suggests and just push a 0.10.6.1 at least?
I agree we can release 0.10.7
When is the release due?
We are waiting @nesquena and @achiu confirmations
C'mon guys! You can!
@argent-smith Yay we can and we have, pushed 0.10.7 finally. Sorry everyone for the delays!