On Wed, Aug 20, 2008 at 7:15 PM, Randy Kramer [EMAIL PROTECTED] wrote:
True, brevity is a virtue, but this is too brief. If you have
objections please state them clearly.
Sorry!
No problem. Just remember that I get many emails every day on many
subjects. Please always quote a previous
On Thursday 21 August 2008 07:32 am, Edward K. Ream wrote:
To have any chance of convincing me, you would have to show why the
different approach is a) better than Leo's already flexible
configuration way and b) worth the trouble to implement.
Edward,
Thanks for offering that opportunity,
On Wed, Aug 20, 2008 at 1:09 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
On Wed, Aug 20, 2008 at 11:36 AM, Kent Tenney [EMAIL PROTECTED] wrote:
Especially now that Leo has shadow files, I think people will be
unsurprised to see Leo config and private in company like:
ls -a
.leo
.bzr
.svn
On Thursday 21 August 2008 08:20 am, Ville M. Vainio wrote:
On Thu, Aug 21, 2008 at 2:32 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
To have any chance of convincing me, you would have to show why the
different approach is a) better than Leo's already flexible
configuration way and b)
On 20 aug, 18:05, Ville M. Vainio [EMAIL PROTECTED] wrote:
On Wed, Aug 20, 2008 at 5:05 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
We have gone around and around with the linux install script. I'd
rather not change it at all unless absolutely required.
I don't see a need for that
I'd rather not add .pth files by default. In the new bzr world I'm
often working on several different branches at once. Adding .pth
files could create some unintended results.
Maybe that could be prevented by using a .pth-file for each branch
like leo-4-3-b1.pth, leo-4-3-1-b2.pth, etc.
On 20 aug, 18:30, Edward K. Ream [EMAIL PROTECTED] wrote:
On Aug 20, 11:05 am, Ville M. Vainio [EMAIL PROTECTED] wrote:
On Wed, Aug 20, 2008 at 5:05 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
We have gone around and around with the linux install script. I'd
rather not change it at
Finally using unittests in a project (not Leo, sorry). First mistake
was to use this pattern:
...
doSomething()
self.failUnless(cond1, ms1)
self.failUnless(cond2, ms2)
self.failUnless(cond3, ms3)
self.failUnless(cond4, ms4)
Although in principle this works, it results in a
On Thu, Aug 21, 2008 at 5:17 PM, rogererens [EMAIL PROTECTED] wrote:
- Just run launchLeo.py from the root directory where you extracted the
tarball.
If a /usr/bin/leo or /usr/local/bin/leo executable script is created
that contains
python root of extracted leo-directory/launchLeo.py $@
Just a wishlist thing, would it be possible to expose the @auto
processing code in a command so that when you have a body like this:
class AClass:
def func1:
do1()
def func2:
do2()
def func3:
do3()
def func4:
do4()
you can automatically push
On Aug 21, 10:27 am, Edward K. Ream [EMAIL PROTECTED] wrote:
Rev 866 of the trunk now contains rewrites of g.es, g.es_print, g.pr,
g.error and g.trace. Please report any print-related problems
immediately.
I have spent most of the day trying to track down some unicode
problems.
The
On Aug 18, 9:47 pm, Terry Brown [EMAIL PROTECTED] wrote:
reading: @shadow tables.sql Bad @+leo sentinel in: tables.sql can not
read 3.x derived file tables.sql you may upgrade these file using Leo
4.0 through 4.4.x reading: @shadow maglink.py
The proposed fixes are on the trunk at rev 874.
On Thu, Aug 21, 2008 at 5:04 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
At present, I have not figured out a way to represent 'big' unicode
characters, such as Ă, in scripts.
It finally dawned on me that I could run test code directly in the
Python interpreter. This eliminates all
13 matches
Mail list logo
