Give Winpdb a New Name
I keep getting complaints from users who overlooked Winpdb since its name sounds Windows specific. I am scratching my head for a new name for some time now and will welcome your ideas.
I keep getting complaints from users who overlooked Winpdb since its name sounds Windows specific. I am scratching my head for a new name for some time now and will welcome your ideas.
same crazy ideas
wxpdb
pdbzilla
wpdb
yap (yet another pdb - my favorite
I was going to suggest pydb but that sounds like a database layer. how about pydebug.
the name shouldn’t have wx in it either. use of wx is just an implementation detail. Installing wx on python is such an enormous hassle that I’m probably not going to use the wx interface. i’d have been happier if you used tkinter despite tk’s lame appearance, if you needed a gui. I’ll probably use the curses interface but wish there was a command line interface. maybe i’ll see if i can write one. paul r
Here’s another name: sPYder. Connotations:
SPY: the debugger allows remote observation (spying) on another program
PY: it’s a Python tool
Spider: 1) catches and eats bugs; 2) does this with a spiderweb (i.e. can debug on multiple threads)
Spyder is a good name but it is a term which is heavily used in the internet.
How about some play on the words “the silly step machine”?
Winpdb is a Python debugger. If you’re looking for clarity and “findability”, I would think that pyDebug would be your best bet.
pydebug is a good name. There seems to be a 6 years old debugger called pydebug that is referred to across the internet but most links to it are dead: http://conferences.oreillynet.com/cs/os2001/view/e_sess/1335
Hi,
I am not the creative kind …
but still,
how about PyCruiser or PyCruzer ?
Regards
Anup
If pyDebug’s taken - maybe something like pyDbg or FastPDB ?
How about pyderweb. Same logic as spyder, but this name is not used for anything right now as far as i can tell. I was going to suggest PySpy but that name is already used for something similar, that actually looks interesting in its own right.
How about epdb (enhanced pdb), pdbgui (same idea as winpdb but witout windows reference
)?
Regards,
I like also the idea of pyDebug because newbies will know that it’s THE python debugger
Laurent
the name doesn’t really matter.
Winpdb is a good product so people will get used to the new name.
Don’t choose the name to reflect a functionality (is a firefox related to web browsing ?)
so just take your hometown, or your best friend, change it a little, make a pun, mix it with your own name, or your dog’s, and it will be the most perfect name for your software.
garter
A small snake that eats bugs
http://en.wikipedia.org/wiki/Garter_snake
(and a dandy wardrobe accessory)
http://en.wikipedia.org/wiki/Garter_(stockings)
It actually says it has an un-particular diet and eats anything it can…
And there are about 5,000,000 garter entries in Google which will make it impossible to find the debugger by typing its name in Google.
the answer is in the pain..
smb (save my butt)
ocisua (oh christ, I screwed up again)
scywyjw (stupid code, why won’t you just work!)
IQ (i quit!!)
ibamftl (I’ve been a manager for too long)
sb2am (sleep before 2 am)
guess what my life has been like lately…
I understand that you found Winpdb useful.
How about tiaab?
(There is always another bug)
Cheers,
Nir
of all the names I’ve seen, I think tiaab works really well except for maybe IQ.
this experience reminds me of when I went through renaming my anti-spam system from camram ( given to me by a slightly drunken brit who misspelled campaign for real mail ) to “twopenny blue” these stamp that came after Penny Black and is of higher value.
And yes, I am finding winpdb useful. I wish it had more keystrokes associated with the various functions but, I can live. What I find most frustrating is debugging CGI. the whole restart and lose your breakpoints thing gets old really fast. it would be nice if there were some sort of external storage for breakpoints so that CGI is could have breakpoints reinstalled on acquisition
I willl check why breakpoints are not saved and loaded automatically in the embedded scenario. In the mean time you can use the save and load breakpoints console commands. Let me know if that works for you in the forum: http://sourceforge.net/forum/forum.php?forum_id=485189
Pyriadne (another spider-inspired name).
Pyriadne sounds a little like one of those medicines advertised by SPAM emails…
Today I am releasing a new version of the debugger still with the Winpdb name but I would like this discussion to continue.
Hello!
What is about PyRipper?
Yet another proposition : PyDebUI,
the “deb” part reflects the debugger nature of the product
the “ui” part reflects the graphical appearance of the product
the fact that I feel compelled to explain it to you is not a good sign as to its readability.
Anyhow… good tool ! (and what a great site, Web 2.0 at its best)
I’ll affirm that it needs a new name. I’ve passed over it several times, thinking it was only for windows. Thanks for putting “platform independent” in the pypi description
1 for garter. It’s fun and easy to remember. As for googleability, “garter debugger” brings up only 2,370 results, and is the first thing I would search for anyway.
MWM
Dragonpy. Like dragonfly. Going with the bug theme. Conveniently, dragonflies eat other bugs.
Venus PyTrap, as in a Venus fly trap. Again, bug eating… pytrap is already on SF.net
Inspyctor: look under the hood
omnipytent: be all knowing… about your program, at least
pyty: have it on us poor developers
Pyleup: when your code is a wreck
pyckaxe: hack it out
Pyd Pyper: lure the vermin out of your program (and into the sea?)
Eh, I’m done.
For now.
Chris: I was about to suggest InsPyct but thought it was too lame and just saw your Inspyctor (which I must say I don’t like either, sorry).
pyDebug or pyDebugger are fine, but a little bit boring IMO.
How about pySquash or pySquasher? I can’t find anything in Google with that name.
Keep up with the good work, winpdb (or should I say pySquasher?) is really useful.
ASL.
No, I was SERIOUS.
And no, I don’t wish to leave an email. I do hope you restore the comment.
I find the software useful, but I’m not going to lend my name to advertising or what not. And, if you don’t like the Monty Python references…
well, you’re using the wrong language (:
Vice… no previous comment by you was ever logged on this PHP driven system.
Imho it should have “pdb” in it (python debugger). I like pdbgui, or guipdb.
How about pybug?
But its not a bug
This is the easiest (and best) python debugger I have used so far. How about EasyPDB ? BTW, it’s also very stable. Thanks for the great work.
You should change the name, really. People don’t even try it, because they think it’s windows specific:
http://code.google.com/p/google-highly-open-participation-psf/issues/detail?id=316
Bravo!! Great diagnostic tool. We are now able to debug applications that use the Python “curses” module to handle character cell displays.
“totalpdb” - First thought was triggered by our experience with a shareware file manager for Windows (3.1 through Vista). It was initially named “Windows Commander”. When Microsoft objected, the author re-branded it “Total Commander”.
Second thought is that total denotes a debugger that is most powerful rather than the debuggers portability across a variety of Python platforms.
“vmpdb” - Simple acronym for a Virtual Machine (based) Python Debugger.
totalpdb is a good name
PySwatter!
How about playing around with debug?
- dybug
- debyg
- depug
pdbgui
guipdb
as it’s “a PDB with GUI”
You know, I kinda like these:
PyPaper
PyDebug
PyTrace
PyDbg
The first one I like because it’s a play on words of the FlyPaper/PyPaper.
The other three, I just like because they are simple. PyDebug is likely my favorite simply because I know what it does when I see the name. No illusions there. That’s how I want my debugger, no illusions, no difficulty, just stable, rocksolid, and gives me the information I need quickly and consisely.
I agree with the name change, I really was not even going to com to the website of a windows specific debugger. I agree that it must be unique in a google search. I suggest something along the lines of a venus flytrap. I think it leaves a neat opportunity for a graphical mascot. Maybe a venus flytrap plant with a python curling up it. So perhaps:
VenusPyTrap
PyTrap
FlyTrap
I had a brain storm last night. What about “Pyrite”?
PYthon
Robust
Interactive
Testing
Environment
Slogans:
Make your Python code “Rite”
Find the nuggets of code that are are not gold
Only fools assume their code is golden
—–
http://www.pyrite.org does not exist, but it might get confused with the Pyrite for use Python with Palm PDAs.
I have more, but I think you get the main idea.
How about simply calling it “Bugger!” or “Oh, bugger!”, because that’s what you say when you need it.
Or Buggy, you could have a cute VW beetle as a mascot.
Jitterbug works well to. Or the Swedish variation on Jitterbug, simply called “Bugg”-
Bugger seems to have good searchability.
Craig, Pyrite has a potentially negative under current meaning that can imply that the thing named pyrite is in itself “fool’s gold”. I looked it up in Wikipedia and got a pleasant flashback to the days when I was playing with chemicals in my toy lab as a little kid. Thanks!
Lennart, the same goes for your recommendation. Try to look it up in Google with the “define:” prefix. Not recommended for young people
Filter, PyTrap is already taken.
My vote goes to pySwatter, because it’s a simple tool.
… although on further consideration, winPdb is not so violent, it’s more like a microscope. But pycroscope is strained, pyscope is not as snappy, and pyEye is taken. pyBugBox (or pBB) is an option - to me, a bug box is a transparent box with a magifier in the lid for looking at bugs, though Google doesn’t immediately back me up.
I still think pySwatter is probably the best - immediately suggests an icon, too.
The name _must_ be changed.
“py” and “debug” should be in the new name.
If PyDebug is not available for adoption, then how about PyEzDebug?
EZ or easy == “no good” in most peoples eyes. Not a good option.
Either completely descriptive (e.g. pdbui) or, as suggested by Ange on Nov. 23rd, completely made up (e.g. jadespy - graphical python debugger, or whatever)
PyDB-IDE
PyDB-GUI
gfxpdb
pdb-fx
… or any combination of these
First thought was Pydeb.
But, Pysect is juicier.
happy brainstorming!
wxpdb?
This discussion seems to have petered out and the old name remains! The name for a python symbolic debugger for those of us who like a tipple or two has to be … pysd
…on reflection this connotation is a bit Brit-centric. But it could also be used by Americans when bugs make them really angry…
re: winpdb-1.4.8
i found recently and was using on windows so no big deal about its name…
really nice debugger!
RE NAME:
keep winpdb because one “wins” when they use it… if you want to “win” then use winpdb.
makes sense to me.
b