Re: Friday Finking: Beyond implementing Unicode

2020-06-12 Thread Elliott Roper
On 12 Jun 2020 at 09:47:04 BST, "moi"  wrote:

> i) Today there people, who are still not understanding this:
> 
 'Å'.encode('utf-8')
> b'\xc3\x85'
 'Å'.encode('utf-16-le')
> b'\xc5\x00'
 'Å'.encode('utf-32-le')
> b'\xc5\x00\x00\x00'
> 
> ii) On a Western Europen Windows, Py 3 is not even working
> correctly with the *characters* of the Windows-1252 coding
> scheme. (As I understand this issue, you may have the same
> problem on let say an iso-8859-2 platform).
> 
> iii) When it works, I mean when it *by chance* works, the
> result is all by satisfying:
> 
 import timeit
 timeit.timeit("s.encode('utf-8')", "s = 'Universität Zürich' * 1000")
> 50.9616764429
 timeit.timeit("s.encode('utf-8')", "s = 'Universitat Zurich' * 1000")
> 2.488587845973
 
> 
> 
> iv) ...
> v) ...
> vi) ...

i) Who cares?
ii) Breaking News. Windows is mired in backward compatibility.
iii) My 3 year old Mac is 5 times faster than that. Get over it.

Maths always made its greatest advances after notation improved.
Terseness and unambiguity are king.

You are looking backward.
DL Neil is looking forward. A long way forward. It won't be our generation,
our brains are already mis-wired.

-- 
To de-mung my e-mail address:- fsnospam$elliott$$
PGP Fingerprint: 1A96 3CF7 637F 896B C810  E199 7E5C A9E4 8E59 E248


-- 
https://mail.python.org/mailman/listinfo/python-list


Re: Friday Finking: Beyond implementing Unicode

2020-06-12 Thread Chris Angelico
On Fri, Jun 12, 2020 at 9:11 PM Elliott Roper  wrote:
>
> On 12 Jun 2020 at 09:47:04 BST, "moi"  wrote:
> i) Who cares?

Don't bother responding to him. He's somehow gotten the idea that
Python's Unicode support is broken, and he spews his vomit out onto
the newsgroup periodically. He's blocked from the mailing list, and
for good reason. Ignore him and save yourself the hassle.

ChrisA
-- 
https://mail.python.org/mailman/listinfo/python-list


Re: pyinstaller

2020-06-12 Thread Robin Becker

On 11/06/2020 16:39, Grant Edwards wrote:

the hands of the developer.  I suppose the OP could quit and stand on
the street corner with a cardboard sign:

I would love to do that :)
--
https://mail.python.org/mailman/listinfo/python-list


Re: Friday Finking: Beyond implementing Unicode

2020-06-12 Thread Terry Reedy

On 6/12/2020 2:03 AM, DL Neil via Python-list wrote:
Unicode has given us access to a wealth of mathematical and other 
symbols. Hardware and soft-/firm-ware flexibility enable us to move 
beyond and develop new 'standards'. Do we have opportunities to make 
computer programming more math-familiar and/or more 
logically-expressive, and thus easier to learn and practice? Could we 
develop Python to take advantage of these opportunities?


...

Could we then also 'update' Python, to accept the wider range of symbols 
instead/in-addition to those currently in-use?


Would such even constitute 'a good idea'?


There was a recent thread on python-ideas discussing this.  It started 
with arrow characters.  There have been others.



--
Terry Jan Reedy

--
https://mail.python.org/mailman/listinfo/python-list


Python database compatibility

2020-06-12 Thread Siddharth Joshi
All,

I am new in Python world and would like to use it for one of the our
purpose . Before that, I would like to ask if Python has compatibility with
ENSCRIBE database .

Enscribe database (file structured) is the native database of HP NonStop
(Tandem) server, mainly used in applications running on nonStop Tandem .
Almost all the applications which runs on Tandem using enscribe are Tier 0
applications (often critical once).

Would be good if anyone let me know on Python and Enscribe compatibility.

Many thanks
Sid
-- 
https://mail.python.org/mailman/listinfo/python-list


Re: Python database compatibility

2020-06-12 Thread Larry Martell
On Fri, Jun 12, 2020 at 5:03 PM Siddharth Joshi  wrote:
>
> All,
>
> I am new in Python world and would like to use it for one of the our
> purpose . Before that, I would like to ask if Python has compatibility with
> ENSCRIBE database .
>
> Enscribe database (file structured) is the native database of HP NonStop
> (Tandem) server, mainly used in applications running on nonStop Tandem .
> Almost all the applications which runs on Tandem using enscribe are Tier 0
> applications (often critical once).
>
> Would be good if anyone let me know on Python and Enscribe compatibility.

If you can use ODBC with it then you can use python with it.
-- 
https://mail.python.org/mailman/listinfo/python-list


Re: pyinstaller

2020-06-12 Thread DL Neil via Python-list

On 13/06/20 3:09 AM, Robin Becker wrote:

On 11/06/2020 16:39, Grant Edwards wrote:

the hands of the developer.  I suppose the OP could quit and stand on
the street corner with a cardboard sign:

I would love to do that :)



Of possible interest to folk interested in this thread:
Recently came across this article:
https://www.activestate.com/blog/how-to-convert-py-to-exe/
NB have no assessment/advice to report
--
Regards =dn
--
https://mail.python.org/mailman/listinfo/python-list


Re: Python database compatibility

2020-06-12 Thread DL Neil via Python-list

On 13/06/20 8:49 AM, Siddharth Joshi wrote:

I am new in Python world and would like to use it for one of the our
purpose . Before that, I would like to ask if Python has compatibility with
ENSCRIBE database .

Enscribe database (file structured) is the native database of HP NonStop
(Tandem) server, mainly used in applications running on nonStop Tandem .
Almost all the applications which runs on Tandem using enscribe are Tier 0
applications (often critical once).


Wow, a 'blast from the past'!

I worked on HP3000s (from which Tandem originally developed) forty years 
ago. My first foray into 'non-stop' computing, supporting banking 
systems and the like, involved jumping-ship to Stratus (or more 
precisely, the re-badged IBM System/88). Others were also involved in 
that project, so happily/sadly I ended-up consulting for a project that 
no-one else wanted: figuring out how to network those new-fangled IBM 
PC/XTs and integrate office systems with aforementioned DBs and similar. 
After all that, please excuse me whilst I take a grandpa-snooze...



The question is broad. What do you want to do once an interface can be 
found, eg do you merely want a one-off use to transcribe the old data to 
a new system, do you want to build a front-end interface and 
data-collection application, or is perhaps a back-end MIS analysis your 
goal? The quality of the interface, its speed, its data-handling 
capabilities, etc, etc, will all influence...



I haven't heard about Enscribe in recent years. My recollection is that 
their direct interfaces were Java-based. Python offers a JDBC 
"connector" which may be worth investigating. There are also other 
new/improved/faster/super libraries, eg JayDeBeAPI - see PyPi. See also 
Attunity (if still available, eg 
http://whp-aus2.cold.extweb.hp.com/pub/nonstop/ccc/apr0110.pdf).


HP pursued various 'modernisation' proposals, which may be worth review, 
eg using SOAP/micro-services and XML/interchange.


The comp.sys.tandem forum discussed ideas (five years ago): 
https://groups.google.com/forum/#!topic/comp.sys.tandem/dG2t9faPzWg


The lingua-franca of DB inter-connection is probably ODBC, and thus the 
Python ODBC connector.



Trusting these give some food-for-thought...
--
Regards =dn
--
https://mail.python.org/mailman/listinfo/python-list