tag:blogger.com,1999:blog-6932260.post115342828114983639..comments2023-11-01T00:21:02.380-07:00Comments on Egocity: Developer's Edition: Bazaar-NG'd ProjectsMarkhttp://www.blogger.com/profile/05923388824282852378noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-6932260.post-69364940118804710022023-05-15T20:35:44.193-07:002023-05-15T20:35:44.193-07:00Great bblog I enjoyed readingGreat bblog I enjoyed readingTiago Baciottihttps://medium.com/@tiagobaciottinoreply@blogger.comtag:blogger.com,1999:blog-6932260.post-88121037684777678752006-09-05T17:47:00.000-07:002006-09-05T17:47:00.000-07:00Try running tracd with DEBUG logging and report an...Try running tracd with DEBUG logging and report any errors it finds. Errors about missing roadmap or ticket modules are fine, since I haven't gotten around to writing those yet.Markhttps://www.blogger.com/profile/05923388824282852378noreply@blogger.comtag:blogger.com,1999:blog-6932260.post-30673502878407771142006-09-05T14:15:00.000-07:002006-09-05T14:15:00.000-07:00well OK, that didn't help. I'll let you know how i...well OK, that didn't help. I'll let you know how it goes :)Phil Wilsonhttps://www.blogger.com/profile/16646664352200705164noreply@blogger.comtag:blogger.com,1999:blog-6932260.post-56027756000843503532006-09-05T13:42:00.000-07:002006-09-05T13:42:00.000-07:00Ah yes, I wondered about that, but it's not listed...Ah yes, I wondered about that, but it's not listed on http://staff.washington.edu/marklee/bzrview/ so missed it. I see it's in http://staff.washington.edu/marklee/bzr/atom-python/ so I'll give it a go. Thanks.Phil Wilsonhttps://www.blogger.com/profile/16646664352200705164noreply@blogger.comtag:blogger.com,1999:blog-6932260.post-1157070998916212172006-08-31T17:36:00.000-07:002006-08-31T17:36:00.000-07:00It shouldn't make a difference.Did you pull/instal...It shouldn't make a difference.<BR/>Did you pull/install the atom-python branch? I neglected to mention in my original post that my trac plugin depends on my python module that reads/writes the atom format. It's still a work in progress, but it more or less does the job.Markhttps://www.blogger.com/profile/05923388824282852378noreply@blogger.comtag:blogger.com,1999:blog-6932260.post-1157067649883041192006-08-31T16:40:00.000-07:002006-08-31T16:40:00.000-07:00I'm using 0.10b1.I didn't actually have that line ...I'm using 0.10b1.<BR/><BR/>I didn't actually have that line in my [components] but I do now and it still doesn't work ("No handler matched request to /atom"). I don't need to change anything in [trac] or [project] ? I'm running Trac standalone, although I doubt that makes a difference.<BR/><BR/>If what you say about Trac development is true, then appears to be a royal pain in the ass :)Phil Wilsonhttps://www.blogger.com/profile/16646664352200705164noreply@blogger.comtag:blogger.com,1999:blog-6932260.post-1156983241801905302006-08-30T17:14:00.000-07:002006-08-30T17:14:00.000-07:00Are you using >=0.10dev? Also, have you enabled th...Are you using >=0.10dev? Also, have you enabled the plugin under the [components] heading in /path/to/trac-data/conf/trac.ini ? E.g.,<BR/>[components]<BR/>atompp.* = enabled<BR/><BR/>Personally, I don't really like eggs that much. I can see their use in plugins and such, but it annoys me when trying to debug them. I'm getting really sick of the "# :-)" line...<BR/>For developing with eggs, I just stick with the <A HREF="http://trac.edgewall.org/wiki/TracDev/PluginDevelopment" REL="nofollow">official trac docs</A>. AFAICT, the only way to do trac plugins is via eggs.Markhttps://www.blogger.com/profile/05923388824282852378noreply@blogger.comtag:blogger.com,1999:blog-6932260.post-1156981623433827142006-08-30T16:47:00.000-07:002006-08-30T16:47:00.000-07:00OK, that's what I'd thought, but both a browser re...OK, that's what I'd thought, but both a browser request and a wget to http://example.com/path/to/trac/atom gives me a 404 (which is why I thought I had it wrong).<BR/><BR/>I thought there might have been a permissions issue (with "assert_has_permissions") but I think I've granted this correctly and it still doesn't work. A quick change to return 200 and some text if the permissions check fails, but no dice.<BR/><BR/>At this point, my Trac and Python module knowledge has been pushed to its limit, so I may have to bow out gracefully :)<BR/><BR/>slightly OT: This is the first time I've actually used an egg - is there a standard way of developing using them, or can you make Python look directly at your code? Google doesn't seem to come up with anything short and to the point.Phil Wilsonhttps://www.blogger.com/profile/16646664352200705164noreply@blogger.comtag:blogger.com,1999:blog-6932260.post-1156978986791662492006-08-30T16:03:00.000-07:002006-08-30T16:03:00.000-07:00Given that I tend to code rather abstractly, I can...Given that I tend to code rather abstractly, I can understand why you can't seem to find the endpoint URL. Currently (i.e., the committed code as of this comment), the endpoint (to the introspection document, I assume you mean) is <http://example.com/path/to/trac/atom>. In a future commit (in order to get authentication working correctly without ugly hacks), the endpoint will be <http://example.com/path/to/trac/login/atom>.<BR/><BR/>(BTW, I am rather annoyed by the number of HTML tags that I can't use in comments...)Markhttps://www.blogger.com/profile/05923388824282852378noreply@blogger.comtag:blogger.com,1999:blog-6932260.post-1156976542884060782006-08-30T15:22:00.000-07:002006-08-30T15:22:00.000-07:00This is very interesting. I'm not entirely sure ho...This is very interesting. <BR/><BR/>I'm not entirely sure how the requests are getting to the plugin though - where is the endpoint URL specified?Phil Wilsonhttps://www.blogger.com/profile/16646664352200705164noreply@blogger.com