Team Chat Logs

2007 0
Mo Tu We Th Fr Sa Su
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30 31        

January 13, 2007

[00:00:45] <alect> elpargo: what version?
[00:00:50] <alect> of trac
[00:01:56] * em-dash has joined #trac
[00:09:30] * Fatal_2 has quit IRC
[00:09:56] * Hydra_ has quit IRC
[00:18:26] * em-dash has quit IRC
[00:20:46] * em-dash has joined #trac
[00:37:50] * cboos has joined #trac
[00:41:13] * gakman has joined #trac
[00:46:53] * pradeep has joined #trac
[00:51:13] * gak has quit IRC
[01:00:57] <cboos> alect?
[01:01:16] <cboos> just saw r4557...
[01:01:46] <cboos> please look again at http://trac.edgewall.org/changeset/4557/sandbox/security/trac/resource.py :)
[01:02:10] <cboos> self._context_map != self._resource_map ...
[01:03:13] * cboos goes back to the "Away" state
[01:05:20] * Sweetsha1k has joined #trac
[01:07:47] <Markonen> uh oh
[01:08:29] <Markonen> I always miss cboos and don't get to slap him with this: http://trac-hacks.org/ticket/951#comment:3
[01:08:53] * gak has joined #trac
[01:09:03] * cboos is happy to be away, then ;)
[01:09:11] <Markonen> haha :)
[01:09:31] <cboos> actually I was going to take a shower, but this can perhaps wait a bit ...
[01:09:47] <cboos> so yes, the DoxygenPlugin is badly lacking support
[01:10:41] <cboos> well, the thing is that I installed it once at my job, it already had a few issues, then requested commit rights to make a bunch of fixes, then left it alone again...
[01:11:02] <cboos> now I'm supposed to be the "maintainer" of it, but this is not really the case in practice, as you can see...
[01:11:05] <Markonen> I figured as much, yet I'm sure it has some users blissfully unaware of that issue, and it's a real killer :)
[01:12:27] <cboos> well, if you harass me again today or tomorrow about it, I'm sure I'll take the 5 minutes needed to fix that ;)
[01:12:38] <Markonen> cool, thanks!
[01:13:17] * cboos really takes that shower now
[01:13:24] * Sweetshark has quit IRC
[01:17:31] * gakman has quit IRC
[01:40:11] * pradeep has quit IRC
[01:40:40] * asmodai pats cboos
[01:46:08] * coderanger has joined #trac
[01:48:52] <mitsuhiko> pygi: ping
[01:50:53] <asmodai> mitsuhiko: PANG!
[01:50:56] * asmodai pats coderanger
[01:51:04] <coderanger> yo
[01:51:11] <mitsuhiko> asmodai: hoi :D
[01:51:16] <asmodai> hawwo
[01:51:36] <coderanger> g'morning
[01:52:01] <mitsuhiko> anyone using pygments for highlighting ruby sources here?
[01:59:22] <asmodai> Not me
[01:59:23] <asmodai> Not yet
[02:18:14] * m_g has joined #trac
[02:42:22] * em-dash has quit IRC
[02:55:47] <coderanger> Is anyone having problems with edgewall svn?
[02:56:46] <The_Tick> I can pretend to be
[02:56:48] <The_Tick> if you like
[02:57:00] <coderanger> heh
[02:59:02] <coderanger> The_Tick: Late night?
[02:59:22] <The_Tick> ya
[02:59:33] <The_Tick> did the postgres move
[03:00:43] <coderanger> any faster?
[03:01:32] <coderanger> the roadmap still seems bad
[03:04:46] <cboos> coderanger: svn.edgewall.org seems to be OK for me, just did an update
[03:05:04] <coderanger> cboos: I can update on https, but not http
[03:05:26] <coderanger> PROPFIND of '/repos/trac/branches/0.10-stable': Could not read status line: Connection reset by peer (http://svn.edgewall.org)
[03:05:33] <cboos> ah, let me do svn info...
[03:05:48] <cboos> URL: http://svn.edgewall.com/repos/trac/sandbox/security
[03:05:56] <cboos> seems slow, but works
[03:06:25] <cboos> well, now, browsing there is even responsive, so np for me
[03:06:50] <coderanger> hmm same thing on checkout, same error on http, works fine on https
[03:07:15] <coderanger> oh well, I'll just use https :)
[03:10:49] * lowkey has joined #trac
[03:12:26] <cboos> coderanger: have you tried the blame branch so far?
[03:12:44] <coderanger> nope, setting up that and security on my dev machine right now
[03:13:05] <cboos> cool,
[03:13:22] <cboos> but try first with the blame branch as the security one was messed up by the last commit
[03:13:44] * cboos fixes that right now
[03:14:00] * termie has quit IRC
[03:14:23] <cboos> + the authz_policy example needs to be updated as well
[03:14:59] <cboos> I wonder if we shouldn't ship this kind of sample plugin with Trac itself
[03:15:14] <cboos> a 'plugins' dir, similar to the old toplevel 'macros' one
[03:15:35] <coderanger> that gets back to the bundling argument
[03:15:41] <cboos> actually renaming that 'macros' folder to 'plugins', as there's no reason to keep the macros one
[03:15:56] <cboos> well, not really. Those won't be ''real'' plugins
[03:16:02] <coderanger> I would rather see a plugin manager tool be included, instead of plugins
[03:16:05] <cboos> just single file plugins that can be used as examples
[03:16:27] <cboos> (as we had the hello_world.py macro)
[03:16:32] <coderanger> the majority of people using Trac probably won't care about dev stuff
[03:17:02] <coderanger> not that there is much of a downside, just an extra file
[03:17:03] <cboos> well, not that true, a lot of people certainly wrote little old-style macros
[03:17:36] <cboos> and now that this is not possible anymore, they need to convert the old-style macros to the new-style one
[03:17:45] <coderanger> ahh, yeah
[03:17:51] <coderanger> for macro plugins that makes sense
[03:18:02] <coderanger> I was thinking an example requesthandler or something
[03:21:49] * cboos_ has joined #trac
[03:21:54] * Sweetshark has joined #trac
[03:24:31] <cboos_> damn, I already ported TracGuideToc.py to 0.11, where's that file?
[03:24:43] <coderanger> trac.wiki.macros?
[03:24:56] <cboos_> ahhh, yes thanks ;)
[03:25:06] <cboos_> forgot :)
[03:26:33] <coderanger> hrmm, so on a fresh checkout of the blame branch I can't get to the browser
[03:27:13] <cboos_> well, the template has changed a bit, be sure to use the one from the branch
[03:27:27] <cboos_> (the templates_dir stuff from trac.ini should be unset)
[03:27:35] <pygi> Miek, I'm here, how may I help
[03:27:50] <pygi> bleh
[03:27:53] <pygi> wrong tab xD
[03:33:14] <coderanger> cboos: Never mind, glitch in my dev scripts
[03:33:36] <coderanger> trunk changed the behavior of --pid-file with tracd
[03:34:46] <cboos_> oops, alect did r4552 on trunk! not on the security branch... no wonder the rename was incomplete there ;)
[03:35:19] <coderanger> If every line in browser is prefixed with "TEXT" is that a pygments issue?
[03:35:30] <cboos_> yes
[03:35:44] <cboos_> too old version I think
[03:35:49] <cboos_> try with the release 0.6
[03:36:02] <cboos_> (link available in
[03:36:05] <cboos_> @milestone 0.11
[03:36:05] <evil_twin> cboos_: Error: "milestone" is not a valid command.
[03:36:07] <mitsuhiko> coderanger: hmm. maybe an incompatibility with trac
[03:36:14] <mitsuhiko> but TEXT is nowhere in the pygments sources
[03:36:35] <cboos_> .. or maybe you have the pygments plugin active?
[03:36:44] <coderanger> nope, not installed on here
[03:36:54] <coderanger> still seeing it with 0.6
[03:37:09] <cboos_> look in About / system configuration, does it say 0.6 ?
[03:37:11] * Sweetsha1k has quit IRC
[03:38:11] <coderanger> I don't have pygments listed there at all
[03:38:40] <cboos_> so it's not loaded for some reason (you can also look in the log, near the beginning,
[03:39:23] <cboos_> there must be something like
[03:39:24] <cboos_> (2784) Trac[Trac Devel:pygments_renderer] DEBUG: Pygments installed? True"
[03:39:25] <mitsuhiko> cboos_: if pygments is installed from source and not from egg it does not appear there
[03:39:43] <cboos_> the above line should
[03:40:00] <coderanger> i have it as false
[03:40:15] * cboos has quit IRC
[03:40:20] <coderanger> pygments is just installed via easy_install
[03:40:25] * cboos_ is now known as cboos
[03:41:00] <cboos> and it does work in trunk?
[03:41:17] <mitsuhiko> cboos: there is/was an imcompatibility
[03:41:20] <coderanger> hmm, haven't tried that
[03:41:22] <mitsuhiko> the lexer functions moved out of pygments.*
[03:41:22] <coderanger> one sec
[03:41:25] <cboos> that would be surprising... there's no big change in blame w.r.t. to that
[03:41:29] <mitsuhiko> they are now in pygments.lexers.*
[03:41:39] <mitsuhiko> but that is/was fixed afair in trac trunk
[03:42:02] <cboos> let me check if that change is also in the blame branch (should be)
[03:42:55] <cboos> from pygments.lexers import get_lexer_by_name
[03:43:03] <cboos> in both trunk and sandbox/blame
[03:44:14] <cboos> mitsuhiko: by the way, it would be cool if there was a way to get the VERSION info directly from the api
[03:44:15] <coderanger> oh jeez
[03:44:19] <coderanger> trunk is even worse
[03:44:26] <coderanger> one sec, ill post screenshots
[03:44:42] <mitsuhiko> cboos: jep. that would be a good thing
[03:44:52] <mitsuhiko> maybe add a __version__ attribute to pygments
[03:44:58] <cboos> mitsuhiko: so that the Pygments version could be seen in system configuration even if not loaded through a plugin
[03:45:07] <cboos> mitsuhiko: right, anything like that ;)
[03:46:06] <cboos> coderanger: better do a svn co ...pygments-0.6... and a setup.py install, would be faster ;)
[03:46:16] <mitsuhiko> cboos: it's already there. since 0.7
[03:46:38] <coderanger> http://coderanger.net/~coderanger/tmp/blamecolor.tiff
[03:46:42] <coderanger> http://coderanger.net/~coderanger/tmp/trunkcolor.tiff
[03:47:43] <coderanger> trunk sees pyments 0.6 as installed
[03:49:10] <cboos> coderanger: you have to upgrade Genshi
[03:49:39] <cboos> there are two problems: 1/ you're running Genshi before r398 or so (don't remember exactly the number)
[03:50:01] <cboos> 2/ in your environment for the blame branch, you can't load the pygments package
[03:50:16] <cboos> 1/ is the reason for the TEXT and START things
[03:50:34] <cboos> 2/ is the reason why you get only TEXT and no START/END in the blame branch
[03:50:54] <cboos> Genshi 0.3.6 works fine for pygments
[03:51:00] * idnar_ has quit IRC
[03:51:03] <cboos> as does latest Genshi trunk
[03:51:10] <cboos> but versions below won't
[03:51:42] <coderanger> okay, trying that
[03:51:50] <coderanger> pypi only has 0.3.3
[03:53:04] <cboos> http://trac.edgewall.org/milestone/0.11#Dependencies (not that the # works actually, 0.10 is sooo under featured ;) )
[03:54:52] <coderanger> how the heck is tracd loading genshi 0.3.3, I just deleted it
[03:56:02] <mitsuhiko> hmm
[03:56:09] <mitsuhiko> utf-8-sig is new in python2.5?
[03:56:38] <cboos> neverheard about that, what should that do?
[03:57:37] <mitsuhiko> cboos: utf-8 decode and strips the stupid byteorder cookie
[03:57:48] <mitsuhiko> >>> "\xef\xbb\xbffoo".decode("utf-8-sig")
[03:57:48] <mitsuhiko> u'foo'
[03:57:54] <mitsuhiko> >>> "\xef\xbb\xbffoo".decode("utf-8")
[03:57:55] <mitsuhiko> u'\ufefffoo'
[03:58:05] <mitsuhiko> or whatever it is
[03:58:25] <cboos> ah, sounds useful ;) why is not that the default...
[03:58:53] <coderanger> okay, highlighting is working again with both blame and trunk (via pygments)
[03:58:54] <mitsuhiko> cboos: i guess it was added in python2.5 and for backwards compatibility they gave it a new name
[03:59:25] <cboos> yes, but I can't imagine why it would be useful to keep the information about the original byteorder...
[04:00:19] <mitsuhiko> i hate endianess
[04:00:20] <cboos> unless the information about the original encoding would be kept as well
[04:00:35] <mitsuhiko> anyone a python ucs2 build here?
[04:00:46] <cboos> me
[04:00:50] <cboos> (windows)
[04:00:54] <mitsuhiko> is u'\ufeff' 1 or 2 chars long?
[04:01:28] <cboos> in utf-8 you mean?
[04:01:30] <cboos> 3
[04:01:45] <cboos> >>> u'\ufeff'.encode('utf-8')
[04:01:46] <cboos> '\xef\xbb\xbf'
[04:01:48] <mitsuhiko> cboos: len(u'\ufeff') gives you three?
[04:01:54] <mitsuhiko> now. as unicode object
[04:02:20] <mitsuhiko> >>> len(u'\ufeff')
[04:02:20] <mitsuhiko> 1
[04:02:23] <cboos> well, as a unicode object, \u<anything> is always 1 ...
[04:02:29] <mitsuhiko> alright
[04:04:23] <mitsuhiko> right 65279 is smaller than 65536 :D
[04:04:35] <coderanger> cboos: Is the age column of the browser supposed to be colored?
[04:06:16] * cboos_ has joined #trac
[04:06:36] <coderanger> cboos_: Connection issues? ;-)
[04:06:59] <mitsuhiko> cboos: alright. utf-8-sig is completely senseless
[04:07:08] <mitsuhiko> it was just used by microsoft for their notepad foobar
[04:09:43] <alect> hi
[04:11:21] <coderanger> alect: alo
[04:20:12] <alect> hihi
[04:20:29] <alect> what exciting things have i missed?!?!
[04:22:25] <alect> ah, resource_map and context_map. whoops
[04:25:34] <alect> where'd cboos go
[04:25:50] * cboos has quit IRC
[04:27:08] <alect> oic
[04:27:26] <alect> r4552 was not an accident :P
[04:28:38] <cboos_> hi alect
[04:28:45] <coderanger> alect: thats what they all say
[04:29:22] <alect> hey cboos :) welcome back from holidays
[04:30:55] <alect> r4557 however, that was just stupidity
[04:33:36] * cboos__ has joined #trac
[04:33:36] * cboos__ is now known as cboos
[04:34:20] <alect> chatting through mozilla eh
[04:35:30] <cboos> well, it's not mozilla's fault, rather the presence of a viruspot / MSN-terminal in my home network ...
[04:35:42] <cboos> I turned that thing off the net for now
[04:36:15] <cboos> and told that girl to do her homework instead ;)
[04:36:31] <alect> aah :)
[04:36:43] <coderanger> bah, who needs homework
[04:38:00] <coderanger> I don't understand why tracd is spawning multiple copies here
[04:38:11] <cboos> -r ?
[04:38:27] <lisppaste5> coderanger pasted "tserver function" at http://paste.lisp.org/display/35113
[04:38:49] <coderanger> after running tserver start, you end up with two tracds for each version
[04:38:56] <coderanger> is -r supposed to do that?
[04:39:05] <cboos> yes
[04:39:28] <cboos> one for watching for code changes and restarting the other, worker one
[04:39:36] <coderanger> ahh, I figured it was a glitch in my code somewhere
[04:39:56] <cboos> (at least that's my superficial understanding of it, the details could be a little different, ask matt_good for the real thing0
[04:39:59] <cboos> thing)
[04:40:37] <coderanger> hrmm, back to the brute force method I suppose
[04:42:59] * ehird has joined #trac
[04:43:06] <ehird> is postgre better supported than mysql on trac?
[04:43:13] <coderanger> yes
[04:43:27] <coderanger> mostly because it is much less dumb
[04:43:51] <cboos> well, I'd also say because none of the core dev really works with mysql
[04:44:21] <cboos> we badly need someone interested in that... dilinger was supposed to do it I think, but he's not that active anymore
[04:44:43] <alect> the blame stuff is cool btw, i checked it out the other day
[04:45:03] <cboos> yes, that's about to be merged now
[04:45:31] <cboos> what do you guys think about the property-renderer stuff?
[04:45:36] <alect> cool
[04:45:56] <alect> the blame overlay should start rendering from the top of the window though, imo
[04:46:01] <coderanger> cboos: From before, is the age column supposed to be colored?
[04:46:17] <cboos> only the text in that column, now
[04:46:21] <coderanger> the differering contrasts make things hard to read
[04:46:36] <cboos> screenshot?
[04:46:52] <coderanger> just a stock system with the age at 4 days
[04:47:13] <cboos> 4 days must be light read...
[04:47:22] <cboos> s/read/red/ sorry
[04:47:22] <coderanger> its pight blue
[04:47:26] <coderanger> er, light
[04:47:44] <cboos> so that must be the oldest stuff in your repo ;)
[04:47:52] <coderanger> its the only stuff
[04:48:22] <cboos> ok, but how's that hard to read?
[04:48:28] <coderanger> but even if it was the oldest, it would be nice if it could be turned off
[04:48:39] <cboos> it can be
[04:48:41] <coderanger> because light blue on light gray is poor contrast
[04:49:09] <coderanger> where?
[04:49:27] <cboos> [browser] color_scale = disabled
[04:49:50] <cboos> wait, let me check, it's too fresh ;)
[04:50:06] <coderanger> cboos: I meant as a user option
[04:50:24] <coderanger> like a checkbox in the header
[04:50:49] <cboos> there are a lots of things from the default config options that should be turned into user options, as a way to override the server defaults
[04:50:56] <cboos> that's another example
[04:51:02] <cboos> should be done in the prefs
[04:51:07] <coderanger> cboos: fair enough
[04:51:28] <cboos> I'm looking for a way to do that automatically, btw
[04:51:52] <cboos> like marking an option as "user overridable", and everything happen automagically :)
[04:51:52] <coderanger> heh, isnt that scheduled for 0.12?
[04:52:09] <cboos> well, that's not scheduled, just an idea so far
[04:53:00] <cboos> but maybe, anyway I don't now much about 0.12, I'm more 0.11 oriented right now :)
[04:53:59] * matt_good_ has quit IRC
[04:54:32] * cboos_ has quit IRC
[04:56:23] * tsb has joined #trac
[05:06:59] <alect> hm
[05:08:35] <cboos> alec, I missed one of your comment above:
[05:08:38] <cboos> "the blame overlay should start rendering from the top of the window though,"
[05:08:50] <cboos> you were talking about the changeset view overlay?
[05:09:34] <alect> yeah
[05:09:58] <cboos> what's wrong with having the changeset displayed next to the line you're looking at?
[05:11:22] <alect> one sec' i'll fire it up
[05:11:33] <cboos> for small changes at least, you get to see what has changed on the right spot, so I think it's rather a feature than an issue ;)
[05:11:56] <alect> i'll take a screenshot
[05:12:55] <alect> http://swapoff.org/files/trac-blame.png
[05:13:18] <alect> not that useful
[05:13:45] <mitsuhiko> hmm. maybe the switch to genshi could introduce a new default theme :D
[05:13:51] <cboos> well, it's up to you to scroll down ;)
[05:13:57] <mitsuhiko> not that i don't like the current one, but i see it every day
[05:14:25] <alect> i don't see the advantage of it myself
[05:14:37] <alect> the highlighted lines show you what changeset you're seeing
[05:14:46] <alect> so placing it potentially off the page doesn't add any value
[05:15:48] <cboos> well, the lines shown in the browser are not all; seeing the diff will show you what was there _before_ the change
[05:16:43] <alect> no no, by "highlighted lines" i just meant that they indicate which lines the changeset is referring to
[05:17:29] <coderanger> cboos: an
[05:17:39] <cboos> well, those show you the lines of that changeset that are /still/ in the file view
[05:17:41] <coderanger> an "X" in the corner of the popup would be nice
[05:17:54] <coderanger> its rather unclear currently how to close it
[05:18:07] <alect> cboos: i know
[05:18:09] <cboos> coderanger: 100% agree, patch welcomed
[05:18:14] <coderanger> might also want to throw in the Draggable plugin and make it moveable
[05:18:44] <cboos> it's sort of movable: if you click on other highlighted lines,
[05:19:02] <cboos> well in their blame cell, it will be repositioned there without being fetched again
[05:19:08] <coderanger> I mean like a normal window, click on the title bar and drag it
[05:19:19] <cboos> that could be useful too, of course
[05:19:32] <coderanger> its a UI paradigm most people will be more familiar with
[05:19:55] <cboos> sure, I just didn't have the energy to code that ;)
[05:20:02] <alect> agreed, that was the first thing i tried when it popped up off the screen :P
[05:20:28] <cboos> it was hard enough to do the blame.js without the jquery doc at hand ;)
[05:20:38] <coderanger> heh
[05:20:48] <coderanger> jquery could use better docs in general
[05:20:50] <alect> it's very cool though
[05:20:57] <alect> extremely useful feature
[05:21:05] <coderanger> yeah, most of my issues are cosmetic details
[05:21:09] <coderanger> the functionality look awesome :)
[05:21:23] <cboos> an extra feature for this is that you can follow the links in the changeset diffs ;)
[05:21:49] <cboos> that will take you to the annotated view starting at the "old" changeset
[05:22:02] <cboos> so that you can "unwind" changes for a given block of code
[05:22:45] <alect> i also like how the textual ages (eg. "1 week") are coloured now
[05:23:22] <cboos> ah, btw, coderanger was complaining about the bad contrast for this, I was waiting for a screenshot...
[05:24:42] <coderanger> http://coderanger.net/~coderanger/tmp/blamecolor.tiff
[05:25:52] * cboos has left #trac
[05:26:02] <alect> !
[05:26:03] * cboos has joined #trac
[05:26:29] * cboos hit the wrong key, with his big fingers
[05:26:33] <alect> hehe
[05:26:34] <alect> smooth
[05:26:42] <cboos> coderanger: that looks fine for me,
[05:26:46] <alect> i have colouring like that too...i don't mind it
[05:26:52] <alect> maybe it's a monitor setting?
[05:27:06] <coderanger> its the only blue text on the screen
[05:27:11] <coderanger> so it just looks weird
[05:27:27] <coderanger> maybe the coloring should be relative to other things in the folders
[05:27:29] * bryanl has joined #trac
[05:27:45] <coderanger> or if nothing else, those should be red because it is the newest stuff inthe repo
[05:31:06] * PingYeh has quit IRC
[05:31:11] * cboos has quit IRC
[05:31:14] * PingYeh has joined #trac
[05:32:32] * cboos__ has joined #trac
[05:32:34] * cboos__ is now known as cboos
[05:33:07] <alect> magic
[05:34:30] <cboos> coderanger: you can easily customize the color scale used, using [browser] oldset_color and [browser] newest_color ... for example, you could use darkgrey for the oldest
[05:34:49] <cboos> [browser] oldset_color = (100, 100, 100)
[05:35:08] <cboos> maybe that'll look better in the browser dir view
[05:35:40] <cboos> matt and jonas seem to think that a color code would be better suited for this, though
[05:36:08] <cboos> that would have the advantage of having a color legend, similar to the one we have for diff colors
[05:36:08] <coderanger> yeah, that looks a bit more natural
[05:36:28] <cboos> I agree this would be better for the browser dir view, but not for the blame
[05:36:38] <cboos> there, I think a color scale is much better
[05:40:15] <cboos> coderanger: now I'm having the same issue with pygments than you had with genshi ;) I keep getting the 0.7dev-r2691 package info, though I've deleted that egg :/
[05:40:18] * asmodai has quit IRC
[05:40:21] * asmodai has joined #trac
[05:40:34] <coderanger> cboos: The problem was not all my tracds were being killed
[05:40:59] <cboos> hm, can't be here (I start it manually)
[05:42:07] <alect> want to see something weird:
[05:42:09] <alect> 2007-01-14 00:37:27,793 Trac[loader] ERROR: Skipping "CherryPy 3.0.0" (version conflict: "(CherryPy 2.2.1 (/usr/lib/python2.4/site-packages/CherryPy-2.2.1-py2.4.egg), Requirement.parse('CherryPy==3.0.0'))")
[05:42:17] <cboos> ...I've simply put the pygments folder in the PYTHONPATH... ah, maybe is reading the Pygments.egg-info folder there...
[05:43:16] <cboos> alect: the message is a bit confusing, right
[05:43:54] <cboos> we should rather say: "Can't load "CherryPy 3.0.0" (version conflict: ...)" in this case
[05:44:18] <alect> why is it trying to load it?
[05:44:38] <cboos> an indirect requirement?
[05:45:35] <cboos> or simply because it's in your easy-install.pth?
[05:47:10] <alect> could be the latter...
[05:48:20] <alect> so what's the opinion on adding WIKI_ATTACH and TICKET_ATTACH?
[05:48:56] <cboos> +1, that's the right thing to do
[05:49:09] <cboos> though we should still support the old options, for backward compat
[05:49:15] <cboos> s/actions/options
[05:49:34] <alect> hmmm
[05:49:45] <cboos> mitsuhiko: http://trac.edgewall.org/changeset/4559 thanks for the tip!
[05:49:46] <coderanger> cboos: Maybe for the 0.11 DB ugrade, prompt them if they want to add the new perms where there are the old ones?
[05:49:49] <alect> i'm not convinced..
[05:50:05] <alect> that would be a good idea
[05:50:12] <cboos> yeah, or do that in an upgrade script
[05:51:12] <cboos> (together with the ROADMAP stuff)
[05:52:47] <cboos> @ticket 3022 in case someone is interested
[05:52:47] <evil_twin> cboos: (ticket <ticket>) -- returns a link to that ticket on the Trac Site
[05:52:55] <cboos> @ticket 3022
[05:52:55] <evil_twin> cboos: http://trac.edgewall.org/ticket/3022
[05:59:38] * chrismir has joined #trac
[06:04:13] * cerw has joined #trac
[06:04:16] <cerw> ello
[06:04:42] <cerw> i am having trouble to get [ticket] restrict_owner =true to work?
[06:04:50] <coderanger> whats not working
[06:05:00] <cerw> there is not SELECT box
[06:05:06] <cerw> still INPUT type=text