Re: [tg-trunk] extract_messages for *.jinja does not work at all.
Am 19.10.2016 um 07:57 schrieb Mingcai SHEN: I finally find the problem after I changed silent to false: Glad you found it. I thought that silent=false was the default in 2.8, but in fact the default didn't change, you need to set it explicitly. -- Chris -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at https://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/d/optout.
Re: [tg-trunk] extract_messages for *.jinja does not work at all.
Am 18.10.2016 um 06:29 schrieb Mingcai SHEN:
I tried both on linux and windows, and they are the same, not text
inside the tags was extracted into pot file. very strange
Problem with virtualenv ?
It should work with virtualenv as well.
Here are the steps you should try:
Create and activate a virtual env, then:
pip install tg.devtools
gearbox quickstart -jnx example
cd example
pip install .
In example/templates/about.jinja,
under {% block contents %} add these lines:
{{ gettext('Hello gettext!') }}
{% trans %}Hello trans!{% endtrans %}
Then run:
python setup.py extract_messages
The output should now contain the line:
"extracting messages from example/templates/about.jinja"
The file example/i18n/example.pot should be created
and should contain these lines taken from about.jinja:
msgid "Hello gettext!"
msgid "Hello trans!"
-- Chris
在 2016年10月17日星期一 UTC+8下午9:39:07，Christoph Zwerschke写道：
Am 17.10.2016 um 14:56 schrieb Mingcai SHEN:
> But it just can extract {% trans %} {% endtrans %} or {{
gettext('') }}
> from the template files into the pot file.
You meant *can't* extract, not *can* extract, right?
I just tried it with a newly created project, and this simple template:
{{ gettext('Hello gettext!') }}
{% trans %}Hello trans!{% endtrans %}
Both texts were copied to the i18n/*.pot file.
I have used Python 2.7, TG 2.3.9, Babel 2.3.4 and Jinja2 2.8.
Are you using any different versions? Also, does it work for you with a
newly created project and the above simple template?
-- Chris
--
You received this message because you are subscribed to the Google Groups
"TurboGears Trunk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to turbogears-trunk+unsubscr...@googlegroups.com.
To post to this group, send email to turbogears-trunk@googlegroups.com.
Visit this group at https://groups.google.com/group/turbogears-trunk.
For more options, visit https://groups.google.com/d/optout.
Re: [tg-trunk] extract_messages for *.jinja does not work at all.
Am 17.10.2016 um 14:56 schrieb Mingcai SHEN:
But it just can extract {% trans %} {% endtrans %} or {{ gettext('') }}
from the template files into the pot file.
You meant *can't* extract, not *can* extract, right?
I just tried it with a newly created project, and this simple template:
{{ gettext('Hello gettext!') }}
{% trans %}Hello trans!{% endtrans %}
Both texts were copied to the i18n/*.pot file.
I have used Python 2.7, TG 2.3.9, Babel 2.3.4 and Jinja2 2.8.
Are you using any different versions? Also, does it work for you with a
newly created project and the above simple template?
-- Chris
--
You received this message because you are subscribed to the Google Groups
"TurboGears Trunk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to turbogears-trunk+unsubscr...@googlegroups.com.
To post to this group, send email to turbogears-trunk@googlegroups.com.
Visit this group at https://groups.google.com/group/turbogears-trunk.
For more options, visit https://groups.google.com/d/optout.
Re: [tg-trunk] extract_messages for *.jinja does not work at all.
Am 13.10.2016 um 15:14 schrieb Mingcai SHEN:
I'm using TG2.3.9 with Jinja2 templates, and when I run "setup.py
extract_messages", it does not extract any strings from jinja files
inside {% trans %} block or {{ gettext('') }} etc...
This should work. Are you sure your templates have the extension
".jinja" (and not ".jinja2" or ".html") and are living in the templates
directory (as specified in setup.py)? Are you sure there is no syntax
error in the jinja template? In Jinja 2.7 errors are silently ignored by
default, so it's recommended to set silent=false or use Jinja 2.8.
-- Chris
--
You received this message because you are subscribed to the Google Groups
"TurboGears Trunk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to turbogears-trunk+unsubscr...@googlegroups.com.
To post to this group, send email to turbogears-trunk@googlegroups.com.
Visit this group at https://groups.google.com/group/turbogears-trunk.
For more options, visit https://groups.google.com/d/optout.
Re: [tg-trunk] Supported Versions?
Am 26.04.2016 um 09:41 schrieb Alessandro Molina: I have not used TW1 for years and was planning to remove it from 2.4, it seems to me it's currently unmaintained so keeping it around is probably an huge burden :D It's a bit difficult to migrate from TW1 to TW2 though. I still have one legacy TG2/Python2 app making extensive use of TW1 where I upgraded TG2 but didn't find the time and energy to upgrade to TW2. -- Chris -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at https://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/d/optout.
Re: [tg-trunk] Future of Genshi
Am 18.02.2015 um 10:15 schrieb Alessandro Molina: I'm writing here because I'm fearing we will have to make a clear step regarding genshi in the near future. So I would like to gather as much opinions as possible regarding the matter. First of all, it's very sad that Genshi has stalled. The idea behind it (actually copied from Kid) was brilliant, particularly at that time when XHTML was all the rage. Now with HTML5 the use of XML has become a bit less interesting. But Genshi worked still quite well for me as a successor of Kid. Unfortunately, I can't give feedback regarding Kajiki, since I haven't used it so far. It doesn't seem very active either, and doesn't seem to have many users, so there may be lingering problems that nobody noticed so far. The CDATA bug you mentioned is still not fixed, either. TW2 compatibility is very important. It seems your argument is that Kajiki can be easier forked and/or maintained as part of the TurboGears project, because it's less complex, do I understand it correctly? -- Christoph -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/d/optout.
Re: [tg-trunk] Tests for tg2devtools
Am 25.06.2013 00:29, schrieb Alessandro Molina: Ok, finally found the reason. While on more recent versions the output for subtests is: tgtest00.tests.functional.test_authentication.TestAuthentication.test_forced_login Anonymous users are forced to login ... ok On Python2.6 the class path is missing: Anonymous users are forced to login ... ok Right, I remember. Unittest had the annoying feature of only showing the docstring before this was fixed in Py 2.7 with unittest2. It is actually possible to change the output by adding a method shortDescription() to the test class. But this only works if the test class derives from unittest.TestCase. -- Christoph -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/groups/opt_out.
[tg-trunk] Using relative names in quickstarted templates
It sometimes bothers me how often the package name of a TG project is repeated in a controller module, both in import statements like from mylongpackagename.model import MyModelClass and in expose decorators like @expose(mylongpackagename.templates.mypage). So I thought about changing the quickstart templates to use relative imports, but I found two problems: 1) Relative imports do not work for Genshi (generally dotted notation) in @expose any more (they used to work in TG1), so we would first need to add that feature back. 2) I read e.g. in PEP8 that relative imports are considered bad practice, not only the old implicit relative imports (which is obvious), but even the newer explicit relative imports. Unfortunately no rationale is given, I can only guess that it's about explicit better than implicit (since explicit relative imports are only explicit about being relative, the location is still implicit). I'm not sure whether explicit better than implicit overtrumps DRY here. And I don't understand why explicit relative imports have been introduced in Python 2 and not been removed from Python 3 if they are really so bad. Opinions? -- Christoph -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/groups/opt_out.
Re: [tg-trunk] Tests for tg2devtools
Am 24.06.2013 18:18, schrieb Alessandro Molina: I made some advancements on the testsuite and now is able to pass on Py2.7 on travis: https://travis-ci.org/TurboGears/tg2devtools/builds/8390939 Great. I tried it under Windows and fixed a small issue. Another problem is that some packages like Genshi are not available as binaries or only available as 32bit version and will not install on Windows unless you have installed a suitable Visual Studio version. And of course, running the test suite is now very slow since all this stuff is now loaded from the Internet every time, which is awful if you have a slow connection. There should be an option to run the tests without virtualenvs or with --system-site-packages so nothing needs to be installed when everything is already available on the system. -- Christoph -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/groups/opt_out.
Re: [tg-trunk] Tests for tg2devtools
Am 23.06.2013 14:51, schrieb Alessandro Molina: The most simple solution would be to specify all the dependencies in tests_require of devtools, but I don't think this is the right solution, the tests should probably install the dependencies depending on the quickstarted app. But then BaseTestQuickStart must also create and destroy a separate virtualenv in its setUp and tearDown methods. By the way, I think it's better to use setUpClass and tearDownClass in this case, creating the environments and quickstarting the project for every test seems overkill to me. -- Christoph -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/groups/opt_out.
Re: [tg-trunk] Tests for tg2devtools
Am 21.06.2013 15:12, schrieb Alessandro Molina: 2) What to do on Py3, the current travis env for TG2.3 tests on Py26, 27, 32, 33. But some of the quickstarts don't work on Py3 due to missing libraries (ming, sprox, tgext.admin mostly). What should we test? Should gearbox quickstart create the project anyway or should it raise an error like --ming not supported on py3? Or should we just SKIP the tests in tg2devtools on py3? I would just skip them, since as long the quickstarted project doesn't work anyway, we don't need to care. -- Christoph -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/groups/opt_out.
Re: [tg-trunk] Tests for tg2devtools
Am 20.06.2013 00:06, schrieb Alessandro Molina: Maybe someone more proficient in nose knows a better way to run the tests of the generated application from inside the testsuite, right now it loads them with nose.run which makes the whole testsuite result as a single test. I found that nose.run() did not run properly. There were several problems: argv[0] must be the command name, the egg_info must be generated first, and it had also issues with output redirection. So I solved it differently, by running setup.py test for the quickstarted project in a subprocess and checking the output. This has the advantage that TG can switch to any other test runner like nose2 and nothing has to be adapted in this test. The improved test_quickstart found a failing test with Mako on Windows due to different linefeeds that would otherwise have gone unnoticed. We should now also add a Travis service hook for tg2devtools. -- Christoph -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/groups/opt_out.
Re: [tg-trunk] Another problem with tests in TG 2.3
Am 19.06.2013 00:27, schrieb Craig Small: Oh, I thought that was done on purpose. I hit that problem when testing things outside the controllers that need models to operate. I basically copied some of the code across to make my own setup but fixing it right would be a better idea. It is fixed in the development branch now. -- Christoph -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/groups/opt_out.
Re: [tg-trunk] Tests for tg2devtools
Am 20.06.2013 00:06, schrieb Alessandro Molina: I tried to implement a more flexible test suite for quickstart, it now runs the quickstart with different options trying to run the test suite for each one of them. You beat me to it, I wanted to do in a similar way. Maybe someone more proficient in nose knows a better way to run the tests of the generated application from inside the testsuite, right now it loads them with nose.run which makes the whole testsuite result as a single test. Yes, that's not so meaningful. The test should check how many tests were run (should be different depending on quickstart options) and whether at least one test was created and run at all. We could give nose2 a try, it doesn't have the run() method but something like discover(exit=False) should do. I'll look into that tomorrow unless you beat me to it again. -- Christoph -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/groups/opt_out.
[tg-trunk] Use nose2 for TG 2.3
Since TG 2.3 requires Py 2.6 already, this would be a good opportunity to move from nose to nose2. What do you think? -- Christoph -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/groups/opt_out.
[tg-trunk] Another problem with tests in TG 2.3
I found another problem when running tests for a quickstarted project with SQLAlchemy: The test application is only loaded in TestController.setUp() which is only run when the test methods in tests/functional run. When you run only the tests in tests/model, then the application is not loaded, the config is empty and setup_db will throw an error. I guess this problem has not been noticed in TG 2.2 because when you run the complete test suite, tests/functional runs before tests/model, so everything is fine, and additionally the nose plugin that was included in Pylons made sure that the configuration was loaded before running the tests. Since we do not use that plugin any more in TG 2.3, we should be more careful about the proper setup. I'll refactor the test templates a bit today to make the setup process cleaner. -- Christoph -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/groups/opt_out.
Re: [tg-trunk] Another problem with tests in TG 2.3
Am 18.06.2013 20:39, schrieb Jorge Vargas: That's what the other tests you found broken were supposed to prevent Yes, I'll try to create a replacement for these as well. -- Christoph -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/groups/opt_out.
Re: [tg-trunk] Problem with TG functional tests
Just noticed that the patch for supporting a 'default' authenticator entry, which was the main problem why the test failed, has not been backported to 2.2 anyway, so it does not make much sense to backport this fix either. I only noticed it because I used a patched version of 2.2 with 'default' authenticator support. But I'll upgrade to 2.3 now. -- Christoph -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/groups/opt_out.
[tg-trunk] Tests for tg2devtools
In devtools.test there is a test_pastetemplate which is broken in 2.3 because devtools.pastetemplate does not exist any more. Are there plans to add tests to devtools again before 2.3 is out? -- Christoph -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/groups/opt_out.
Re: [tg-trunk] Problem with TG functional tests
Am 14.06.2013 10:30, schrieb Alessandro Molina:
https://github.com/TurboGears/tg2/commit/1c4da8da9fc5bc85023645b72f906d8c3132fc97#L1R888
should fix the issue. It looks like it was introduced by the
('default', None) authenticator feature that changed the original
list of authenticators in the case both the default and custom
authenticators were defined.
Nice, thanks for looking into this. I'd like to backport the fix to the
2.2 branch, is that ok?
-- Christopg
--
You received this message because you are subscribed to the Google Groups
TurboGears Trunk group.
To unsubscribe from this group and stop receiving emails from it, send an email
to turbogears-trunk+unsubscr...@googlegroups.com.
To post to this group, send email to turbogears-trunk@googlegroups.com.
Visit this group at http://groups.google.com/group/turbogears-trunk.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [tg-trunk] Problem with TG functional tests
Am 14.06.2013 16:03, schrieb Alessandro Molina: Thanks, will update it soon, did the patch work for you? Haven't tried it, since my projects are still using TG 2.2. -- Christoph -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/groups/opt_out.
Re: [tg-trunk] Re: TG Website redesign proposal
Nice. I also liked the gears in the background of the old version, but the new version looks cleaner and more modern without them. Everyone likes flat and simple design these days. -- Christoph Am 13.06.2013 15:16, schrieb Alessandro Molina: Added responsive breakpoints to make it also visible on mobile devices, if everyone is fine with it I would deploy this evening Bests, Alessandro -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[tg-trunk] Problem with TG functional tests
I have just run into an ugly problem with TG 2.2.2 that you can
reproduce as follows:
* Quickstart a project
* Set in config/app_cfg.py:
base_config.sa_auth.authenticators = [('default', None)]
* Run paster setup-app
* Run nosestests
You get this error:
app = setup_auth(app, skip_authentication=skip_authentication,
**auth_args)
File ...\tg\configuration\auth.py, line 227, in setup_auth
return _AuthenticationForgerMiddleware(app, **who_args)
TypeError: __init__() got an unexpected keyword argument 'dbsession'
I think the problem is this:
When running the test, the app is configured with the same config object
multiple times. In the first run, in add_auth_middleware, the sqlauth
authenticator is created using create_default_authenticator(). In this
process, the dbsession parameter is removed from auth_args.
However, in the second run, the sqlauth authenticator is already setup
in the configuration, create_default_authenticator() will not be
executed, the dbsession parameter is not removed, and finally the
_AuthenticationForgerMiddleware will be called with that parameter which
it does not want to have.
The easiest way to fix this is to let _AuthenticationForgerMiddleware
ignore superfluous arguments. Any better ideas?
-- Christoph
--
You received this message because you are subscribed to the Google Groups
TurboGears Trunk group.
To unsubscribe from this group and stop receiving emails from it, send an email
to turbogears-trunk+unsubscr...@googlegroups.com.
To post to this group, send email to turbogears-trunk@googlegroups.com.
Visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [tg-trunk] Re: Repository Combining Idea
Am 25.04.2013 04:46, schrieb Michael Pedersen: Is everybody okay with simply not having tags in the tg2docs repository? But doesn't rtfd.org create the various versions of the docs based on tags in the repository? -- Chris -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [tg-trunk] Re: Repository Combining Idea
Am 25.04.2013 18:52, schrieb Michael Pedersen: If it does, then why not combine everything down into one repository? As for size, we'd be creating a single repository that's about 24M to download/clone/search. For point of reference, the actual repository for tg2 is 7.1M, tg2devtools is 3.1M, and tg2docs is 13.6M (according to a du I just did on them). The additional size is not excessive, searching is not going to be appreciably longer, and releases/tags will be simpler to manage. Everything for tg2 will be under one umbrella. I'm really failing to see an issue with this. I get different numbers: On disc: 4MB for tg, 2MB for tgdev, 39MB for tgdocs, Via network: 2.5MB for tg, 0.8MB for tgdev, 10.5MB for tgdocs That's a large overhead when the docs are always included. Also, if somebody wants to add complete zipped tutorials with source code, images or even screencasts and videos to the docs (we had these in the tg1 docs), then they will grow even larger. Concerning tgdev, if we add larger front-end frameworks with JavaScript libraries and themes as optional quickstart templates, and these are regularly updated, it may become larger as well. Some workflows for deploying or testing require cloning the tg repository which will then take time over slow networks. For instance, our travis build clones the repo after every push to the repo. -- Christoph -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscr...@googlegroups.com. To post to this group, send email to turbogears-trunk@googlegroups.com. Visit this group at http://groups.google.com/group/turbogears-trunk?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [tg-trunk] Re: 2.3 doc review
Am 07.01.2013 12:47, schrieb Alessandro Molina: Also open to suggestions, I agree that the current theme is a bit depressing for the color scheme :D What else do you expect when you let a German create the theme? ;) -- 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] 1.0/1.1/1.5 Docs
Am 05.01.2013 21:02, schrieb Michael Pedersen: Hey, Christoph? Since you're the one who knows the most about this, I'll ask you: How does one generate the docs for TG 1.0, 1,1, and 1.5? I'm working on a site rebuilding script/tool that I want to have those be part of the process it runs. Since I'm focused on the 2.x line right now, I figured you'd be the best choice for how to find out what I need for 1.x. Hi Michael, there is a script for creating the docs, you run it with sudo -u turbogearsorg ~turbogearsorg/bin/make_docs 1.0 Replace 1.0 with 1.5 to create the docs for TG 1.5. There is also script to create the API docs sudo -u turbogearsorg ~turbogearsorg/bin/make_api_docs 1.0 Haven't used these for a long time. If things do not work properly any more and you need help, let me know. -- 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] 2.3 doc review
Nice, thanks! Minor issue: in the TG 2.1 and 2.2 version of the docs, you could move the sidebar to the right side by grabbing the handle and it would stay there (via cookie). This doesn't seem to work any more in 2.3. -- Chris -- 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] Translation of TW2 messages
Am 03.10.2012 11:25, schrieb Alessandro Molina: That's a great work, I ended up having the same issue but I solved it by handling the translation inside my own application, your solution is much more convenient. Ok, so I sent a pull request to get in TW2. Maybe you can then add the Italian translations. -- 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.
[tg-trunk] Translation of TW2 messages
After replacing FormEncode validators with TW2 validators in a TG2 app I found that the validator messages were not translated any more. I'm proposing the patch at https://github.com/toscawidgets/tw2.core/issues/55 to solve this problem, please let me know what you think. Maybe we could also use the same method for FormEncode, I find the currently used method of translating FormEncode messages too intricate. -- 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.
[tg-trunk] Re: Switching To GitHub
Just want to point out that the move to GitHub has some other positive side-effects. For instance, GitHub makes it much easier for people to fork TurboGears and send in pull requests. Another advantage is that you can connect to the Github issues from Eclipse/Mylyn, for those who are using PyDev. If you haven't checked out the PyDev+Mylyn combination, I encourage you to do so, it's really useful and fun to work with. -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To view this discussion on the web visit https://groups.google.com/d/msg/turbogears-trunk/-/N77a4J-TrXoJ. 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] TurboGears 2.2 and authentication
Am 19.09.2012 05:56, schrieb Michael Pedersen: No need to wait even. The repositories will be copied wholesale, so the push can be done whenever. Ok, I'll only have time next week anyway. Will check that in to the development branch then and merge it back to the branch-2.2 so it will go to 2.2.1. -- 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.
[tg-trunk] TurboGears 2.2 and authentication
While upgrading a project from TG 2.1 to 2.2 I noticed that the
authenticators setting (a list of custom authenticators) is handled
differently depending on whether authmetadata is defined (new-style
config) or not (old style).
In new-style configuration, the default authenticator will not be used
at all when custom authenticators are specified, while in old-style
configuration, the default authenticator will be appended.
I think we should re-establish the old behavior. It often makes sense to
prepend additional authenticators to the default one. Of course, you can
always add the default one manually, but it's cumbersome.
Or, we could make it even more flexible by allowing a value of
('default', None) in the authenticators list which will be
automatically replaced by the default authenticator. That way you can
specify exactly the position of the authenticator in the chain. I have
already created a patch for this, let me know what you think.
-- 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] Switching To GitHub
Am 10.09.2012 17:11, schrieb Christophe de Vienne: Have you considered bitbucket too ? IIRC the tg repositories were once hosted there, and it has the same avantages over SF (the ones you mention at least). That would mean switching from git back to hg again. Much easier to stay with git. It's bad enough that we have to change our project platform again, but at least please let's not change the VCS type and convert the repository again! Also, I remember there was a long discussion where some developers had issues with both bitbucket and hg, and wanted to use git instead. Not sure if these were real issues, or if they are solved now, but that's actually why we moved away from bitbucket. If we move, we should at least not move in circles. -- 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] Switching To GitHub
Am 10.09.2012 20:45, schrieb Kevin Horn: FYI, bitbucket supports git repos now, as well as hg ones. Thanks for the update, that move had indeed slipped under my radar. -- Chris -- 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] Where to report web page and documentation inconsistencies
Am 12.07.2012 15:08, schrieb Eoghan Murray: The SourceForge signup process is heavy handed enough to have turned me away from submitting a simple documentation fix. You don't even need to register, you can login with OpenID using your Google account and a couple of others. -- 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] Where to report web page and documentation inconsistencies
Am 12.07.2012 21:05, schrieb Eoghan Murray: I was able to create that SourceForge user from scratch. I can't find a repository for TurboGears 1.5 though The repository is here: https://sourceforge.net/p/turbogears1/code/ If you want to write a page about TurboMail and how it can be used with TurboGears 1.5, feel free to do so and post it here or as a ticket. This is how I updated my turbomail settings from 1.0 to 1.5: I think these changes are only necessary when updating to a newer TurboMail version, they are not related to the TG upgrade itself. -- 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] Re: State of the Gears
Am 08.07.2012 21:20, schrieb Alessandro Molina: Now I don't see any point in bringing it up again, especially considering that the 2.3 pylons less branch has been already under development for 6 months, is now able to serve TurboGears applications three times faster without any required change, works on Python3 and has 1/3 of the dependencies we previously had. That doesn't mean that TurboGears can't work with the Pyramid team, we are in 2012 and most of the web frameworks are now build by many independent modules that provide some kind of feature to the framework. We will continue to share WebOb, Baker, WebHelpers, most of the repoze stack and many other things. It's just a matter of would you like to replace 400 lines of custom code with a library thousands of lines big that won't do anything new and you will probably have to monkeypatch deeply like it happened with Pylons?. TurboGears already broke code of its past users too many times and doing it again would probably hurt the project a lot more than not having written on our homepage that we are whatever underlying framework based. Agree with all points. Actually Pyramid is not such a huge library, it's still pretty lightweight. Nevertheless, the core Pyramid docs is already a 700 pages PDF file. People would have to use a framework where they don't understand what's going on in the lower levels or they would have to read these 700 pages just to understand the lower levels. Also, if TG would make another radical change now, we would again come into the situation where people start asking shall I use TG2 now or shall I wait for when TG3 based on Pyramid appears, and start wondering whether they will be able to migrate their TG2 apps. And then, the documentation would need to be adapted again etc. Lastly, everything also depends on the time and energy the core developers have at hand, and that is very limited. Mark, who orginally came up with the plan of a merge, wasn't able to spend time for the project any more. Currently only Alessandro and Michael are actively working on the project. Maintaining what we currently and developing that slowly and carefully is already enough work. I think they're doing a good job, and I like that TG2 is moving more steadily now and less jumping around with new ideas and changes every other week. -- 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] Where is latest documentation location?
Am Freitag, 6. Juli 2012 04:59:57 UTC+2 schrieb Michael Pedersen: Allow me to apologize for not getting this done sooner. It's been a very busy week for me (just started a new job, and there's all the joys of settling in at a new job work that needs doing). Anyway, the problem turns out to be that I missed a merge step in my process (which is a big part of why I'm trying to automate the entire thing). This is now fixed, and the docs for 2.2 are actually 2.2 docs. Thanks, the 2.2 docs now appear as 2.2.0rc2, but the 2.1 docs (which are linked on the home page) appear as 2.2.0rc1 which is confusing. -- Chris -- You received this message because you are subscribed to the Google Groups TurboGears Trunk group. To view this discussion on the web visit https://groups.google.com/d/msg/turbogears-trunk/-/Lr3aH-FN3dUJ. 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] TurboGears 2 doc issues
When I go to http://www.turbogears.org/2.1/docs/, it says TG 2.2.0rc1 docs in the upper left corner. When I go to http://www.turbogears.org/2.2/docs/, it also says TG 2.2.0rc1 docs but the start page is different. When I click on Getting started, both docs talk about TG 2.1.5. Pretty confusing. -- 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] Jinja Problems
Am 20.04.2012 10:34, schrieb Alessandro Molina: Sorry, my fault. I forgot to rename the templates in the test suite. The strange thing is that I didn't receive any email fron jenkins reporting the failed builds. See the console output: Sending e-mails to: turbogears-trunk@googlegroups.com ERROR: Invalid Addresses ... Caused by: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.7.1 turbogears-trunk@googlegroups.com: Relay access denied Looks like we need to configure Jenkins with a different mail server as the current one does not replay any more. -- 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] 2.2 updates
Am 25.03.2012 23:06, schrieb Alessandro Molina: As I'm getting near the end of the targets that got decided for 2.2 release during the last meeting, I decided to write here to update the other development team members of the current status and ask some help with testing. We decided to require Py 2.5-2.7 for TG 2.2. So we need to adapt Jenkins to test against Py 2.5 instead of Py 2.4 and against Py 2.7 instead of/in addition to Py 2.6. We can then also modernize the code a bit to make use of Py 2.5 (http://docs.python.org/whatsnew/2.5.html). TG 2.1.x should stay compatible with Py 2.4. I'll try to help if I find some time. Thanks for all the great work in the last months. -- 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] Disabling routes by default in TG2.2/2.3
Am 29.02.2012 12:52, schrieb Alessandro Molina: As routes is performed for each request is a performance bottleneck for no benefit in 99% of TG projects, so it is probably fine to disable it and require an enable_routes=True option in app_cfg to enable it again. It would require little effort for people that use it to get it back and it would avoid getting between people that don't use it speeding up the routing process by default. +1 -- 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] Style guidelines (was: Making a 2.1.5 bugfix release?)
Am 25.02.2012 16:53, schrieb Alessandro Molina: Merging the branch made me notice just one issue, for future commits please remember to split feature/bugfix commits from pure syntax rearrangement/cleanup ones. You're right, clean-up work should be done in separate commits. I'm particularly guilty of this. Whenever I see a PEP8 warning anywhere in my IDE, I immediately feel compelled to fix it, along with the real bugfix I'm just working at, and then check in everything together. That's a bad habit of mine, I'll try to improve in this regard. Also do we really want to enforce 80 cols PEP8 limit? I usually find impossible to read 80cols python code and nowadays it is usually possible to put two windows side by side even with a 110/120cols limit. If you prefer to strictly follow PEP8 I'll adapt, but I really think that the 80cols limit hurts a lot readability. I think it's still useful as it's not only about screen size but also about readbility (see http://stackoverflow.com/questions/746853/the-80-column-limit-still-useful). Since Python does not use such long namespaced class names as Java, it is rare that lines are longer than 80 chars and I think it looks odd when in 100 lines 1 line sticks out. Also, long lines often have a code smell (long methods with conditional complexity, too many parameters, excessively long identifiers). So I think the 80 col limit in PEP8 still makes sense. But this is mainly a matter of taste. Officially, we already relaxed that rule (http://turbogears.org/2.1/docs/main/Contributing.html), I just forgot about it. It may help if we check in a .pylintrc file with e.g. max-line-length=120 and other relaxiations we like. Then all contributors can point their IDEs to this .pylintrc file, and we don't see the warnings we don't want to care about. There are some other things that are not regulated by PEP8 and therefore are somtimes changed back and forth when different contributors prefer different styles. We should decide on one style, and document it on the page mentioned above. E.g. we should decide how to format continuation lines. One style is this: def long_function_name( long_parameter_name, another_long_parameter_name): do_something() Another one is this: def long_function_name(long_parameter_name, another_long_parameter_name): do_something() Both are PEP8ish. I prefer the former, as I generally try to avoid formatting that only makes sense with monospaced chars. While I'm at it, we should also add more and better docstrings, and enforce PEP257 in addition to PEP8: One-line: def rand_bar(foo): Randomize the bar of a foo object. Multi-line: def rand_bar(foo): Randomize the bar of a foo object. Foo must be None, in which case we do nothing, or a Foo instance with a bar property. Another thing that will help is when everybody checks in with trailing whitespace stripped. I hate it when I make a small fix and then in the diff I see hundreds of lines changed because blanks have been removed at line ends by my editor. We could also use a commit hook for that. -- 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.
[tg-trunk] Problem installing older TG2 versions
On the tg-users mailing list the problem came up that it seems to be impossible to easy_install non-current TG2 versions even though we have set up special download indexes for these, because the dependency_links setting points to the current index and overrides the -i option of easy_install. Any ideas how to solve this? Should we re-package the old archives in the download sections with proper dependency_links? See here for the original thread: http://groups.google.com/group/turbogears/browse_thread/thread/c94928c51e3c67cd/0ad14f6b843e7aac -- 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] What should we do with Dojo?
Am 24.02.2012 05:34, schrieb Michael Pedersen: I have no object to providing ways to use Bootstrap, especially if it's just a set of jQuery plugins. From reading a (very) little about it, though, it looks like it might be an alternative, instead, and that I'll have issues with providing in the defaults. Provide a way to use it, but just don't make it the default. The HTML and CSS files of Bootstrap can be used without the jQuery Plugins. They could be used instead of our current quickstart templates. The jQuery plugins are only an addition to that, I understand them as an alternative to jQuery UI. In think we have decided to support jQuery as default JS library, but jQuery itself provides no widgets. jQuery UI would be a natural choice, but it's a bit limited and developing slowly. Bootstrap plugins are an alternative, also jQuery Tools, Kendo UI, Ninja UI (all jQuery based). -- 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] What should we do with Dojo?
Am 23.02.2012 04:29, schrieb Michael Pedersen: At this point in web land, jQuery seems to rule the roost, and I'd like to make that the default choice that we tell people to use, and provide ways to use the others. I think that boils down to that somebody needs to bring tw2.jquery back into shape. Another idea would be to make use of Bootstrap (for http://twitter.github.com/bootstrap/) - it could be included as part of the default quickstart app and/or its jQuery plugins could be provided through a tw2.bootstrap as an alternative to jquery.ui. -- 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] Making a 2.1.5 bugfix release?
Am 23.02.2012 05:29, schrieb Michael Pedersen: The only issue I have with anything is the seeming belief that we need a special branch for the 2.1 line. We really don't. We do our planned next release work on development. When we have to do a bug-fix release, we branch from the tag that had the bug, fix there, and merge as appropriate. That would still a special branch, even when made only at relase time. I think it's better to have an branch existing all the time, and whenever we feel a bug needs to be backported, we can add it to that branch at any time, without immediately making a bugfix release. In this case, we'll branch from 2.1.4, cherrypick the commits we need from development, and create the 2.1.5 tag from that. In the process, we'll also probably have to update jenkins a bit, but that's livable. Btw, are Py 2.5 and Py 2.7 available on that server? -- 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] Making a 2.1.5 bugfix release?
Am 22.02.2012 10:37, schrieb Alessandro Molina: Anyone is against to this? Is there any reason for not doing this? We always made bugfix releases for older branches in the past, that's a good practice. Also the 2.1 branch is important since we recently decided it's the last one that provides Python 2.4 compatibility. -- 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] Suggestion to make Chuck Norris happy again
Ok, I have now added download directories development and next for the corresponding branches in our Git repository. The development directory contains the Crank package which made Chuck really happy. Is the development branch supposed to work with Python 2.4? There are two issues that currently break it, namely jinja_lookup (which I fixed already) and Crank which also may be easily fixable but I haven't looked at it yet. -- 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] Suggestion to make Chuck Norris happy again
Am 16.02.2012 20:15, schrieb Alessandro Molina: I remember Python2.4 support being dropped with the last release. Michael can probably confirm this as I remember him adding version check inside the TG source code. There is only a version check that allows Py2.4 to work by adding pysqlite and hashlib. We could remove this and simplify other code when we really want to drop Py2.4. We should then also make Jenkins test with Py2.5 and 2.7 instead of 2.4 and 2.6. I'm currently a bit confused about our roadmap and which branch will become which version. Is there a protocol of our decisions in January? -- 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] Suggestion to make Chuck Norris happy again
Am 16.02.2012 20:45, schrieb Alessandro Molina: I'm currently managing work this way: development branch - 2.2 pylons-less branch - 2.3 python3 branch - whatever will be after that And the next branch is for the next 2.1.x bugfix release, right? -- 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] Suggestion to make Chuck Norris happy again
Am 16.02.2012 23:20, schrieb Alessandro Molina: Actually I always thought that the next branch was only for release process like stated on http://www.turbogears.org/book/appendices/preprelease.html#finalizing-changes-on-next-branch Makes sense, then this is only intended as a temporary branch. I always used the development branch for bugfixes that should have gone in the next to come release. But if that next release will be 2.2 and we later want to release a 2.1.5 bugfix we should also have a separate 2.1 branch (which still supports Py2.4 and works without Crank). Since the development branch has already progressed to Crank, we need to create the 2.1 branch from the masteror the last next branch. There is already a brach-2.0. -- 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.
[tg-trunk] Suggestion to make Chuck Norris happy again
The TG 2.1 tests on the Jenkins server are currently failing and Chuck Norris really does not like it. It looks like this is caused by the fact that we now use Crank which is missing in the current index. This also reveals an issue with the test setup in general. The Jenkins script is installing the dependencies from http://tg.tgy/current/index/. To do it properly we should add another directory /next/ parallel to /current/ on the TG server. In the beginning, /next/ should be a copy of /current/. When we update or add to our requirements, the packages in /next/ should be adapted, e.g. put Crank in here or a newer version of WebOb. The tests setup should then install from /next/ and at the time we create a new release we already have our packages ready and just need to rename /next/ to /current/. -- 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] Re: Experimental Pylons-less branch
Am 12.12.2011 00:20, schrieb Alessandro Molina: Now pylons-less branch passes all the tests both with and without pylons installed and is now a bit faster than the pylons based branch. Congratulations! This is really a big step forward. Did you run some real-life TG apps with that branch? Unfortunately, our test suite is not very comprehensive, so we should test this with some of our apps and add more unit tests if we notice any problems. Hope I can find some time over the holidays for giving this a try. -- 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] Few questions about new release
Am 05.12.2011 11:55, schrieb Alessandro Molina: I was thinking about the idea of having a bunch of fake packages like tgproject-sqla, tgproject-ming and so on so that people can place as a dependency for their project in setup.py. Having tgproject-sqla==2.1.1 would provide all the right packages when they run setup.py instead of having to specify one by one the required packages. This also helps us when we want to change pieces of TG that are provided by the quickstart template and makes easier to upgrade a project to a new version of TG as it would be possible to just change the version number of that package instead of having to look around for the version to use for each and every package. What do you guys think about this? My gut feeling is that this will make the confusion even greater. We have too many small packages with little functionality already, and then we would even have some with no functionality. Also, as we faced a few issues with dependencies I was considering if it might not help improving the experience of users having the precise version specified for all the dependencies inside the TG package. This is actually more difficult for us to maintain, but should totally remove the need for the local index and should avoid future issues like the webob one. That local index has not only the advantage of offering the right versions, but it can also offer additional packages (like compiled eggs for Windows) that are not available in the original locations, and it also serves as a backup and archive when the original locations are down or older packages have been removed. Does anyone know if there is any known issue for TG with SQLA0.7? Haven't noticed any problems so far. -- 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] Few questions about new release
Am 05.12.2011 15:03, schrieb Alessandro Molina: Any other idea on how to avoid people having to manage a hube bunch of packages they really don't care about? We could add upper limits to the version numbers in addition to the lower limits. Sure, in reality, even slight changes can break a TG project. For instance, I found some of my apps were broken when updating repoze.who.plugins.sa from 1.0rc2 to 1.0 (http://github.com/repoze/repoze.who-sqlalchemy/issues/1) and it took me quite some time to identify the cause. Some small changes can have a big effect. Can we keep both available? The local index and the precise version? So that both ways work. That would be an option. One problem is that we must differentiate between the requirements of TG itself and the requirements of the TG project. The former are maintained by us, the latter by the project maintainer. And the more restrictions we have, the easier they can get at odds with each other when updating TG. -- 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.
[tg-trunk] [ANN] TurboGears 1.5.1 released
On behalf of the TurboGears Team, I am pleased to announce that TurboGears 1.5.1 is now available for download. Instructions for downloading and installing are at http://www.turbogears.org/1.5/docs/Install.html Changelog and upgrade instructions are available via http://www.turbogears.org/1.5/docs/WhatsNew.html We enabled and tested some new performant ways of running TurboGears 1.5 behind WSGI enabled web servers, as explained here: http://www.turbogears.org/1.5/docs/Deploy/ We recommend upgrading older TurboGears 1.x versions to 1.5 which is usually much easier than upgrading to 2.x. New TurboGears projects should start with TurboGears 2 which is the current, actively maintained variant of the TurboGears web-framework, based on Pylons instead of CherryPy. Have fun with TurboGears and let us know if there are any problems. -- Christoph Zwerschke -- 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] [ANN] TurboGears 1.5.1 released
On behalf of the TurboGears Team, I am pleased to announce that TurboGears 1.5.1 is now available for download. Instructions for downloading and installing are at http://www.turbogears.org/1.5/docs/Install.html Changelog and upgrade instructions are available via http://www.turbogears.org/1.5/docs/WhatsNew.html We enabled and tested some new performant ways of running TurboGears 1.5 behind WSGI enabled web servers, as explained here: http://www.turbogears.org/1.5/docs/Deploy/ We recommend upgrading older TurboGears 1.x versions to 1.5 which is usually much easier than upgrading to 2.x. New TurboGears projects should start with TurboGears 2 which is the current, actively maintained variant of the TurboGears web-framework, based on Pylons instead of CherryPy. Have fun with TurboGears and let us know if there are any problems. -- Christoph Zwerschke -- 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] Request For Feedback
Am 18.11.2011 21:06, schrieb Michael Pedersen: First up: Python 2.4. I've said it in the past few months, but it's starting to look like we must address this sooner rather than later. Other projects are dropping support for it (for instance, WebOb, as of 1.1b1, has dropped support). I'm even willing to mark the next release as 2.2 just so we can drop 2.4 support entirely, and make our minimum either 2.5 or 2.6 (I'd like it to be 2.6 personally, so that we don't have to reach a similar point in another year or two). What does everybody else say? Right. I'd say drop Py 2.4 in TG 2.2 and Py 2.5 in TG 2.3. Second up: repoze.who is at 2.0. With our current set up, we are locked in at the 1.x series. I'd like to find a way to bring 2.0 support in so that it works easily for people. We can make it so that it is not required (similar to how TW1 and TW2 are both options), but I definitely want to get all of our packages upgraded to support the latest of everything. This way, we reduce some of the issues we've had where people are managing to get incompatible versions of packages (WebOb in particular). If possible, we should move to repoze.who 2.0 in TG 2.2 or 2.3, and also consolidate the used plugins as Alessandro suggested. Unfortunately it seems I won't have enough time for working on TG2 the next two months, so sorry I cannot help out with this. -- 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] Thought About planet.turbogears.org
Michael, I would not include tickets or changesets in the feed, as it will be too much noise and people will quickly unsubscribe. But maybe we could activate the Blog tool on the SourceForge project page and post some summary about what we're doing on that Blog, similarly to what you have been already doing with your weekly reports in the last months, and then add the RSS feed of that Blog. -- 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.
[tg-trunk] FormEncode sprint
There will be a IRC sprint for FormEncode on the weekend of Sep 24 for closing the accumulated issues on the bug tracker. Please join us if you want to help out. Mailing list is here: http://www.formencode.org/en/latest/community.html Btw, the FormEncode docs have moved to Read The Docs and the list of validators is available again. -- 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] Offline For Unknown Time
Good luck to you and all the others out there. -- 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] Content-Type in tg quickstart
Am 28.07.2011 21:56 schrieb Alessandro Molina:
I just did a few changes to render.py, decorators.py and master.html
and I'm now able to render pages in both xhtml and
application/xhtml+xml by simply specifying it inside the expose
decorator like:
@expose('app.templates.index') - outputs xhtml with content_type text/html
@expose('app.templates.index', content_type='application/xhtml+xml')
- outputs xml with right content type
Also changing charset in response works correctly.
Probably is fine to push this as is as it might have his own life.
Yes, that would be nice to have.
Btw, we have a similar problem with the doctype. As far as I see, in TG2
you cannot change it or have it automatically adapt to the content type
(e.g. HTML, XMTML1, HTML5).
Yes, this is indeed a more difficult issue to solve.
Should we define h.doctype() and substitute the line in master.html with that?
Currently there isn't any easier solution that I'm able to think of.
Genshi actually inserts the proper doctype if you pass it along with the
output method to the render method (e.g. doctype='html').
The only problem is that Pylon's render_genshi function does not pass
the doctype parameter. I had already reported this as Pylons ticket 613,
but it was never fixed. So the best solution would be to just inline and
improve Pylon's templating.render_genshi funtion into TG's
render.render_genshi function.
The doctype could then set from in render_genshi according to the
'templating.genshi.doctype' setting, with a suitable default derived
from the output method.
-- 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] Content-Type in tg quickstart
Am 25.07.2011 21:31 schrieb Alessandro Molina: Otherwise there might be cases where the controller reports a content-type and the meta tag another one if the users switched content type from the controller without making the template content type dependent from a variable. Actually if you're using templates you can't switch the content type (charset) in the controller anyway since you would need to also switch the output encoding of the templating engine which TG2 does not support. Any issue that I'm unable to see? One reason for keeping the meta tags is that they are useful when you store or cache pages for offline reading. Otherwsie, the content-type sent in the http header always takes precedence, so they will not harm even if they are wrong. Btw, this was one of the things I liked in Kid templates, where the engine injected the right meta tag in its output automatically. -- 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.
[tg-trunk] [ANN] TurboGears 1.5 released
On behalf of the TurboGears Team, I am pleased to announce that TurboGears 1.5 is now available for download at http://www.turbogears.org and the Python package index http://pypi.python.org/pypi/TurboGears Instructions for downloading and installing are at http://www.turbogears.org/1.5/docs/Install.html Changelog and upgrade instructions are available via http://www.turbogears.org/1.5/docs/WhatsNew.html Note that the well-known TurboGears 1 documentation has been cleaned up and migrated from MoinMoin to Sphinx. TurboGears 1 is a web-framework that has been created by Kevin Dangoor in 2005. Version 1.5 is the latest version in the original TurboGears 1 branch based on CherryPy, now featuring CherryPy 3. Simultaneously, we have also released bugfix versions 1.0.10 and 1.1.3 of the older branches running on CherryPy 2. The 1.0 branch is suitable for Python 2.3 to 2.5, while the 1.1 and 1.5 branches support Python 2.4 to 2.7. We recommend upgrading older TurboGears 1.x versions to 1.5 which is usually much easier than upgrading to 2.x. New TurboGears projects should start with TurboGears 2 which is the current, actively maintained variant of the TurboGears web-framework, based on Pylons instead of CherryPy. Have fun with TurboGears and let us know on the mailing list if there are any problems. -- Christoph Zwerschke -- 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] TG1 and Jenkins
Am 25.05.2011 22:54 schrieb Michael Pedersen: As you can see, something's not quite right with TG1.1 and TG1.5. The error messages in the build output looked like genuine issues, and not problems with the build environment, so I have to forward this along. Ok, I'll try to look into this tomorrow. -- 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] Python 2.4 Support
Am 20.05.2011 06:02 schrieb Michael Pedersen: Our current development tree provides support for Kajiki. Kajiki does not support Python 2.4. Can't we just provide support for Kajiki as an option without dropping support for Python 2.4? Genshi would continue to be the default because it's fully backward compatible and runs everywhere. -- 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] Python 2.4 Support
Am 20.05.2011 17:40 schrieb Michael Pedersen: This option didn't even cross my mind. The reason it didn't is because it violates another goal: 100% testing coverage. To test that Kajiki works, we have to test it. In order to test it, we have to render a page. On Python 2.4, we can't do that. In my opinion we do not need to require 100% coverage with Py 2.4 if there is already 100% coverage with Py 2.4 and all tests except for the Kajiki option do run with Py 2.4. If we drop Py 2.4 support then we should do it in the next minor release, i.e. TG 2.2. TG 2.1.x bugfix releases should continue to work with Py 2.4, but maybe we can add a deprecation warning. -- 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] few improvements for the website
Am 17.05.2011 14:47 schrieb Alessandro Molina: Inside it there are two Of /2.1 and Of /2.0 links that when opened load an apache directory index instead of any page. Also the SiteLink is quite confusionary as it appears having both Documentation and Turbogears Documentation links one pointing to the 2.1 doc and the other pointing to the 2.0 doc. Also the How to install link points to the 2.0 doc instead of 2.1 Thanks for reporting. I have changed the Apache config so that /x.y/ redirects to /x.y/docs/ instead of showing a directory, and have deactivated the site links with the Google webmaster tools. The site link changes may take some time to become visible. Also the TG web page is missing a description tag which causes google to show the old description from TG1.0 Michael, is it possible to add a description (and keywords) with tgext.pages? -- 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] TG2 Status Update - May 9, 2011
Am 10.05.2011 05:38 schrieb Michael Pedersen: Christoph, once we get the Jenkins instance working the way we expect it to, would you mind working out the details of getting TG1 projects properly building there? I'd like to have all of our projects showing up properly. Ok, I'll care for that. It will help if you document the Jenkins setup for TG2 when you're finished. -- 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] TG2 Status Update - Apr 18, 2011
Am 25.04.2011 18:08 schrieb Christoph Zwerschke: It will be good to have a virtual host anyway, so that we can do some redirects to better mimic the old MoinMoin wiki (e.g. redirect URLs without .html suffix). Also, docs.turbogears.org should redirect to the page at http://beta.turbogears.org/en/documentation. -- 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] TG2 Status Update - Apr 18, 2011
Am 19.04.2011 06:01 schrieb Michael Pedersen: Christoph, will you be able to get through the 1.x docs this week? And it's okay to say no, I'm just wanting to find out if we can plan the DNS changeover for the coming weekend. I'll try to do it tomorrow, but it would help if I can get some feedback on what to do with the wiki pages which are not actually part of the 1.x documentation. These fall in three categories: First, the wiki had several top-level pages with meta info about the project which do not belong into the actual docs. I will probably just remove most of these, but I'm a bit reluctant and want to get some feedback first. Can you to go through these and have a look if there is info that should be incorporated somewhere into the main website, or into an archive section or something: http://beta.turbogears.org/old/Contributing.html (and pp.) http://beta.turbogears.org/old/DevStatus.html http://beta.turbogears.org/old/DocHelp.html http://beta.turbogears.org/old/DocTeam.html (and pp.) http://beta.turbogears.org/old/GSoC.html (and pp.) http://beta.turbogears.org/old/GettingHelp.html http://beta.turbogears.org/old/News.html http://beta.turbogears.org/old/SprintOrganization.html (and pp.) http://beta.turbogears.org/old/TurboGearsBookMarks.html http://beta.turbogears.org/old/TurboGearsConsultants.html http://beta.turbogears.org/old/TurboGearsApplications.html http://beta.turbogears.org/old/TurboGearsBookMarks.html http://beta.turbogears.org/old/TGScreencasts.html http://beta.turbogears.org/old/VideoHelp.html Second, the MoinMoin wiki contained also the docs for some smaller, related projects. Not sure what to do with these: http://beta.turbogears.org/old/FastData.html http://beta.turbogears.org/old/tgDOMinclude.html http://beta.turbogears.org/old/tgLightbox.html http://beta.turbogears.org/old/tgMochiKit.html http://beta.turbogears.org/old/TGScheduler.html http://beta.turbogears.org/old/TurboCheetah.html http://beta.turbogears.org/old/TurboJson.html http://beta.turbogears.org/old/TurboKid.html Since most of them are on PyPi anyway, one idea is to put these docs into the long_description of the projects so these docs will appear on their PyPi pages. Third, the wiki also had two foreign language translations, but outdated and incomplete, so I think I will just remove them: http://beta.turbogears.org/old/ru/1.0/OfflineInstall.html http://beta.turbogears.org/old/ru/1.0/ToDoListTutorial.html -- 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] Re: [TurboGears] TG2 Status Update April 11, 2011
Today I worked on the MoinMoin - Sphinx conversion. Even though we already used ReST format, it was still quite time-consuming, particularly because I tried to retain as much material as possible (we can still throw parts of it away later, but I wanted to have it archived in the repository). As a first step, I have moved everything (1.0, 1.1 and 1.5 docs and meta infos) into one Sphinx project with subdirectories for 1.0, 1.1 and 1.5. The result is viewable here: http://beta.turbogears.org/old/ Let me know if things are not working properly or missing. As the next step, the 1.0, 1.1 and 1.5 directories should become independent Sphinx projects so that their namespaces do not collide and they can make references to the right package version, and made available directly under the URLs /1.0/, /1.1/, /1.5/, and the meta infos need to be merged into the new website (do we have a repositoriy for the website?), some outdated parts of the meta infos should probably go into an archive section of the website. The current source for the old docs is available at: http://sourceforge.net/p/turbogears1/code/7283/tree/docs/wiki/ -- 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] Just seen new doc
Am 06.04.2011 00:49 schrieb Alessandro Molina: I have just seen http://beta.turbogears.org/2.1/docs/ and I think that it is awesome. Great work. An absolute improvement over the current 2.1 doc theme. Yes, thanks for merging that in, Mike. I had invested some time work into this new layout last year and already feared this was in vain. The contents still needs to be improved and updated, but it's good to see we're finally overcoming the stagnation. -- 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] TG Trac and a Request
Am 04.04.2011 05:06 schrieb Michael Pedersen: Evening all. I'd like to ask people to do some simple tests for me overnight/tomorrow (i want to have this done before I send out my next status report). Looks good (enough) to me. -- 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] TG Project home on SF.net
Am 31.03.2011 15:02 schrieb Alessandro Molina: I have just noticed that turbogears.sf.net is currently set as the project home for TG2 project on sf.net. It might have sense to update that to http://turbogears.org/ to avoid problems for new users that found the project searching for a framework on sf.net Even worse, the project home link is broken if you are logged in since it does not work with https. But it's not obvious how and if this can be changed for a new style SF project. Mark? -- 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] TG2 Status Update - Mar 21, 2011
I have now migrated the Subversion repository from the old TurboGears server (http://svn.turbogears.org) to SourceForge (https://sourceforge.net/p/turbogears1/code/). The transfer took several hours since the SVN repository is huge: It contains the hisotry of the complete website with all the required files, videos etc. (close to 1GB). Please let me know if everything is there. It seems Allura has indexing problems again: If you click on a commit or on the history, the author name and commit message is not displayed in many cases. Also, does Allura not display diffs? -- 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] TG2 Status Update - Mar 21, 2011
Thanks. I hope we can then finish the Trac migration this weekend. -- Christoph Am 24.03.2011 05:08 schrieb Mark Ramm: That should be fixed now. Rabbitmq failures at the time of the ticket entry meant they were in mongo but not solr. New updates to allura should mean this will never happen again. -- 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] Minor Mid Week Update
Am 11.03.2011 05:25 schrieb Michael Pedersen: DNS updates are propagating right now. Tomorrow morning we'll be able to switch beta.turbogears.org http://beta.turbogears.org to the new server, and begin working on the details of what content goes where. It's important that docs.turbgoears.org (the MoinMoin wiki) will be kept running or moved to the new server until the TG 1 docs have been migrated to Sphinx. Right now both www.turbogears.org and docs.turbogears.org are not reachable any more. -- 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] Minor Mid Week Update
Hi Michael, I've created a similar TG1 tracker on SF now and also started moving the tickets. I'm always adding a link to the SF ticket as a comment in the Trac ticket, and then close the Trac ticket as duplicate. I suggest we do the same with the TG2 tickets, so we can see which tickets have already been moved. -- Christoph Am 10.03.2011 05:01 schrieb Michael Pedersen: I've started populating the ticket tracker on SF. It's slow going, mainly because I'm tired already this week. Still, 16 tickets copied over in an at least semi-usable fashion. Would people mind checking out what's there, and seeing if it works for them? -- Michael J. Pedersen My IM IDs: Jabber/peder...@icelus.tzo.com mailto:peder...@icelus.tzo.com, ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/pedermj022...@hotmail.com mailto: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. -- Herzliche Grüße 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] (1.5) Trac rejections
Am 09.03.2011 05:44, schrieb Ken Kuhlman: Unfortunately Trac has decided that I'm a spammer, so I can't create, assign, or note tickets. Should I wait until we're using Allura? I see there's a turbogears1 project on sourceforge now. Anything I can do to help? Right, I've closed a few TG1 Trac tickets and will move the remaining TG1 tickets to SF (Allura) this week, and then also help moving the TG2 Trac. So the new trackers will be available in the next days, Michael and I will give extra notice on the lists. It would be nice if you test the TG 1.5 branch as far as possible. Feedback on the list an on the SF tracker once it's available. I have a test for it sitting on my laptop, though it requires a refactoring of testutil.capture_log get_log. Those aren't used much (not at all in the test suite), so I don't believe there's a problem with making the change even though we're already at a 2nd beta. I didn't want to do it without a ticket, however. Such minor changes are still possible in TG 1.5. There will be another beta or at least a rc before the final release. The larger tickets will be moved to TG 1.5.1 which will then not be a bugfix release only. I think it's important to get TG 1.5 out the door because people will only start migrating to 1.5 and giving feedback when there is an official release available. -- 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] Re: tg 2.1+ and nosetests
Am 09.03.2011 05:55 schrieb Michael Pedersen: Now that my test cases are finally passing cleanly, I can get to work on migrating tickets and applying patches as appropriate. Thanks, Michael. It's important to keep our test suite clean. We should install Hudson/Jenkins on Florent's server once the trackers and home page have been set up, so such things will get more attention. The tests should also run in different environments (different Pylons and Python versions etc.) -- 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
Am 07.03.2011 02:15 schrieb Mark Ramm: I have no objections to this approach. As for the TG2 as sf.net location, I'm partial to /p/turbogears2/ but can be persuaded by somebody with a strong argument/ Ok, so let's follow that plan now. I'm also for using turbogears1 and turbogears2 as project names, and removing turbogears because that will create only confusion. We should also create a top level project turbogears3, orion, karnak but obviously we will need to agree on a name first. I like Orion, but it can be confused with Apache Orion. -- 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
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.
[tg-trunk] Another suggestion for the Trac migration
As already posted, one of the things that is hampering us for too long already is the migration of our old Trac. We actually wanted to move to SF to minimize the admin work, but it turned out to make more work as expected, and I'm still doubt how faithful/useful the migrated tickets and comments will be, i.e. whether the markup, authors, links to revisions, versions, milestones etc. will be properly preserved. We have ~2500 tickets, ~2000 for TG1 and ~500 for TG2. That looks much, but if we look at the *active* tickets only, we're actually talking about only ~130 tickets, ~30 for TG1 and ~100 for TG2. So why don't we just forget about the old cruft and start with a plain slate? Most of it has become irrelevant anyway and is only creating confusion now. So my suggestion is that we create fresh Allura trackers for TG1, TG2 and TG3 on SF. We will then go through all still active tickets on the old Trac and do a triage: * simple - do it immediately and close * more complex - manually enter them in Allura and close in Trac * irrelevant, outdated, not reproducable etc. - just close In the last category, we could already clarify the tickets, add ideas for solutions etc. Once all tickets on the old Trac have been closed that way (I expect this can be done in one or two weeks), I will copy the old Trac to Florent's server where it can serve as a read-only reference. What do you think about this idea? -- 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
Am 05.03.2011 13:19 schrieb Christoph Zwerschke: * simple - do it immediately and close * more complex - manually enter them in Allura and close in Trac * irrelevant, outdated, not reproducable etc. - just close In the last category, we could already clarify the tickets, add ideas for solutions etc. I meant in the second category. This would not only accelerate our SF migration, but also the development. After we've gone through all open tickets that way, we could immediately release TG 2.1.1. -- 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] Re: Trac Migration Status Update
Am 27.02.2011 04:42 schrieb Christopher Arndt: You can run Trac on a read-only slave of a repository. I've done that in the past. If needed, I can look for the necessary scripts to set up a Subversion repository replication. Actually our goal was to simplify the infrastructure, not complicate it ;-) but this will provide us with an extra repository backup and simplify the full move to SF later, so seems like a good idea. We will come back to you if we need help with that. -- 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] Re: Trac Migration Status Update
Am 27.02.2011 18:12 schrieb Felix Schwarz: So if you have problems/questions I'm glad if I can help out (also speaking as a Trac/Babel/Bitten developer). Thanks, Felix. The current status is that Mark wants to give Allura another chance. So I'm waiting for the outcome of that since it's our preferred option. We're currently moving back and forth a bit, but luckily, it's going two steps forth and one step back only ;-) In the meantime, we can work on other things like the new homepage. -- 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] Re: TG2 Weekly Status Update - February 14, 2011
Am 22.02.2011 11:34, schrieb Florent Aide: As I said above we wanted a TG2 showcase and we wanted flexibility. I think that some of the applications that we have on this server can still be usefull. Thanks, Florent. I think we should follow that route, we already wanted to do that a long time ago and hopefully now we have enough steam again to make it happen. I preferred SF, but it seems the beta forge (Allura) is not yet mature enough. We can of course re-evaluate that option at a later time, if we don't create a too sophisticated site that will be difficult to migrate elsewhere. Concerning the bug tracker, I vote for using the latest stable version of Trac, but split up in subprojects for TG1 and TG2. -- 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] Re: TG2 Weekly Status Update - February 14, 2011
Am 17.02.2011 16:18 schrieb Michael Pedersen: So, what's the difference between using Trac tasks and flow.io http://flow.io? Especially if we throw in something like a gantt chart plugin? (I have seen that one, even used it, so I know it exists and does well). Especially since people can be on Trac, take tasks, etc. I would use flow.io for coordinating the general project management related tasks and workflow and Trac for keeping track of concrete, detailed development tasks directly related to the code. The advantage of flow.io is that you see who is working on what at the moment and get a nice overview of what has been done recently and what needs to be done next. -- 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] Re: TG2 Weekly Status Update - February 14, 2011
Am 17.02.2011 17:50 schrieb Michael Pedersen: I'll get myself logged into it tonight and check it out. I'm not going to promise anything. I will say that it looks promising, though. Then again, github looks promising, too. Part of me wonders if we might not be better off with github vs SF, too. Some of what they offer looks amazing in comparison. Concerning flow.io please don't misundertand me, I don't propose it as an alternative bug tracker, just as an additional tool for handling the high level management tasks which are not directly related to the code and relatively few compared to the number of trac tickets. And yes, github is not bad, but I think the bugtracker is also their weak point. I'm currently busy but also want to evaluate the SF hosted trac option this weekend, so please wait until I could have a look before making any drastic moves. Also, maybe you can talk with the SF support team via IRC (#sourceforge at freenode) regarding the forge tracker documentation. They are usually very responsive and helpful. -- 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] Re: TG2 Weekly Status Update - February 14, 2011
Am 17.02.2011 23:36 schrieb Mark Ramm: I'll talk to folks on this end and make sure we get the migration API docs pushed out into a publicly accessible place. Thanks, Mark. Maybe the export/import scripts are already sufficient for our needs, but that would help anyway. We probably need to make some adjustments, e.g. map Trac usernames to SF usernames (at least for the core developers). @Michael: We should prolong the ultimatum for the SF tracker migration now that we have some code and hopefully soon also docs for the tracker API. We need some time to experiment with this. -- 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] Re: TG2 Weekly Status Update - February 14, 2011
Am 16.02.2011 03:47 schrieb Michael Pedersen: You missed the documentation being fixed. That, in fact, is the only item on my list that you didn't mention. We're definitely agreeing on the needs of TG2. Right, documentation is also important for me. Btw, don't forget I've already worked on the layout (https://bitbucket.org/cito/tg-docs-21) so we can start from there and concentrate on the content. Another idea to push things forward: We could use http://flow.io for managing the higher level project management, coordinating our efforts, keeping track of what needs to be done and spreading the workload. It might be a good idea, I just don't know enough about it. Never seen it, never used it, never heard of it before now. And I still have to finish learning enough of git to be comfortable. I don't think I can pick up another new tool yet. flow.io is not a complicated tool, you can use it intuitively without learning efforts. And open source projects can use it for free. It could remind us of all the open tasks we discussed and would show who is working on what so that we do not suddenly start to work on the same thing at the same time. As some more people like Florent want to join the project team it is important to coordinate our efforts so we don't step on each others toes. -- 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] Re: TG2 Weekly Status Update - February 14, 2011
Am 17.02.2011 04:48 schrieb Michael Pedersen: I'll admit to being confused still: Which machine is Florent's? Where does the current www.turbogears.org http://www.turbogears.org actually point? Ok, that obviously needs clarification: www.turbogears.org is our old server where all of the components (os, python, svn, trac, moinmoin wiki etc.) are outdated now. The server had been granted by Webfaction a long time ago, but actually only as a temporary solution, we're really drawing on their generosity already and promised to move for a long time already. *We really shouldn't touch that server any more*. The plan had been to move to Florent's server but it was never realized since everybody was busy. Later SF came up as an alternative since Mark is working there and since they also use TG2 so we have some connections anyway. But Florent's server is still interesting at least for the CI stuff, and maybe also for bug tracking, at least until SF offers a more viable solution. As far as integration/performance tests, what were you thinking? Behavior-driven tests, using something like Lettuce or PyCukes? Scripted installations? Something else? I'm thinking that we should be able to do the following: * full unit testing with 100% coverage * testing of the installation from scratch (ultimately, on a variety of platforms) * performance testing (using pystones to benchmark the machine, and then using that to normalize the requests/second for a few pages out of a quickstarted application) * Possibly scripting tests for a few extensions and making sure they work properly (such as tgext.admin) I also thought of writing a more realistic, sophisticated reference TG app that could be used as base for the benchmark and functional tests and also serve as demo app for new users. That would be better than only using a hello world or quickstarted project to test TG performance. But of course, the tests should also quickstart apps with different options and test these. I.e. we should not only test tg, but also tgdevtools. I think currently tgdevtools has no automated tests. -- 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] Re: TG2 Weekly Status Update - February 14, 2011
Am 15.02.2011 14:47, schrieb Alessandro Molina: On Tue, Feb 15, 2011 at 2:34 PM, jorge.var...@gmail.com jorge.var...@gmail.com wrote: Both the methods you suggest have been tried before and both have failed. Forcing our pypi index, has the opposite problem, if there is a mayor security release, or something that unbreaks something that broke really bad (look for the Extremes package for an example of how it was broken in our pypi and fixed in regular pypi. We have off course to keep our pypi updated when fixes for the libraries that we use appear. This shouldn't be a problem as we use TG ourselves and so we know when it won't install anymore. I wanted to answer the same, I don't see the problem with the approach itself, but with us failing to properly maintain our own PyPI. -- 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] Re: TG2 Weekly Status Update - February 14, 2011
Am 15.02.2011 16:15, schrieb Michael Pedersen: This is a viable way of specifying the requirements, definitely. I'd actually go with 0.7 and 0.8, though. The problem with that is that setuptools considers 0.7a1, 0.7b1, 0.7rc1 all 0.7 (which makes some sense). So 0.7a1 is probably what you want. -- 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] Re: TG2 Weekly Status Update - February 14, 2011
Am 15.02.2011 16:46, schrieb Christophe de Vienne:
What about 0.7dev ?
Right, 0.7dev is sorted even before 0.7a
with the current setuptools and distutils:
from pkg_resources import parse_version as V
V('0.7.dev1') == V('0.7dev1') V('0.7a1') V('0.7b1') V('0.7')
True
However, 0.7dev is not valid and 0.7.dev 0.7a
with the newly proposed version schema of PEP386:
from verlib import NormalizedVersion as V
V('0.7a1') V('0.7b1') V('0.7.dev1') V('0.7')
True
V('0.7dev')
verlib.IrrationalVersionError: 0.7dev
So maybe we need to combine both: 0.7.dev1, 0.7a1
-- 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] TG2.1 Weekly Status Update, Feb 7, 2011
Am 12.02.2011 22:04 schrieb Michael Pedersen: Okay, I've managed to get logged into the sf.net http://sf.net web, and tested out uploading data to it. I've been able to upload a test page, and retrieve it afterwards. Another progress I just noticed is that the hosted apps and other tools have now been activated for all of the SF Pylons projects (thanks, Rick). l'll check if the TG1 trac can be imported to a hosted Trac next weekend or one of the other tools may be useful for us. -- 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] TG2.1 Weekly Status Update, Feb 7, 2011
Thanks for the update, Mike. Such updates are helpful even if not much has been done so as to identify where things are hanging. Regarding the migration of tickets we're currently stuck because as far as I see Trac has not yet been activated on SF (must be done manually by SF staff for the beta forge we're using) so we cannot migrate the TG1 tickets, and the documentation of the new forge API is not yet online so we cannot write a script to migrate the TG2 tickets. -- 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.
