Re: [ease-dev] Python module loading

["BERNARD, Alain" <alain.bernard@xxxxxxxxxx>]

Hi,

Sounds good! 
IMHO, the proposals 'b' or 'd' are fine. Both introduce a prefix so that there is no chance that EASE namespaces override other namespaces. Between b or d, I don't know, because EASE refers clearly to EASE modules, but for end-users it would be maybe more simple to identify modules loaded from the eclipse world with the 'Eclipse' prefix (as today, no one refers to EGit, which is a project name, but everything in Eclipse refers simply to Git)

I also like your proposal of loading all modules at once. 

Alain

-----Message d'origine-----
De : ease-dev-bounces@xxxxxxxxxxx [mailto:ease-dev-bounces@xxxxxxxxxxx] De la part de Christian Pontesegger
Envoyé : mercredi 5 juillet 2017 11:25
À : ease developer discussions <ease-dev@xxxxxxxxxxx>
Objet : [ease-dev] Python module loading

Hi devs,

today I played a little with python import hooks to see how we can make module loading more python like for EASE developers.

It is relatively simple to use import statements instead of loadModule. 
Now I am reaching out to you python developers to ask how we should organize namespaces here:

instead of

     loadModule("/Platform/Resources")

we could use

a) import Platform.Resources
b) import EASE.Platform.Resources
c) import Eclipse.EASE.Platform.Resources
d) import Eclipse.Platform.Resources
e) ???

What would be a good python-style package name?

We could also think if we allow to import multiple modules at once, eg

     from Platform import *  # loads Resources modules and all other modules from the Platform category


let me know your thoughts

Christian

_______________________________________________
ease-dev mailing list
ease-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ease-dev

This mail has originated outside your organization, either from an external partner or the Global Internet.
Keep this in mind if you answer this message.



The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.