Menu
▾
▴
pydispatcher-devel — Python Dispatcher Developers
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(21) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(7) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
(1) |
Mar
|
Apr
(2) |
May
(3) |
Jun
(4) |
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2005 |
Jan
(1) |
Feb
(8) |
Mar
|
Apr
(2) |
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
(9) |
Oct
(2) |
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Patrick K. O'B. <po...@or...> - 2003-07-01 22:43:24
|
On Tuesday 01 July 2003 05:17 pm, Mike C. Fletcher wrote: > Python (CNRI) license is actually pretty complex and involved compared > to a BSD or MIT license. PythonLabs Python license is just a pointless > maze of complexity. I'm fine with a Python license (it's your code > after all), I can copy it into the distribution just as easily as the > shorter ones. If you registered the project with Python (CNRI) license, > then let's just go ahead and use that. > > Make a final statement and I'll copy in the appropriate license.txt from > OpenSource.org. The project was registered under the Python Software Foundation License. If it's good enough for Python, it should be good enough for dispatcher, since I'm not a lawyer. So let's go with that for now, and if you'd like a BSD or MIT license I would gladly give it to you with that license as well. http://www.opensource.org/licenses/PythonSoftFoundation.php -- Patrick K. O'Brien Orbtech http://www.orbtech.com/web/pobrien ----------------------------------------------- "Your source for Python programming expertise." ----------------------------------------------- |
|
From: Mike C. F. <mcf...@ro...> - 2003-07-01 22:31:56
|
Patrick K. O'Brien wrote: >On Tuesday 01 July 2003 08:56 am, Mike C. Fletcher wrote: > > >>We don't currently have any documentation for using dispatcher. Would >>be nice to get something put together for the home page + docs >>directory. There is a placeholder in the docs directory of the dispatch >>project at the moment. >> >> > >I prefer reST for documentation, or wiki pages. I've got a wiki site that we >can use, if we want. > I'd like to include documentation in the distribution. Never used reST, I tend to write directly in basic HTML w/ class properties and use CSS to present it. That works fine for me, and produces good-looking documentation, but I'm certainly open to someone else writing the docs in reST ;) , as a last resort, I'll learn reST, but I'm not really thrilled with the format. Wiki is cool for enhancing a basic documentation set, but I'm thinking here of "basic usage" and reference docs, the kind of things you really want to have available whereever the package gets installed. >>Note that there is a problem with SourceForge's file upload which makes >>it a royal pain to update the website, I will do so when we have a >>"presentable" site, but I'm not particularly interested in updating it >>for every minor change. >> >> > >We could also just point to a section of my website (www.orbtech.com) where we >can put pages for this. > If I'm working on the site, I'd rather use the SF server, I've got batch files that allow me to automatically update the website directly via scp (once SF gets itself fixed). Probably easier than giving me an account on orbtech. >>Also integrated the changes I could see in the dispatcher module of the >>event package into the dispatcher module of the dispatch package. I >>don't have any unit tests to check those effects, however, so this is >>really just "it didn't appear to break anything", rather than a robust >>integration effort. >> >> > >I've always felt bad that there aren't unit tests for this thing, so this is >just another reason to make them a priority. So little time, so many things >to test. > The current test suite is really quite minimal (I think there's only about 15 tests), they just test basic functionality of the 3 modules, no failure-case tests, no real stress tests, there's lots of room for improvement. BTW, no need to copy me on posts, I'm subscribed to the dev list. Have fun, Mike _______________________________________ Mike C. Fletcher Designer, VR Plumber, Coder http://members.rogers.com/mcfletch/ |
|
From: Mike C. F. <mcf...@ro...> - 2003-07-01 22:17:38
|
Patrick K. O'Brien wrote: >On Tuesday 01 July 2003 08:56 am, Mike C. Fletcher wrote: > > >>Okay, doing some preliminary work on this... >> >> * We'll want a license declaration. I'm assuming something like >> BSD/MIT or similar wide-open license. >> >> > >I just assumed we'd do a Python license. Do you have a particular preference? > Python (CNRI) license is actually pretty complex and involved compared to a BSD or MIT license. PythonLabs Python license is just a pointless maze of complexity. I'm fine with a Python license (it's your code after all), I can copy it into the distribution just as easily as the shorter ones. If you registered the project with Python (CNRI) license, then let's just go ahead and use that. Make a final statement and I'll copy in the appropriate license.txt from OpenSource.org. Have fun, Mike _______________________________________ Mike C. Fletcher Designer, VR Plumber, Coder http://members.rogers.com/mcfletch/ |
|
From: Patrick K. O'B. <po...@or...> - 2003-07-01 22:11:32
|
On Tuesday 01 July 2003 08:56 am, Mike C. Fletcher wrote: > We don't currently have any documentation for using dispatcher. Would > be nice to get something put together for the home page + docs > directory. There is a placeholder in the docs directory of the dispatch > project at the moment. I prefer reST for documentation, or wiki pages. I've got a wiki site that we can use, if we want. > Note that there is a problem with SourceForge's file upload which makes > it a royal pain to update the website, I will do so when we have a > "presentable" site, but I'm not particularly interested in updating it > for every minor change. We could also just point to a section of my website (www.orbtech.com) where we can put pages for this. > Also integrated the changes I could see in the dispatcher module of the > event package into the dispatcher module of the dispatch package. I > don't have any unit tests to check those effects, however, so this is > really just "it didn't appear to break anything", rather than a robust > integration effort. I've always felt bad that there aren't unit tests for this thing, so this is just another reason to make them a priority. So little time, so many things to test. Thanks for all your work, btw. -- Patrick K. O'Brien Orbtech http://www.orbtech.com/web/pobrien ----------------------------------------------- "Your source for Python programming expertise." ----------------------------------------------- |
|
From: Patrick K. O'B. <po...@or...> - 2003-07-01 22:02:51
|
On Tuesday 01 July 2003 08:56 am, Mike C. Fletcher wrote: > Okay, doing some preliminary work on this... > > * We'll want a license declaration. I'm assuming something like > BSD/MIT or similar wide-open license. I just assumed we'd do a Python license. Do you have a particular preference? > * I've done a preliminary trove categorisation for the project > * Considering "dispatch" as the name for the package, so > o from dispatch import dispatcher Sounds good to me. -- Patrick K. O'Brien Orbtech http://www.orbtech.com/web/pobrien ----------------------------------------------- "Your source for Python programming expertise." ----------------------------------------------- |
|
From: Mike C. F. <mcf...@ro...> - 2003-07-01 05:01:29
|
Probably will not be doing any more work on the dispatcher project until the weekend. Good time to check out the "dispatch" package from CVS and play with what's currently in there. Enjoy, Mike _______________________________________ Mike C. Fletcher Designer, VR Plumber, Coder http://members.rogers.com/mcfletch/ |
|
From: Mike C. F. <mcf...@ro...> - 2003-07-01 04:30:06
|
We don't currently have any documentation for using dispatcher. Would be nice to get something put together for the home page + docs directory. There is a placeholder in the docs directory of the dispatch project at the moment. Note that there is a problem with SourceForge's file upload which makes it a royal pain to update the website, I will do so when we have a "presentable" site, but I'm not particularly interested in updating it for every minor change. Also integrated the changes I could see in the dispatcher module of the event package into the dispatcher module of the dispatch package. I don't have any unit tests to check those effects, however, so this is really just "it didn't appear to break anything", rather than a robust integration effort. Enjoy, Mike _______________________________________ Mike C. Fletcher Designer, VR Plumber, Coder http://members.rogers.com/mcfletch/ |
|
From: Mike C. F. <mcf...@ro...> - 2003-07-01 03:25:21
|
Okay, doing some preliminary work on this...
* We'll want a license declaration. I'm assuming something like
BSD/MIT or similar wide-open license.
* I've done a preliminary trove categorisation for the project
* Considering "dispatch" as the name for the package, so
o from dispatch import dispatcher
Will likely check in "dispatch" in a few hours (I'm just reading through
the copy in event to see what needs to be integrated from there).
Enjoy,
Mike
_______________________________________
Mike C. Fletcher
Designer, VR Plumber, Coder
http://members.rogers.com/mcfletch/
|
