31–40 of 53 posts
# List your project dependencies here. # For more details, see: # http://packages.python.org/distribute/setuptools.html#declar...
then people might try out your software more easily.
I would help if explained how to get the dependencies in better detail. I have been finding packages for 20 minutes. I would love to try this out but I can't seem to get it running. If you list the project dependencies in your 'setup.py' instead of having # List your project dependencies here. # For more details, see: # http://packages.python.org/distribute/setuptools.html#declar... then people might try out your sof…
I would help if explained how to get the dependencies in better detail. I have been finding packages for 20 minutes. I would love to try this out but I can't seem to get it running. If you list the project dependencies in your 'setup.py' instead of having # List your project dependencies here. # For more details, see: # http://packages.python.org/distribute/setuptools.html#declar... then people might try out your sof…
OK, I will do that. It's listed in Requirements at http://madlag.github.com /jarvis/ , but not yet in the RTD documentation.
It seems everyone is rediscovering Smalltalk!
It seems everyone is rediscovering Smalltalk!
Yeah, except without all the bad parts like images that can get corrupted and stateful (wtf were they thinking?) web-apps.
Earlier quoted context omitted.
Yeah, except without all the bad parts like images that can get corrupted and stateful (wtf were they thinking?) web-apps.
Yeah, the image concept only works properly when Smalltalk is the operating system, as it was originally developed.
(I've often said around here that things would've worked out better if there wasn't such a barrier between stuff happening in Smalltalk and outside in the OS -- community wise. But if you're willing to play just in the Smalltalk sandbox, it's a pretty awesome experience.)
It seems everyone is rediscovering Smalltalk!
Yeah, except without all the bad parts like images that can get corrupted and stateful (wtf were they thinking?) web-apps.
Sorry, I've been a professional in Smalltalk since 1998, and I've never encountered a corrupted image. The closest thing I've seen to that is de-sync with source code. (Which you don't care much about if you're using SCM, for the same reasons everyone else uses SCM.)
stateful (wtf were they thinking?) web-apps.
Same things others were thinking at the time -- you're just seeing a slice of history. People still rave over the debugging in Seaside like it's magic, though.
Earlier quoted context omitted.
Yeah, except without all the bad parts like images that can get corrupted and stateful (wtf were they thinking?) web-apps.
Yeah, except without all the bad parts like images that can get corrupted Sorry, I've been a professional in Smalltalk since 1998, and I've never encountered a corrupted image. The closest thing I've seen to that is de-sync with source code. (Which you don't care much about if you're using SCM, for the same reasons everyone else uses SCM.) stateful (wtf were they thinking?) web-apps. Same things others were thinking…
Typing `C-c p d b` in my Emacs inserts this macro:
import sys; sys.stdout = sys.__stdout__; import ipdb; ipdb.set_trace()
All the benefits of a Lisp REPL and a Smalltalk debugging environment in a language people actually use. Tab-completion, dumps, breakpoints, testing assumptions/data, running arbitrary code inside a specific environ...the works.
I can use it in my virtualenvs without having to explain to an IDE what a virtualenv, a running test in Nose, a normal script, or a running web server. It's normal code so I can wrap the trace in a condition or whatever else I want.
Earlier quoted context omitted.
Yeah, except without all the bad parts like images that can get corrupted Sorry, I've been a professional in Smalltalk since 1998, and I've never encountered a corrupted image. The closest thing I've seen to that is de-sync with source code. (Which you don't care much about if you're using SCM, for the same reasons everyone else uses SCM.) stateful (wtf were they thinking?) web-apps. Same things others were thinking…
>People still rave over the debugging in Seaside like it's magic, though. Typing `C-c p d b` in my Emacs inserts this macro: import sys; sys.stdout = sys.__stdout__; import ipdb; ipdb.set_trace() All the benefits of a Lisp REPL and a Smalltalk debugging environment in a language people actually use. Tab-completion, dumps, breakpoints, testing assumptions/data, running arbitrary code inside a specific environ...the wo…
Earlier quoted context omitted.
>People still rave over the debugging in Seaside like it's magic, though. Typing `C-c p d b` in my Emacs inserts this macro: import sys; sys.stdout = sys.__stdout__; import ipdb; ipdb.set_trace() All the benefits of a Lisp REPL and a Smalltalk debugging environment in a language people actually use. Tab-completion, dumps, breakpoints, testing assumptions/data, running arbitrary code inside a specific environ...the wo…
Apparently, you missed the point -- which was not a nerd missing match. Is this a defensive reaction to my calling you on the "corrupted image" BS?
Sometimes I toss stuff out there in the hopes of being shown something better. It's teaches me new things.
Lets take a moment to think on our poor brethren still tossing print statements all over the place though.