You can subscribe to this list here.
2003 |
Jan
(24) |
Feb
(226) |
Mar
(150) |
Apr
(103) |
May
(101) |
Jun
(83) |
Jul
(80) |
Aug
(27) |
Sep
(48) |
Oct
(2) |
Nov
(17) |
Dec
(5) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(11) |
Feb
(67) |
Mar
(53) |
Apr
(60) |
May
(79) |
Jun
(17) |
Jul
(6) |
Aug
(13) |
Sep
(14) |
Oct
(6) |
Nov
(13) |
Dec
(161) |
2005 |
Jan
(37) |
Feb
(31) |
Mar
(82) |
Apr
(119) |
May
(30) |
Jun
(5) |
Jul
(3) |
Aug
(9) |
Sep
(7) |
Oct
(14) |
Nov
(1) |
Dec
(10) |
2006 |
Jan
(32) |
Feb
(18) |
Mar
(12) |
Apr
(14) |
May
(10) |
Jun
(5) |
Jul
(1) |
Aug
(17) |
Sep
(21) |
Oct
(6) |
Nov
(27) |
Dec
(16) |
2007 |
Jan
(4) |
Feb
(6) |
Mar
(18) |
Apr
(1) |
May
(33) |
Jun
(6) |
Jul
(16) |
Aug
(12) |
Sep
(12) |
Oct
(9) |
Nov
(17) |
Dec
(31) |
2008 |
Jan
|
Feb
(4) |
Mar
(9) |
Apr
(29) |
May
(11) |
Jun
(7) |
Jul
(21) |
Aug
|
Sep
(3) |
Oct
(22) |
Nov
|
Dec
|
2009 |
Jan
|
Feb
(5) |
Mar
(4) |
Apr
(8) |
May
(8) |
Jun
(9) |
Jul
(6) |
Aug
(2) |
Sep
(1) |
Oct
(3) |
Nov
|
Dec
|
2010 |
Jan
(16) |
Feb
(6) |
Mar
|
Apr
|
May
(27) |
Jun
(5) |
Jul
(2) |
Aug
(9) |
Sep
(1) |
Oct
(35) |
Nov
(5) |
Dec
|
2011 |
Jan
(18) |
Feb
(3) |
Mar
(18) |
Apr
(18) |
May
|
Jun
(4) |
Jul
|
Aug
(5) |
Sep
|
Oct
(3) |
Nov
(13) |
Dec
(9) |
2012 |
Jan
|
Feb
|
Mar
(4) |
Apr
|
May
(1) |
Jun
(38) |
Jul
(5) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(9) |
2013 |
Jan
(3) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
(6) |
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Akai <ope...@gm...> - 2017-03-04 17:23:45
|
Markus - Annoyingly, sourceforge just auto-discarded your email and I can't figure out how to undo that, so it is below for anyone else who wants to read it. Yeah, Python 2 is getting toward it's EOL. Thankfully, the port seemed to be mostly painless. I was surprised I managed to do as much as I did in six or so hours. Pyblosxom is a really solid engine. Every time I read over the code, I'm amazed at what a good job you all did in making it what it is. Have a great day, Akai Subject: Re: [Pyblosxom-devel] Python3 Branch is up - Pysblosxom From: Markus Koschany Date: 03/03/2017 09:02 PM To: pyblosxom-devel Am 03.03.2017 um 15:41 schrieb Akai: > Hey guys - > > I found some time and started work on bringing Pyblosxom to Python3. > The Branch is up, and about 90% of the features I tested work. > > The comment plugin is still failing badly, and I believe some of the > HTML Stripping functionality of the text views need work. But normal > HTML seems to be working great. > > If any of you feel like hacking on it, enjoy. > Python2 has been getting a little old, and the case for keeping it > around has been slowly vanishing - The thought of starting a new blog by > installing Python2 was hard for me to swallow, and Pyblosxom is still my > favourite engine. > > Have a great day! > > -Akai That is great news. Thank you for working on the Python 3 port. I was a bit worried about Pyblosxom in Debian because we will try to remove Python 2 within the next two years but with Python 3 support its future should be secured. Regards, Markus |
From: Akai <ope...@gm...> - 2017-03-03 14:41:48
|
Hey guys - I found some time and started work on bringing Pyblosxom to Python3. The Branch is up, and about 90% of the features I tested work. The comment plugin is still failing badly, and I believe some of the HTML Stripping functionality of the text views need work. But normal HTML seems to be working great. If any of you feel like hacking on it, enjoy. Python2 has been getting a little old, and the case for keeping it around has been slowly vanishing - The thought of starting a new blog by installing Python2 was hard for me to swallow, and Pyblosxom is still my favourite engine. Have a great day! -Akai |
From: Akai <ope...@gm...> - 2016-02-20 20:51:10
|
Hey guys! So its becoming more and more obvious that my work/life balance isn't going to improve any time soon. What I hoped would be a small disruption has become daily 10-15hr workdays and not leaving me time to work on things I care about, Pyblosxom among them. If any of you have vision and interest in stepping up and doing more with Pyblosom, I'm happy to do at least as much as I'm doing now. Either way, I'm not abandoning the project. Just been too busy to do it justice. I'm happy to be a "maintainer" in that I'm here to answer questions, debug/make patches, maintain the site, etc.., but I'm not anywhere near what you guys deserve in the way of active improvement. Yours, Akai |
From: Akai <ope...@gm...> - 2015-09-29 18:28:55
|
Looks great! I'll get those added to our plugin registry :-) On 9/28/2015 2:08 PM, seanh wrote: > On 27 September 2015 at 22:57, seanh <sn...@gm...> wrote: >> Ah, just realised this plugin doesn't work, you can't use cb_prepare() >> to remove entries from the entry_list. Hopefully this can be re-done >> as a cb_truncatelist() plugin. Will give it a try soon > Fixed! I think it works as documented now, almost the exact same code > but wuth cb_truncatelist() instead of cb_prepare() worked. > > ------------------------------------------------------------------------------ > _______________________________________________ > Pyblosxom-devel mailing list > Pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel |
From: seanh <sn...@gm...> - 2015-09-28 11:09:16
|
On 27 September 2015 at 22:57, seanh <sn...@gm...> wrote: > Ah, just realised this plugin doesn't work, you can't use cb_prepare() > to remove entries from the entry_list. Hopefully this can be re-done > as a cb_truncatelist() plugin. Will give it a try soon Fixed! I think it works as documented now, almost the exact same code but wuth cb_truncatelist() instead of cb_prepare() worked. |
From: seanh <sn...@gm...> - 2015-09-27 21:58:05
|
Ah, just realised this plugin doesn't work, you can't use cb_prepare() to remove entries from the entry_list. Hopefully this can be re-done as a cb_truncatelist() plugin. Will give it a try soon On 27 September 2015 at 22:14, seanh <sn...@gm...> wrote: > https://github.com/seanh/pyblosxomdrafts > > Really simple drafts plugin: any entries that have a "drafts" > directory anywhere in their path are filtered out of index pages, but > can still be viewed by going directly to their permalink pages. |
From: seanh <sn...@gm...> - 2015-09-27 21:15:01
|
https://github.com/seanh/pyblosxomdrafts Really simple drafts plugin: any entries that have a "drafts" directory anywhere in their path are filtered out of index pages, but can still be viewed by going directly to their permalink pages. |
From: seanh <sn...@gm...> - 2015-09-27 21:13:37
|
Just wanted to let people know about a new Pyblosxom plugin: https://github.com/seanh/pyblosxommtimecache It does the same thing as the entrycache plugin (that is: it saves the dates of your entries so that they don't change if you edit a file), but I wanted a version that would keep the entry dates in a YAML file (really nice and easy syntax for editing by hand) and that would have really simple source code and installation instructions. This one was harder than I expected to write, the fact that Pyblosxom requires mtimes in os.stat format is pain. |
From: Akai <ope...@gm...> - 2015-06-01 21:56:15
|
Good catch! I'll test it, and get it merged in as soon as I can (hopefully tomorrow) Thanks On 5/29/2015 3:24 PM, Hauke Fath wrote: > Hi, > > taking the readmore plugin for a spin, I noticed that the text on the > "More..." page is always rendered in the vanilla html flavour. The > following patch, modelled after other plugins, fixes that and makes it > use > the current flavour, if set: > > > --- Pyblosxom/plugins/readmore.py.orig 2013-07-31 > 00:53:58.000000000 +0000 > +++ Pyblosxom/plugins/readmore.py > @@ -209,7 +209,11 @@ def cb_story(args): > # otherwise we replace the breakpoint with the template > base_url = config["base_url"] > file_path = entry["file_path"] > - flavour = config.get("default_flavour", "html") > + > + # Set and use current (or default) flavour for full entry > + flavour = data.get( > + "flavour", config.get("default_flavour", "html")) > + > url = '%s/%s.%s' % (base_url, file_path, flavour) > > link = (template % {"url": url, > > > (see also > <http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/www/py-blosxom/patches/patch-Pyblosx > > om_plugins_readmore.py>). Please apply. > > Cheerio, > hauke > > > -- > "It's never straight up and down" (DEVO) > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Pyblosxom-devel mailing list > Pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel |
From: Hauke F. <hauke@Espresso.Rhein-Neckar.DE> - 2015-05-29 13:22:37
|
Hi, taking the readmore plugin for a spin, I noticed that the text on the "More..." page is always rendered in the vanilla html flavour. The following patch, modelled after other plugins, fixes that and makes it use the current flavour, if set: --- Pyblosxom/plugins/readmore.py.orig 2013-07-31 00:53:58.000000000 +0000 +++ Pyblosxom/plugins/readmore.py @@ -209,7 +209,11 @@ def cb_story(args): # otherwise we replace the breakpoint with the template base_url = config["base_url"] file_path = entry["file_path"] - flavour = config.get("default_flavour", "html") + + # Set and use current (or default) flavour for full entry + flavour = data.get( + "flavour", config.get("default_flavour", "html")) + url = '%s/%s.%s' % (base_url, file_path, flavour) link = (template % {"url": url, (see also <http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/www/py-blosxom/patches/patch-Pyblosx om_plugins_readmore.py>). Please apply. Cheerio, hauke -- "It's never straight up and down" (DEVO) |
From: Markus K. <ap...@ga...> - 2013-10-29 16:07:11
|
On 29.10.2013 12:16, Akai wrote: > Hi - > > No problem, thank you! > The files are there, I just has mislinked them > I have updated the page and all download links work correctly again. > > Let me know if there is any issue with the naming scheme, it looks > correct to me. Thanks for taking care of this. If you renamed the Downloads folder to download again, that would be perfect. If it is too much trouble, never mind, then I will adjust the script that scans for new upstream releases with the next regular update of pyblosxom. Regards, Markus |
From: Akai <ope...@gm...> - 2013-10-29 11:16:08
|
Hi - No problem, thank you! The files are there, I just has mislinked them I have updated the page and all download links work correctly again. Let me know if there is any issue with the naming scheme, it looks correct to me. On 10/28/2013 10:05 PM, Markus Koschany wrote: > Hi Akai, > > I just wanted to say hello and thank everyone for their work on > pyblosxom and your kind words on the former front page. I intend to > maintain pyblosxom for Debian for the foreseeable future. > > It seems that the links to older releases are currently broken. Would it > be possible to fix them because some Debian QA tools depend on that, > namely a process that checks for newer upstream versions of pyblosxom. > This tool also depends on a correct naming scheme for release tarballs > like pyblosxom-1.5.3.tar.gz. > > Thanks in advance and please feel free to contact me directly, if you > have any questions regarding the Debian package of pyblosxom. > > Regards, > > Markus > > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > > > _______________________________________________ > Pyblosxom-devel mailing list > Pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel |
From: Markus K. <ap...@ga...> - 2013-10-28 20:05:10
|
Hi Akai, I just wanted to say hello and thank everyone for their work on pyblosxom and your kind words on the former front page. I intend to maintain pyblosxom for Debian for the foreseeable future. It seems that the links to older releases are currently broken. Would it be possible to fix them because some Debian QA tools depend on that, namely a process that checks for newer upstream versions of pyblosxom. This tool also depends on a correct naming scheme for release tarballs like pyblosxom-1.5.3.tar.gz. Thanks in advance and please feel free to contact me directly, if you have any questions regarding the Debian package of pyblosxom. Regards, Markus |
From: Akai <ope...@gm...> - 2013-10-13 18:51:56
|
Hi everyone - The new site is deployed! Besides modernizing the look a little, the new site's goal is to make it easier to find things, make changes, and keep track of the existing content. The new design also makes it easier to make visible micro-updates (such as tweets) for things that aren't HUGE issues, but should be visible. The old site is great and I'd like the new one to be at least as good, if not amazingly better - so let me know if you catch any issues or think any changes should be made (or feel free to do a github pull request to that page. Its all static HTML as of right now, except for the plugins/flavours) I have many more changes to make, which will hopefully improve PyBlosxom as well. The site is available at our normal URL http://pyblosxom.github.io/ Yours, -Akai |
From: Zoom.Quiet <zoo...@gm...> - 2013-07-31 11:43:39
|
thanx for all! waiting so long time... 2013/7/31 Akai <ope...@gm...>: > Thanks! :-) > > On 7/31/2013 1:22 PM, Hauke Fath wrote: >> On Wed, 31 Jul 2013 04:37:46 +0300, Akai wrote: >>> Version 1.5.3 has been released! >> Thanks! >> >> I updated the pkgsrc www/py-blosxom package. >> >> Cheerio, >> hauke >> > > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > Pyblosxom-devel mailing list > Pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel -- 人生苦短, Pythonic! 冗余不做,日子甭过!备份不做,十恶不赦! KM keep growing environment culture which promoting organization be learnning! 俺: http://about.me/zoom.quiet 许: http://creativecommons.org/licenses/by-sa/2.5/cn/ |
From: Akai <ope...@gm...> - 2013-07-31 10:28:32
|
Thanks! :-) On 7/31/2013 1:22 PM, Hauke Fath wrote: > On Wed, 31 Jul 2013 04:37:46 +0300, Akai wrote: >> Version 1.5.3 has been released! > Thanks! > > I updated the pkgsrc www/py-blosxom package. > > Cheerio, > hauke > |
From: Hauke F. <hauke@Espresso.Rhein-Neckar.DE> - 2013-07-31 10:22:22
|
On Wed, 31 Jul 2013 04:37:46 +0300, Akai wrote: > Version 1.5.3 has been released! Thanks! I updated the pkgsrc www/py-blosxom package. Cheerio, hauke -- Hauke Fath <hauke@Espresso.Rhein-Neckar.DE> Ernst-Ludwig-Straße 15 64625 Bensheim Germany |
From: Akai <ope...@gm...> - 2013-07-31 01:37:50
|
Hi Everyone - Version 1.5.3 has been released! You can get it the normal way: via the download page here: http://pyblosxom.github.io/download/ or via pip: pip install pyblosxom Feel free to comment on anything. It's been a while since our last release - Let me know what you like, what you hate and if anything broke. I'm moving from here to adding in the Jinja2 plugin and getting more themes and plugins together to hopefully improve the ease of getting started Have a great day! |
From: Janis K. <ja...@fi...> - 2013-07-19 19:06:53
|
Akai wrote: > Hi, > > How many of you are using the latest version from git? > I think it might be time to make a point release, and then move to > adding new features such as the integration of the theme repos, Jinja2, > etc.. > > -Akai > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Pyblosxom-devel mailing list > Pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel > > > I haven't upgraded yet.. It's been very busy since we moved. I'll see if I can grab the lastest release today <grin> Ok, just downloaded pyblosxom-1.5.2.tar.gz :) Thanks Akai, appreciate your time in this. Take care, Janis |
From: Akai <ope...@gm...> - 2013-07-18 21:46:28
|
Hi, How many of you are using the latest version from git? I think it might be time to make a point release, and then move to adding new features such as the integration of the theme repos, Jinja2, etc.. -Akai |
From: Akai <ope...@gm...> - 2013-06-26 01:43:54
|
Hi, It's been a pretty tumultuous year both for me and PyBlosxom. I've spent a lot of this time getting used to the codebase, which was frankly somewhat intimidating to someone new to the project, which I was when I first joined a year ago. On the Pyblosxom front, Although we haven't had a super-large amount of updates, We did get some bugs squashed and began a new repo for external plugins, which I hope will eventually lead to plugins being more updated and accessible Markus Koschany (https://launchpad.net/~apoleon) has been working on the Debian repo to finally get our package there updated for the next release. (If you are on this list, Thank you!) We made the move over to GitHub will all our stuff and the documentation has been updated to reflect it I'm happy to note it looks like we got a few new installs and a few new faces appeared on IRC We also now have a shiny new repo for themes - I've uploaded an updated version of MainlyGreen to get started with, which has been updated for the latest PyBlosxom and optimized for pagnate and the comments plugin. If anyone would like to submit cool themes, tested and converted or not, I'd be happy to test and update them. |
From: seanh <sn...@gm...> - 2013-04-14 11:04:06
|
Hey, setting up pyblosxom using CGI on a shared UNIX server. I appended to sys.path in pyblosxom.cgi to add the python-markdown lib (for pyblosxom's markdown plugin), just as it does to add the config.py file: sys.path.append("/arpa/s/seanh/pyblosxom/blog/") sys.path.append("/arpa/s/seanh/python-markdown") but this resulted in python-markdown crashing. I found out that the reason was that there was a different python module also called "markdown" installed by someone else system-wide, and the path to this module was before the path to my python-markdown module on sys.path. So I've now changed the two lines in my pyblosxom.cgi to this: sys.path.insert(0, "/arpa/s/seanh/pyblosxom/blog/") sys.path.insert(0, "/arpa/s/seanh/python-markdown") and it works. Changing the first line wasn't necessary to fix my markdown plugin problem but I changed it anyway just to be safe. I wonder if the CGI deployment instructions and default pyblosxom.cgi file should be changed to use insert instead of append? It seems safer |
From: Akai <ope...@gm...> - 2013-01-31 09:51:47
|
The issue has been fixed and pushed. Thanks for the tip Will! On 1/27/2013 1:52 AM, will kahn-greene wrote: > When you're using it in a CGI context, then print statements will print > to stdout. > > There's at least one print statement in cb_handle around line 144. > That's probably causing the problem. Try removing that. > > /will > > > On 01/26/2013 06:09 PM, Akai Kistune wrote: >> Hey! >> >> I'm playing with different hosting options and the >> Pyblosxom.plugins.flavourfiles seems to break my Apache CGI setup. >> I haven't spotted what could be triggering it. >> >> Apache log - malformed header from script. bad header=/flavourfiles/: >> pyblosxom.cgi >> >> Ideas anyone? > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnnow-d2d > _______________________________________________ > Pyblosxom-devel mailing list > Pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel |
From: will kahn-g. <wi...@bl...> - 2013-01-27 00:14:44
|
When you're using it in a CGI context, then print statements will print to stdout. There's at least one print statement in cb_handle around line 144. That's probably causing the problem. Try removing that. /will On 01/26/2013 06:09 PM, Akai Kistune wrote: > Hey! > > I'm playing with different hosting options and the > Pyblosxom.plugins.flavourfiles seems to break my Apache CGI setup. > I haven't spotted what could be triggering it. > > Apache log - malformed header from script. bad header=/flavourfiles/: > pyblosxom.cgi > > Ideas anyone? |
From: Akai K. <ope...@gm...> - 2013-01-26 23:09:56
|
Hey! I'm playing with different hosting options and the Pyblosxom.plugins.flavourfiles seems to break my Apache CGI setup. I haven't spotted what could be triggering it. Apache log - malformed header from script. bad header=/flavourfiles/: pyblosxom.cgi Ideas anyone? |