ANN: SE 2.3. Available now
A few Cheese Shop upload problems have been solved with the help of this
creative group. Thank you all!
Version 2.2 beta should be phased out. It has a functional defect,
missing matches with a very low statistical probability. Version 2.3 has
this fixed.
Download URL: http://cheeseshop.python.org/pypi/SE/2.3
A list of possible handling improvements is being made to be
incorporated in the next version, One major flaw of the interface design
came to light the other day when a user reported a non-functioning
Editor Object made with a file name. If the constructor cannot find the
file it records the fact in the object's log without making the user
aware that his Editor Object is incomplete or altogether devoid of
substitutions. His obvious conclusion is that the damn thing isn't
working right.
Compile errors should certainly be reported at compile time. The next
version will send all messages being logged also to stderr by default.
The thing to do with the current version, if it appears to malfunction,
is to inspect the log and the compiled substitutions.
>>> Editor = SE.SE ('operators.se')
>>> Editor.show_log ()
Fri Nov 03 12:49:17 2006 - Compiler - Ignoring single word
'operators.se'. Not an existing file 'operators.se'.
>>> Editor = SE.SE ('se/operators.se') # path was missing
>>> Editor.show_log ()
(Log is empty. All is well.)
>>> Editor.show (show_translators = 1)
(snip)
Single-Byte Targets
1: |<|->|LT|
2: |>|->|GT|
Multi-Byte Targets
3: |&&|->|AND|
4: ->|OR|
etc...
The display makes definition errors conspicuous. Missing definitions
indicate malformed or redefined (overwritten) ones.
Frederic
--
http://mail.python.org/mailman/listinfo/python-list
Re: ANN: SE 2.3. Available now
Frederic Rentsch wrote:
> A few Cheese Shop upload problems have been solved with the help of this
> creative group. Thank you all!
>
> Version 2.2 beta should be phased out. It has a functional defect,
> missing matches with a very low statistical probability. Version 2.3 has
> this fixed.
>
>Download URL: http://cheeseshop.python.org/pypi/SE/2.3
>
As a matter of polite netiquette, a message like this really ought to
have a paragraph telling us what SE *is*.(Unless it's a secret :-))
> A list of possible handling improvements is being made to be
> incorporated in the next version, One major flaw of the interface design
> came to light the other day when a user reported a non-functioning
> Editor Object made with a file name. If the constructor cannot find the
> file it records the fact in the object's log without making the user
> aware that his Editor Object is incomplete or altogether devoid of
> substitutions. His obvious conclusion is that the damn thing isn't
> working right.
>Compile errors should certainly be reported at compile time. The next
> version will send all messages being logged also to stderr by default.
> The thing to do with the current version, if it appears to malfunction,
> is to inspect the log and the compiled substitutions.
>
> >>> Editor = SE.SE ('operators.se')
> >>> Editor.show_log ()
>
> Fri Nov 03 12:49:17 2006 - Compiler - Ignoring single word
> 'operators.se'. Not an existing file 'operators.se'.
>
> >>> Editor = SE.SE ('se/operators.se') # path was missing
> >>> Editor.show_log ()
>
> (Log is empty. All is well.)
>
> >>> Editor.show (show_translators = 1)
>
> (snip)
>
> Single-Byte Targets
> 1: |<|->|LT|
> 2: |>|->|GT|
>
> Multi-Byte Targets
> 3: |&&|->|AND|
> 4: ->|OR|
>
> etc...
>
> The display makes definition errors conspicuous. Missing definitions
> indicate malformed or redefined (overwritten) ones.
>
>
> Frederic
>
>
>
--
http://mail.python.org/mailman/listinfo/python-list
Re: ANN: SE 2.3. Available now
Gary Herron wrote: > As a matter of polite netiquette, a message like this really ought to > have a paragraph telling us what SE *is*.(Unless it's a secret :-)) nah, if you've spent more than five minutes on c.l.python lately, you'd noticed that it's the Solution to Everything (up there with pyparsing, I think). -- http://mail.python.org/mailman/listinfo/python-list
Re: ANN: SE 2.3. Available now
Gary Herron wrote:
> Frederic Rentsch wrote:
>
>> A few Cheese Shop upload problems have been solved with the help of this
>> creative group. Thank you all!
>>
>> Version 2.2 beta should be phased out. It has a functional defect,
>> missing matches with a very low statistical probability. Version 2.3 has
>> this fixed.
>>
>>Download URL: http://cheeseshop.python.org/pypi/SE/2.3
>>
>>
> As a matter of polite netiquette, a message like this really ought to
> have a paragraph telling us what SE *is*.(Unless it's a secret :-))
>
>
Thanks for the inquiry. I've been hawking this thing so persistently of
late that I'm afraid to start being perceived as a nuisance. SE is a
stream editor that is particularly easy and fast to use. A summary of
its characteristics is only a click away at the URL a few lines up from
this line.
Frederic
>> A list of possible handling improvements is being made to be
>> incorporated in the next version, One major flaw of the interface design
>> came to light the other day when a user reported a non-functioning
>> Editor Object made with a file name. If the constructor cannot find the
>> file it records the fact in the object's log without making the user
>> aware that his Editor Object is incomplete or altogether devoid of
>> substitutions. His obvious conclusion is that the damn thing isn't
>> working right.
>>Compile errors should certainly be reported at compile time. The next
>> version will send all messages being logged also to stderr by default.
>> The thing to do with the current version, if it appears to malfunction,
>> is to inspect the log and the compiled substitutions.
>>
>> >>> Editor = SE.SE ('operators.se')
>> >>> Editor.show_log ()
>>
>> Fri Nov 03 12:49:17 2006 - Compiler - Ignoring single word
>> 'operators.se'. Not an existing file 'operators.se'.
>>
>> >>> Editor = SE.SE ('se/operators.se') # path was missing
>> >>> Editor.show_log ()
>>
>> (Log is empty. All is well.)
>>
>> >>> Editor.show (show_translators = 1)
>>
>> (snip)
>>
>> Single-Byte Targets
>> 1: |<|->|LT|
>> 2: |>|->|GT|
>>
>> Multi-Byte Targets
>> 3: |&&|->|AND|
>> 4: ->|OR|
>>
>> etc...
>>
>> The display makes definition errors conspicuous. Missing definitions
>> indicate malformed or redefined (overwritten) ones.
>>
>>
>> Frederic
>>
>>
>>
>>
>
>
--
http://mail.python.org/mailman/listinfo/python-list
Re: ANN: SE 2.3. Available now
Fredrik Lundh wrote: > Gary Herron wrote: > > >> As a matter of polite netiquette, a message like this really ought to >> have a paragraph telling us what SE *is*.(Unless it's a secret :-)) >> > > nah, if you've spent more than five minutes on c.l.python lately, you'd > noticed that it's the Solution to Everything (up there with pyparsing, I > think). > > > > And here's the proof I am being perceived as a nuisance. I apologize, keeping to myself that I don't care. Frederic -- http://mail.python.org/mailman/listinfo/python-list
Re: ANN: SE 2.3. Available now
Frederic Rentsch wrote: > And here's the proof I am being perceived as a nuisance. I apologize, > keeping to myself that I don't care. since you're constantly targeting newbies, and are hawking your stuff also for things for which there are simple and efficient solutions available in Python's standard library, your behavior could be seen as more than just a nuisance. -- http://mail.python.org/mailman/listinfo/python-list
Re: ANN: SE 2.3. Available now
Fredrik Lundh wrote: > Frederic Rentsch wrote: > > >> And here's the proof I am being perceived as a nuisance. I apologize, >> keeping to myself that I don't care. >> > > since you're constantly targeting newbies, and are hawking your stuff > also for things for which there are simple and efficient solutions > available in Python's standard library, your behavior could be seen > as more than just a nuisance. > > > > Thank you for making me aware of it. I totally agree with you that inefficient complexity should never replace efficient simplicity. SE, in fact, is much more a convenient interface complement than a stand-alone tool and as such meant to cooperate with the available Python idiom. I used this forum to connect with real-life problems, which I believe is one of its main purposes. Testing the envelope of my 'stuff' I would almost certainly have overstretched it on occasion. And again, what's wrong with this absolutely normal development process? And what better environment could there be for it than an interest group like this one where experts like yourself offer direction? I am not targeting newbies (whatever that is). I am not targeting at all. I invite response. You had cause to respond as this message of yours reveals. But you didn't respond and now your are angry with me for it. So, thanks again for the information. Your comments are always welcome. I understand your style as an expression of your personality. Belligerence passes my notice if I don't see what I have to do with it. Regards Frederic -- http://mail.python.org/mailman/listinfo/python-list
Re: ANN: SE 2.3. Available now
> nah, if you've spent more than five minutes on c.l.python lately, you'd > noticed that it's the Solution to Everything (up there with pyparsing, I > think). SE would be the Solution to Everything. pyparsing Provides Your Perfect Alternative where Regexp Syntax Is No Good. The "re" module is just Routinely Expected to solve all problems. :) -tkc -- http://mail.python.org/mailman/listinfo/python-list
