> Don't know if it's already too late, but I suppose feedback is always
> appreciated.
> At first, good idea to remove the regexp section, because it's almost
> always the same. I hope you replace it with a list of list methods?!
> And to the list of special class methods, if you mention some of the
> mathematical operators like __eq__() you should maybe also mention
> that there are a lot more if these (e.g. for shift and modulo etc).
> The sys.argv box and the slicing is done very well, but I miss
> something about string formatting.
> Other things coming into my mind were some unicode decode functions
> (because I'm German and I often have problems with umlauts) and time
> functions, because without them, the strftime reference is more or
> less useless.

> All in all very well done, thanks for your great work, that's one more
> cheat sheet in my collection.

> Greets, Charly

> On 2 Aug., 22:50, Dave Child <d...@addedbytes.com> wrote:
>> Thanks for your feedback, Levi. From the sound of it, I get the
>> impression that there might be better options out there.

>> Saw getbackboard.com the other day - looks like it might be a good
>> alternative. Would be perfect if it allowed you to give a public URL
>> to a board, but sadly you have to invite everyone individually,
>> apparently - which seems a bit odd to me.

>> Dave

>> On 1 Aug, 18:33, Levi Watts <viruswa...@gmail.com> wrote:

>> > On three systems that I have worked on, each had methods of giving
>> > feedback.  I have yet to receive feedback on any of those.  The first
>> > had a user base in the few hundred, but the users didn't have reason
>> > to use it often.  The second and third had active users, but never
>> > over twenty.

>> > A comment system that appears on the same page as the subject being
>> > talked about seem to have the best feedback potential.  Those that
>> > have a comment box right after the user has seen the subject.

>> > In this case, that would be a page dedicated to stating what the sheet
>> > is, an image of it w/ a download link for it, a comment box to follow,
>> > and finally the feedback already received (mix and match as you
>> > please).

>> > I have knowledge in C#, VB, .net, and a few others.  I have no
>> > knowledge in Subversion or Python.

>> > On 1 Aug, 08:31, "David Child" <d...@addedbytes.com> wrote:

>> > > The Python cheat sheet will, unless there's anything else to be
>> > > changed, be released next week, so if you have anything to add or
>> > > suggest, now's the time!

>> > > Latest version is still:http://added-bytes-cheat-sheets.googlegroups.com/web/python_cheat_she...

>> > > The one change that is going to be completed this weekend is that the
>> > > regex section will be replaced (given that regex has its own cheat
>> > > sheet).

>> > > Unfortunately, no feedback on the preview yet, which either means:

>> > > 1) I got it right first time. Woohoo :)
>> > > 2) No Python developers in the group.
>> > > 3) My email saying that the preview was up didn't make it to anyone.
>> > > 4) Google Groups is the wrong format for this sort of feedback system.

>> > > At the risk of this going unread or unanswered, anyone have any ideas
>> > > if there is a better way to get other people involved and solicit
>> > > feedback on cheat sheets before they're released?

>> > > Dave

>> > > --
>> > > AddedBytes.com - Web Marketing and Development