Re: [tg-trunk] Another suggestion for the Trac migration
Am 05.03.2011 19:43 schrieb Michael Pedersen: I'm not about to leave you alone for it. I'll help. I'll start looking at the 2.x tickets tonight. Does that mean you agree with me that we should start on SF with a clean plate? We could then create these new Allura trackers for TG1 and TG2 already this week and start moving active tickets from Trac there. I did not hear opinions from anybody else, though. So if anybody has objections, please raise them *now* and don't complain later! On another note, we now have 3 different TG2 projects on SourceForge! http://sourceforge.net/p/pylonsproject/tg2/home/ http://sourceforge.net/p/turbogears2/home/ http://sourceforge.net/p/turbogears/home/ If it goes on like that we will create even more confusion than when TG2 moved to Bitbucket. So please, reach an agreement with Mark which is the official one, and delete the other two. -- Christoph -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To post to this group, send email to turbogears-trunk@googlegroups.com. To unsubscribe from this group, send email to turbogears-trunk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
Re: [tg-trunk] Another suggestion for the Trac migration
On Sun, Mar 6, 2011 at 3:21 PM, Christoph Zwerschke c...@online.de wrote: I did not hear opinions from anybody else, though. So if anybody has objections, please raise them *now* and don't complain later! Sounds like a reasonable approach to me. I can help move the open 1.x tickets over to Allura. On another note, we now have 3 different TG2 projects on SourceForge! http://sourceforge.net/p/pylonsproject/tg2/home/ http://sourceforge.net/p/turbogears2/home/ http://sourceforge.net/p/turbogears/home/ This one isn't needed either: https://sourceforge.net/p/pylonsproject/tg1/home/ IMHO, tg 1 2 should be seperate projects on SF, so http://sourceforge.net/p/turbogears/home/ http://sourceforge.net/p/turbogears2/home/ should be kept for their respective use. (Moved from top post): On Sun, Mar 6, 2011 at 8:36 PM, Michael Pedersen m.peder...@icelus.orgwrote: That's where I'm uploading code to, so I'm going to vote for http://sourceforge.net/p/turbogears2/home/ as the ultimate home for TG2. I've not created a TG1 project, as I'm not even a good candidate for discussing who should get access to the repo, never mind doing anything with it. chrisz, faide, carndt, kskuhlman, rejoc, jon, and dbrattli have made commits in the last 2 years should get automatic invites. Also, as BDFL, Mark should have access. Hopefully others will speak up as willing to help maintain 1.x. -Ken -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To post to this group, send email to turbogears-trunk@googlegroups.com. To unsubscribe from this group, send email to turbogears-trunk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
[tg-trunk] tg 2.1+ and nosetests
So, it's taken some doing (thanks to the difficulties imposed by lxml, which I'm now wanting to find a way to get rid of), but I now have the nosetests working almost entirely. I've got one failure, and have to hit the sack before I can figure out the fix. Pasting the output below. Any chance anybody knows/recognizes this failure, and can tell me an easy fix for it? (tg21test)[marvin@mpdev tg2 (development *%)] python setup.py nosetests running nosetests running egg_info writing requirements to TurboGears2.egg-info/requires.txt writing TurboGears2.egg-info/PKG-INFO writing top-level names to TurboGears2.egg-info/top_level.txt writing dependency_links to TurboGears2.egg-info/dependency_links.txt writing entry points to TurboGears2.egg-info/entry_points.txt reading manifest file 'TurboGears2.egg-info/SOURCES.txt' writing manifest file 'TurboGears2.egg-info/SOURCES.txt' running build_ext .F./home/marvin/venvs/tg21test/lib/python2.6/site-packages/Beaker-1.5.2-py2.6.egg/beaker/cache.py:228: DeprecationWarning: Specifying a 'type' and other namespace configuration with cache.get()/put()/etc. is deprecated. Specify 'type' and other namespace configuration to cache_manager.get_cache() and/or the Cache constructor instead. return self._legacy_get_value(key, **kw) . == FAIL: test_304 (tests.test_caching.TestEtagCaching) -- Traceback (most recent call last): File /home/marvin/src/tg2/tests/test_caching.py, line 164, in test_304 assert 304 in resp.status, resp AssertionError: Response: 200 OK Cache-Control: no-cache Content-Type: text/html; charset=utf-8 Etag: foo Pragma: no-cache bar begin captured logging pylons.controllers.util: DEBUG: ETag didn't match, returning response object pylons.controllers.util: DEBUG: ETag didn't match, returning response object - end captured logging - -- Ran 284 tests in 2.118s FAILED (failures=1) (tg21test)[marvin@mpdev tg2 (development *%)] -- Michael J. Pedersen My IM IDs: Jabber/peder...@icelus.tzo.com, ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/pedermj022...@hotmail.com -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To post to this group, send email to turbogears-trunk@googlegroups.com. To unsubscribe from this group, send email to turbogears-trunk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
