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
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?
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:
{{
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
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
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
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
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
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
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
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
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
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
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
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
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,
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
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
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
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
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
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
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,
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
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,
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
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
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
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
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
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
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
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
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.
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
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
--
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
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,
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
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.
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
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
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
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
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.
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
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
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
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
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
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
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
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.
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
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?
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
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
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
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
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
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
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
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
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
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
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
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
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
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.
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
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.
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
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
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).
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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.
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
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
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
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
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
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
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
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
1 - 100 of 355 matches
Mail list logo
