@cewing Thanks. I'll keep your recommendation in mind. I can see an argument for both: Passing exactly what the function needs increases reusability, but passing an entire collection of things streamlines function call. I realized i was using both styles in one project, so I wanted to know what reasons you might have for picking one over the other. My trend seems to be to pass just what the function needs for functions that transform a single value such as:
sanitize_id(id_):
u"""Remove invalid username characters.
Characters are removed here instead of being labled
as invalid at username generation because the API
for one service automatically adds a special character
to the id that another service does not allow.
"""but I also tend to pass entire collections to helper functions if the calling function accepts a collection: get_or_create_customer() needs to accept a collection of customer attributes in case it needs to create a customer, so _get_customer() accepts the same type of collection.
Excellent
cewing @cewing rubs hands together w/ glee
was just about to test it out
I don't see channel history, for one thing :(
but perhaps that's because I just logged in via this transport for the first time
let's see what happens going forward
```python
def some_fun(arg):
print arg
```
blech
not good here in textual
doesn't look like it translates well to the http client either
wonder if there's some multi-line input ability
this is a heading
yeah, @jefrailey can you type a bit of formatted stuff so I can see what it looks like arriving at me?
def function(argument):
u"""Docstring."""
return argument += 1
ah well.
nothing in life is perfect
Not ideal, but it could work as a band aid
might also be a matter of improving the textual IRC theme
this is, after all, just an HTML view
Maybe some appropriate css and such might be able to fix the formatting issues.
cewing @cewing wonders if someone has written such a thing yet
jefrailey @jefrailey is waiting for the trout slap wars
its pretty sweet that this thing suggests rooms based on your github repos
@/all Some of you may see labels on your pull requests that say scary things like, "question," or "invalid." They don't necessarily mean there's something wrong with your pull request--one of us will comment on the request if there is a problem. I'm using them to track requests that I've looked at, but are not yet ready to be merged. "Invalid," means that only some of the files in the pull request have been graded; "question" means that there's either a merge conflict or an out of place file.