Hi,
Marius Gedminas wrote:
I do not think that the requirements to
4. Write unit tests
5. Merge bugfixes from trunk to the release branch
6. Wait for the incredibly slow updates on the collector
discourage me all that much.
Right. They don't discourage me either, but there is a special
[EMAIL PROTECTED] wrote:
Almost surely, the code should be cur_tid = tid rather than
cur_tid tid. But there is nobody that is sure about it.
Well, as I've asked before, what needs to happen for someone to _become_
sure about it?
(or at least change it and see what happens? ;-) )
cheers,
[Dieter M]
Almost surely, the code should be cur_tid = tid rather than
cur_tid tid. But there is nobody that is sure about it.
[Chris W]
Well, as I've asked before, what needs to happen for someone to _become_
sure about it?
Same answer as before: someone who understands the intended
Hi All,
Is there any more graceful way to run the zope.i18n tests from the Zope
core than the following from an instance:
bin\tests --path=/../lib/python -s zope.i18n
cheers,
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
Hi.
Chris Withers wrote:
Been looking more into getting lists of available languages for a domain
out of Zope 3.
Just curious, do you use only the zope domain or some other domains as well?
Philipp pointed me to zope.i18n.interfaces.ILanguageAvailability, which
appears to be a tiny
Hanno Schlichting wrote:
Chris Withers wrote:
Been looking more into getting lists of available languages for a domain
out of Zope 3.
Just curious, do you use only the zope domain or some other domains as well?
Other domains as well. In fact, the only domain I care about is one
specific to
[EMAIL PROTECTED] wrote:
Christian Theune wrote at 2006-7-5 11:46 +0200:
...
Another thing are the rules about unit tests. Some bugs touch areas that
are poorly tested. When I fix a bug over there, do I have to work harder
to introduce the fix because I have to start introducing tests?
We
Chris Withers wrote:
Hi All,
Is there any more graceful way to run the zope.i18n tests from the Zope
core than the following from an instance:
bin\tests --path=/../lib/python -s zope.i18n
$ svn co .../trunk Zope3
$ cd Zope3
$ make
$ python test.py -s zope.i18n
Philipp
Hi there,
I see a few packages lurking in svn.zope.org that I can't make much
sense of:
* For example, what is zope.generic? I can't find a README.txt anywhere
in the top-level directories. What I *can* see is that it seems to be
another big bag for subpackages like zope.app. I thought we were
Chris Withers wrote:
Hi All,
Been looking more into getting lists of available languages for a domain
out of Zope 3.
Philipp pointed me to zope.i18n.interfaces.ILanguageAvailability, which
appears to be a tiny interface that's not used anywhere.
Not within in Zope 3 at least...
What
Chris Withers wrote:
TranslationDomain should still implement ILanguageAvailability and
zope.i18n.zcml.registerTranslations should register domains for that
interface as well as ITranslationDomain,
I'd prefer to create an interface extending ITranslationDomain and
ILanguageAvailability, making
On 7/6/06, Philipp von Weitershausen [EMAIL PROTECTED] wrote:
- Do other people also think it'd be a good idea to come up with some
repository guidelines? Stephan had a proposal about specifying package
metadata and code maturity/quality, I think it's worth working towards
easily accessible info
Philipp von Weitershausen wrote at 2006-7-6 18:29 +0200:
... fixing a trivial error without a unit test ...
How would you make sure that your fix for even a trivial
NameError actually works? Perhaps you introduced another typo in the
bugfix?
Obviously, I have considerable more confidence in my
On 7/6/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
When I have introduced secondary bugs in my fixes (which occasionally
happened), then a unit test would not have helped. The reason was then
that the affected code was used in unanticipated ways -- and
because it was unanticipated, I would
Lennart Regebro wrote at 2006-7-6 20:03 +0200:
On 7/6/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
When I have introduced secondary bugs in my fixes (which occasionally
happened), then a unit test would not have helped. The reason was then
that the affected code was used in unanticipated ways
Hi Philipp
good idea, just some update what allready happen when
you where in China ;-)
[...]
I see a few packages lurking in svn.zope.org that I can't
make much sense of:
* For example, what is zope.generic? I can't find a
README.txt anywhere in the top-level directories. What I
*can*
Philipp von Weitershausen wrote:
Chris Withers wrote:
TranslationDomain should still implement ILanguageAvailability and
zope.i18n.zcml.registerTranslations should register domains for that
interface as well as ITranslationDomain,
I'd prefer to create an interface extending ITranslationDomain
Hi Philipp, Dominik
Dominik, can you give a short overview what zope.generic
can do?
[...]
If you take a closer look at this package and you will see
that each
subpackage is well documented.
Right. But that information isn't easily accessible. You have
to go to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
no problem, I agree to have a place for such infos.
The README.txt files are not good enough for give a overview
because you have to checkout first or browse the really slow
repos with a browser.
Tell me where is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Theune wrote:
Hi,
Marius Gedminas wrote:
I do not think that the requirements to
4. Write unit tests
5. Merge bugfixes from trunk to the release branch
6. Wait for the incredibly slow updates on the collector
discourage me all that
20 matches
Mail list logo
