Subscribe: SourceForge.net: SF.net Project News: PyPE (Python Programmers Editor)
http://sourceforge.net/export/rss2_projnews.php?group_id=85104
Added By: Feedage Forager Feedage Grade B rated
Language: English
Tags:
betas  command  current  features  files  find  much  news  plugin  pype  python  release  replace  shell  shells  time  unicode  work 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: SourceForge.net: SF.net Project News: PyPE (Python Programmers Editor)

Recent posts to news



Recent posts to news



Last Build Date: Fri, 14 Sep 2012 21:28:07 -0000

 



PyPE Subversion

Fri, 14 Sep 2012 21:28:07 -0000

PyPE is now available via subversion. I probably should have put it up years ago, but eh?



2.3/2.3.1

Fri, 14 Sep 2012 21:28:06 -0000

Sorry about those find/replace bugs. I hadn't been using 'replace all', 'replace in selection' or even 'find previous' very often, but I should have checked everything when I added in the interactive 'replace all' and 'replace in selection'. Sorry about that. I hope everyone likes the embedded Python and command shells. There are still a few nits that I'd like to fix, but not for a while - they work quite well for what I indended them to. One minor note: on Windows, sometimes even when you SIGKILL something, and you get a "process ended" event, sometimes the process survives. I don't know why this is, but be careful!



Screenshots?

Fri, 14 Sep 2012 21:28:06 -0000

Does anyone have some screenshots of PyPE running in Linux or on a Mac? Alternatively, have people been having issues running PyPE on Linux or Mac that would preclude such screenshots from being taken?



Embedded shell?

Fri, 14 Sep 2012 21:28:06 -0000

I have previously spoken against the embedding of shells in PyPE, primarily because I have had bad luck with certain editors crashing during experimentation. What do I mean? Take any one of a number of Python source editors with an embedded shell and try 'while 1: pass'. Note how you've essentially killed your editor? Ick. During my use of wx.Shell, I've come to the point where embedding shells is somewhat reasonable. You can get an ugly command-line and/or Python interpreter with the current shell, but that's only one. I, like many of you, tend to have a handful of command lines open, not a few of which are Python shells, and honestly, I prefer seeing a shell with syntax highlighting. With that said, I've taken some ideas from Orbtech's PyShell as shipped with wxPython, added remote execution capabilities, and added the ability to use ctrl+break to attempt to stop the current execution. This doesn't work all the time, so if necessary, it will close stdin on the remote shell, and kill the process after a second or third ctrl+break (automatically starting up a new shell as necessary). My plan is to make adding a Python shell or command shell as easy as creating a new document, and probably just remove the shell tab on the bottom toolbar. That's about all from me for right now. So much stuff to do.



PyPE 2.1 release

Fri, 14 Sep 2012 21:28:06 -0000

Skipping a 2.0 release (because I've been numbering the betas 2.0.x), we've gone straight to a non-beta 2.1 . I've been running this version for the last week or so, and it has been quite solid so far. This is a suggested upgrade to everyone who has ever run PyPE. A big thank you to Dave Schuyler, who poked and prodded me for months during the various betas suggesting features and offering code, I don't know how many revisions we emailed back and forth (but I could probably count if I really wanted to). He is directly and/or indirectly responsible for much of the intuitive Find/Replace behavior, the toolbar, swapping locations of the name/line and log bars, Search tab, smartcasing, ctags, and others. Astute observers will note that this is the first non-beta release in over a year. For those of you who have been unwilling to run the Betas (are there any?), this will be a big change for you. As such, I've hidden the download for 1.9.3, which has had over 4600 downloads since its release last year. Not bad at all. Let's see if we can break 10k on this one. Spelunkers will notice an unfinished C/C++ parser in the parsers.py module. I will likely finish it by the next release, but wouldn't be averse to the idea of a user-supplied parser. As always, check the changelogs, look through the menus, and enjoy!



PyPE 2.0 sometime

Fri, 14 Sep 2012 21:28:06 -0000

Work on the 2.0 betas is progressing, albeit slowly (I've also got work and paper writing, there is only so much time to spare). The next beta/release will include an updated find in files tab with support for multiple types of views, cTags searching, and other goodies.



PyPE 2.x status

Fri, 14 Sep 2012 21:28:06 -0000

So, after spending all too much time working on a rewrite of PyPE, I decided to just start hacking on PyPE 1.9.3, adding in those pieces that I had promised in the last news post. I have many of the changes that I wanted to get in done, though it is not done yet. I had promised another PyPE user that it would be done by January 1st, but I'm going to need to spend much of my remaining time until New Year's working on a paper. Sorry! Fear not, 2.x will eventually get done (I know I want/need some of the features that I'm working on), and will include all the features listed before and more. Thank you for using PyPE!



PyPE 2.x

Fri, 14 Sep 2012 21:28:06 -0000

Indeed, there will be more PyPE. I have a direction I'd like PyPE to move, and it would be there if I hadn't been employed full time developing with Python over the summer (contract ends in a week), and doing research on an interesting problem for graduate work. Fear not however, I have the framework built, and 90% of PyPE 1.x can be transferred with no change, though I'm going to do a bit of work on the auto-indent and parser. There will be a plugin system, in fact, most everything that existed in the menus before, will become a plugin. It will include options to register hotkeys and all that other good stuff, perhaps even menu additions. Plugins will be optional, select as many or as few as you desire, even where each plugin will be (above, below, to the left, or to the right of the editing window). With this plugin system will come all sorts of strange and wonderful things: 1. Filesystem browser (with pathmarks) 2. Project manager (project files with folder structure for organization, perhaps with auto-generation of setup.py files) 3. Find in current document/files will be moved to a plugin. 4. Todo will become a plugin, will allow arbitrary strings (todo list, fixme list, etc), and will have options for per-document, all open documents, AND current open project. If someone wants to write an interpreter plugin, while I wouldn't ever ship it with PyPE, I would provide a link (I've been bitten by interpreter+editor crashes before). I'll also be including the ability to 'split' the window vertically or horizontally once, so that if you want to be viewing two parts of the same document, or even view two different documents simultaneously, you would be able. Yeah, all sorts of good stuff is going to be coming to PyPE, and I'm sorry it is not already done. But hey, for-pay software gets priority over for-fun software.



State of PyPE

Fri, 14 Sep 2012 21:28:06 -0000

As most people will notice, PyPE has become better with each subsequent release. Version 1.9.1 works pretty well, and has most everything that I want/need, which begs the question: Where will PyPE go from here? Honestly, I don't know. I didn't really have a direction for PyPE when I first started, other than wanting it to be stable, fast and useful. I believe it fulfills those goals right now, and future versions likely won't have significantly more features than PyPE does right now. Perhaps a few more options like coloring function and class definitions, maybe new icons, maybe moving the todo items into the browsable source tree, makes sense. I'll do my best to try to fix the few remaining unicode bugs (having to do with files with unicode names, or in paths with unicode names) when solutions present themselves, but likely all major work will be pushed off until the summer of 2004, when I will (hopefully) be less busy. Thank you for using PyPE.



PyPE 1.6.5.2 released (little fanfare)

Fri, 14 Sep 2012 21:28:06 -0000

PyPE 1.6.5.2 has just been released (as the subject says), with a few fixes over the 24-hour-old release of 1.6.5. If you really want to know the fixes, there's the changelog to check. The real fanfare ordeal is PyPE 1.6.5, which includes support for Unicode on systems that support it. There are, of course, a few visual modifications, bugfixes, etc., but yeah, Unicode and stuff. While I have no need for unicode (only really being able to speak English), there are seemingly ~6 billion people on this planet, some of which have access to computers, many of which DON'T speak English, and have a use for PyPE. Anyways, I can't imagine that this news post would make it to the front page, and I can't imagine that anyone but me is actually going to read it. So, without further ado, "Spoon!" - The Tick