Re: installing Doorstop on macOS (for RTEMS use)

[Andrew Butterfield]

Hi Sebastian,

I just did option 3 (python.org ) again on another iMac - 
very straightforward- my recommendation.

Regards, Andrew

> On 30 Oct 2019, at 13:24, Sebastian Huber 
>  wrote:
> 
> On 25/10/2019 01:18, Chris Johns wrote:
>> On 24/10/19 9:52 pm, Andrew Butterfield wrote:
>>>   I got around to doing a doorstop install that does not rely on homebrew,
>>> using the python.org  distribution for 3.8
>>> 
>>> Everything worked fine - python3 is installed in /Library just like the OS X
>>> native python 2.7
>>> Doorstop runs just fine too.
>> Excellent and thanks for this. I think this or the other solution that was
>> posted should work. This means I cannot see any blockers for Doorstop on our
>> supported hosts.
> 
> Ok, great. Thanks for all the testing and other valuable input.
> 
> I think on macOS we have now five options:
> 
> 1. homebrew
> 
> 2. MacPorts
> 
> 3. python.org installer
> 
> 4. pyenv
> 
> 5. wait for Apple to ship a Python 3
> 
> We need a recommendation for the user manual.
> 
> -- 
> Sebastian Huber, embedded brains GmbH
> 
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> Phone   : +49 89 189 47 41-16
> Fax : +49 89 189 47 41-09
> E-Mail  : sebastian.hu...@embedded-brains.de
> PGP : Public key available on request.
> 
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users


Andrew Butterfield Tel: +353-1-896-2517 Fax: +353-1-677-2204
Lero@TCD, Head of Foundations & Methods Research Group
School of Computer Science and Statistics,
Room G.39, O'Reilly Institute, Trinity College, University of Dublin
 http://www.scss.tcd.ie/Andrew.Butterfield/


___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: installing Doorstop on macOS (for RTEMS use)

[Chris Johns]

On 31/10/19 5:21 pm, Sebastian Huber wrote:
> On 30/10/2019 21:39, Chris Johns wrote:
>> On 31/10/19 12:24 am, Sebastian Huber wrote:
>>> On 25/10/2019 01:18, Chris Johns wrote:
 On 24/10/19 9:52 pm, Andrew Butterfield wrote:
>     I got around to doing a doorstop install that does not rely on 
> homebrew,
> using the python.org  distribution for 3.8
>
> Everything worked fine - python3 is installed in /Library just like the 
> OS X
> native python 2.7
> Doorstop runs just fine too.

 Excellent and thanks for this. I think this or the other solution that was
 posted should work. This means I cannot see any blockers for Doorstop on 
 our
 supported hosts.
>>>
>>> Ok, great. Thanks for all the testing and other valuable input.
>>>
>>> I think on macOS we have now five options:
>>>
>>> 1. homebrew
>>>
>>> 2. MacPorts
>>>
>>> 3. python.org installer
>>>
>>> 4. pyenv
>>>
>>> 5. wait for Apple to ship a Python 3
>>>
>>> We need a recommendation for the user manual.
>>>
>>
>> I suggest 3. because it is the simplest to do and it does not step on global
>> paths.
> 
> Ok.
> 
>>
>> Can we assume Doorstop is only needed if developing or maintaining RTEMS?
> 
> Yes, definitely.
> 
> You mean the user manual is not the right place to add Python 3.6+ to the host
> computer requirements? We could add this to the RTEMS Software Engineering 
> manual.
> 

Good question. If there is nothing in the User Manual related to developing or
maintaining RTEMS then yes the eng manual would be the correct place. I am sure
we will find other things that are specific to each host. For example I will
need to add a section to the eng manual on the release procedure and this has a
range of specific packages that are needed.

Chris
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: installing Doorstop on macOS (for RTEMS use)

[Chris Johns]

On 31/10/19 12:24 am, Sebastian Huber wrote:
> On 25/10/2019 01:18, Chris Johns wrote:
>> On 24/10/19 9:52 pm, Andrew Butterfield wrote:
>>>    I got around to doing a doorstop install that does not rely on homebrew,
>>> using the python.org  distribution for 3.8
>>>
>>> Everything worked fine - python3 is installed in /Library just like the OS X
>>> native python 2.7
>>> Doorstop runs just fine too.
>>
>> Excellent and thanks for this. I think this or the other solution that was
>> posted should work. This means I cannot see any blockers for Doorstop on our
>> supported hosts.
> 
> Ok, great. Thanks for all the testing and other valuable input.
> 
> I think on macOS we have now five options:
> 
> 1. homebrew
> 
> 2. MacPorts
> 
> 3. python.org installer
> 
> 4. pyenv
> 
> 5. wait for Apple to ship a Python 3
> 
> We need a recommendation for the user manual.
> 

I suggest 3. because it is the simplest to do and it does not step on global 
paths.

Can we assume Doorstop is only needed if developing or maintaining RTEMS?

Chris
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: installing Doorstop on macOS (for RTEMS use)

[Sebastian Huber]

On 25/10/2019 01:18, Chris Johns wrote:

On 24/10/19 9:52 pm, Andrew Butterfield wrote:

   I got around to doing a doorstop install that does not rely on homebrew,
using the python.org  distribution for 3.8

Everything worked fine - python3 is installed in /Library just like the OS X
native python 2.7
Doorstop runs just fine too.


Excellent and thanks for this. I think this or the other solution that was
posted should work. This means I cannot see any blockers for Doorstop on our
supported hosts.


Ok, great. Thanks for all the testing and other valuable input.

I think on macOS we have now five options:

1. homebrew

2. MacPorts

3. python.org installer

4. pyenv

5. wait for Apple to ship a Python 3

We need a recommendation for the user manual.

--
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: installing Doorstop on macOS (for RTEMS use)

[Chris Johns]

On 24/10/19 9:52 pm, Andrew Butterfield wrote:
>   I got around to doing a doorstop install that does not rely on homebrew,
> using the python.org  distribution for 3.8
> 
> Everything worked fine - python3 is installed in /Library just like the OS X
> native python 2.7
> Doorstop runs just fine too.

Excellent and thanks for this. I think this or the other solution that was
posted should work. This means I cannot see any blockers for Doorstop on our
supported hosts.

Chris
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: installing Doorstop on macOS (for RTEMS use)

[Andrew Butterfield]

Hi Chris,

  I got around to doing a doorstop install that does not rely on homebrew,
using the python.org  distribution for 3.8

Everything worked fine - python3 is installed in /Library just like the OS X 
native python 2.7
Doorstop runs just fine too.

Regards, Andrew

> On 14 Oct 2019, at 18:49, Chris Johns  wrote:
> 
> On 11/10/19 5:23 pm, Sebastian Huber wrote:
>> Hello Chris,
>> 
>> I know that you don't like homebrew based solutions on macOS.
> 
> I do not mind homebrew or macports however for RTEMS is not practical to 
> support
> them.
> 
>> The reasons for this are understandable.
> 
> Thanks
> 
>> This is why I suggested to use the installer from python.org:
>> 
>> https://lists.rtems.org/pipermail/users/2019-October/067192.html
>> 
>> There are Python 3 installers available for macOS from python.org:
>> 
>> https://www.python.org/downloads/mac-osx/
> 
> For developers or users making changes to RTEMS this is fine.
> 
>> According to the pip project site it is already installed for Python 2 
>> >=2.7.9
>> or Python 3 >=3.4:
>> 
>> https://pip.pypa.io/en/stable/installing/
>> 
>> For example to install Python 3.7.4 on macOS you can use:
>> 
>> https://www.python.org/ftp/python/3.7.4/python-3.7.4-macosx10.9.pkg
>> 
>> I don't have a Mac and cannot test this.
>> 
>> The Python 2.7 end of life is in 2 months and 20 days (January 1, 2020). The
>> first Python 3 release was in 2008. Are there plans from Apple to update 
>> their
>> Python support in Xcode to a state of the art version?
> 
> I do not know what Apples has planed. I suppose at some point they will have 
> too.
> 
>> Using the doorstop tool
>> is not absolutely necessary right now. The file format is so easy, you can do
>> almost everything with a text editor by hand (and scripts). What you cannot
>> easily do is the calculation of the fingerprint, however, this can be done by
>> the one who commits a patch. So, in case a Python 3 support with pipenv is on
>> the Apple roadmap for the next year, this would make this easier.
> 
> This sounds reasonable.
> 
> Chris


Andrew Butterfield Tel: +353-1-896-2517 Fax: +353-1-677-2204
Lero@TCD, Head of Foundations & Methods Research Group
School of Computer Science and Statistics,
Room G.39, O'Reilly Institute, Trinity College, University of Dublin
 http://www.scss.tcd.ie/Andrew.Butterfield/


___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: installing Doorstop on macOS (for RTEMS use)

[Chris Johns]

On 16/10/19 12:57 am, Stanislav Pankevich wrote:
> Hello everyone,
> 
> Maybe I am too late to join this discussion but as far as I followed
> this thread, no one has mentioned using https://github.com/pyenv/pyenv
> to install Python 3 and its dependencies on macOS.

You are not too late and thanks for taking the time to send this email. The
pyenv tools looks nice and I will take a close look.

> Actually, I try to avoid using any of the Ruby, Python or Node system
> installations provided by Apple. Instead, I use pyenv for Python and
> similar projects for other languages.

I can understand this.

> Given that you have a folder where you want to have Python 3
> available, you simply put a .python-version file with the Python
> version you need. After that, you can install and use the needed
> Python 3 version provided to you by pyenv.
> 
> Hope this is useful.

Yes this is useful and I may come back to you if I need a hand. I hope that is 
OK?

Chris
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: installing Doorstop on macOS (for RTEMS use)

[Chris Johns]

On 16/10/19 8:51 am, Peter Dufault wrote:
>> On Oct 14, 2019, at 13:49 , Chris Johns  wrote:
>>
>> On 11/10/19 5:23 pm, Sebastian Huber wrote:
>>> Hello Chris,
>>>
>>> I know that you don't like homebrew based solutions on macOS.
>>
>> I do not mind homebrew or macports however for RTEMS is not practical to 
>> support
>> them.
> 
> I'm a MacOS user and lapsed *BSD committer.  The majority of MacOS users 
> working with RTEMS will have a VM that they will use for RTEMS development.

I do not use a VM on MacOS and much prefer to develop and run my RTEMS
development as a native environment. I am currently traveling with a Mac laptop
and working on things natively without the need to start, stop and have a
resource hungry VM spinning away all the time. My battery life is reasonably
good and the laptop is nice and responsive.

I think maintaining a VM for me on a Mac is more work than maintaining RTEMS on
MacOS for the project :)

> The homebrew and macports solutions to obtain compatible packages only 
> complicate the issue.  How many Mac users who are working on RTEMS can't work 
> in a VM running CentOS, and how many don't have a machine that allows that?  
> Let me know if I'm wrong.

I do not know if are wrong and what you suggest is a reasonable and valid way
for some users to work with RTEMS but I do not think having it as the
recommended option is where we should head. I for one would not want to keep
such a VM around to test and make sure.
> This is different from e.g. mingw support, where I think the tools need to 
> work as plug-ins.

I know of at least one person who runs CentOS in a VM on Windows as their
development environment. I think their VM disk image corrupted recently, I hope
they had a back up one of the environments or both or something.

I am sure we can resolve the issue of Python3 on MacOS. There are solutions, we
just need to review the options and select the one that best suites our needs.

Chris
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: installing Doorstop on macOS (for RTEMS use)

[Chris Johns]

On 11/10/19 5:23 pm, Sebastian Huber wrote:
> Hello Chris,
> 
> I know that you don't like homebrew based solutions on macOS.

I do not mind homebrew or macports however for RTEMS is not practical to support
them.

> The reasons for this are understandable.

Thanks

> This is why I suggested to use the installer from python.org:
> 
> https://lists.rtems.org/pipermail/users/2019-October/067192.html
> 
> There are Python 3 installers available for macOS from python.org:
> 
> https://www.python.org/downloads/mac-osx/

For developers or users making changes to RTEMS this is fine.

> According to the pip project site it is already installed for Python 2 >=2.7.9
> or Python 3 >=3.4:
> 
> https://pip.pypa.io/en/stable/installing/
> 
> For example to install Python 3.7.4 on macOS you can use:
> 
> https://www.python.org/ftp/python/3.7.4/python-3.7.4-macosx10.9.pkg
> 
> I don't have a Mac and cannot test this.
> 
> The Python 2.7 end of life is in 2 months and 20 days (January 1, 2020). The
> first Python 3 release was in 2008. Are there plans from Apple to update their
> Python support in Xcode to a state of the art version?

I do not know what Apples has planed. I suppose at some point they will have 
too.

> Using the doorstop tool
> is not absolutely necessary right now. The file format is so easy, you can do
> almost everything with a text editor by hand (and scripts). What you cannot
> easily do is the calculation of the fingerprint, however, this can be done by
> the one who commits a patch. So, in case a Python 3 support with pipenv is on
> the Apple roadmap for the next year, this would make this easier.

This sounds reasonable.

Chris
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: installing Doorstop on macOS (for RTEMS use)

[Chris Johns]

On 14/10/19 4:07 pm, Sebastian Huber wrote:
> On 13/10/2019 11:15, Chris Johns wrote:
>> On 12/10/19 8:08 am, Joel Sherrill wrote:
>>> On Fri, Oct 11, 2019, 3:40 PM Gedare Bloom >> > wrote:
>>>
>>>  On Thu, Oct 10, 2019 at 8:34 AM Andrew Butterfield
>>>  >> >
>>> wrote:
>>>  >
>>>  > Dear RTEMS Users,
>>>  >
>>>  >  Sebastian Huber asked me to check the availability of Doorstop
>>>  (https://pypi.org/project/doorstop/) for macOS, and to report my 
>>> experience
>>>  on this mailing list.
>>>  >
>>>  >  It is planned to use this for RTEMS requirements in the RTEMS
>>>  qualification project.
>>>  >
>>>  I would like to clarify and request confirmation that the use of
>>>  Doorstop tools will not be required for "casual" RTEMS users.
>>
>> It is the view I have. I cannot confirm the view of others.
>>
>>> It will
>>>  be necessary for RTEMS maintainers and for users who want to be
>>>  involved in the pre-certification effort. Correct?
>>
>> Great question. I do not know.
> 
> Yes, RTEMS maintainers and users who want to be involved in the
> pre-qualification effort will have to work with Doorstop and the specification
> items. RTEMS users will not get in touch with Doorstop directly and don't have
> to install it.

Great. It is good to know Doorstop itself holds no state information and the
YAML files that control the build are the same files Doorstop uses. I am fine
with developers and maintainer needing to install and manage more dependencies
including python3 than a standard user.

>>> I have identified some roles for using RTEMS and we may want to discuss 
>>> those at
>>> another time.
>>
>> Lets then leave this aside until we get to discuss them :)
>>
>>> If this is required when you bootstrap RTEMS, I would consider it something
>>> required by a casual user given that we expect everyone to do that.
>>
>> Then I suggest it does not become part of any bootstrap process.
> 
> What do you mean with bootstrap? Calling ./boostrap or ./rtems-bootstrap? My 
> new
> build system prototype doesn't need such a step. You can clone the repository
> and directly start with "./waf configure". You just have to provide a
> "build.ini" file, but this is more or less the same as the old configure 
> command
> line options.
> 

Nice, this makes things simpler.

Chris
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: installing Doorstop on macOS (for RTEMS use)

[Chris Johns]

On 12/10/19 8:08 am, Joel Sherrill wrote:
> On Fri, Oct 11, 2019, 3:40 PM Gedare Bloom  > wrote:
> 
> On Thu, Oct 10, 2019 at 8:34 AM Andrew Butterfield
> mailto:andrew.butterfi...@scss.tcd.ie>> 
> wrote:
> >
> > Dear RTEMS Users,
> >
> >  Sebastian Huber asked me to check the availability of Doorstop
> (https://pypi.org/project/doorstop/) for macOS, and to report my 
> experience
> on this mailing list.
> >
> >  It is planned to use this for RTEMS requirements in the RTEMS
> qualification project.
> >
> I would like to clarify and request confirmation that the use of
> Doorstop tools will not be required for "casual" RTEMS users.

It is the view I have. I cannot confirm the view of others.

> It will
> be necessary for RTEMS maintainers and for users who want to be
> involved in the pre-certification effort. Correct?

Great question. I do not know.

> I have identified some roles for using RTEMS and we may want to discuss those 
> at
> another time.

Lets then leave this aside until we get to discuss them :)

> If this is required when you bootstrap RTEMS, I would consider it something
> required by a casual user given that we expect everyone to do that.

Then I suggest it does not become part of any bootstrap process.

Chris
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: installing Doorstop on macOS (for RTEMS use)

[Joel Sherrill]

On Fri, Oct 11, 2019, 3:40 PM Gedare Bloom  wrote:

> On Thu, Oct 10, 2019 at 8:34 AM Andrew Butterfield
>  wrote:
> >
> > Dear RTEMS Users,
> >
> >  Sebastian Huber asked me to check the availability of Doorstop (
> https://pypi.org/project/doorstop/) for macOS, and to report my
> experience on this mailing list.
> >
> >  It is planned to use this for RTEMS requirements in the RTEMS
> qualification project.
> >
> I would like to clarify and request confirmation that the use of
> Doorstop tools will not be required for "casual" RTEMS users. It will
> be necessary for RTEMS maintainers and for users who want to be
> involved in the pre-certification effort. Correct?
>

I have identified some roles for using RTEMS and we may want to discuss
those at another time.

If this is required when you bootstrap RTEMS, I would consider it something
required by a casual user given that we expect everyone to do that.


> > It turned out to install really easily on my machine, in few 10s of
> seconds
> >
> > The following is a record of my system setup w.r.t. python,
> > and the installation process.
> >
> >
> > Hardware/OS: MacBook Pro, 2.8Ghz i7, 16GB ram, 500GB flash, macOS 10.14.6
> >
> > python state:
> >
> > ~> which python
> > /usr/local/bin/python
> > ~> python --version
> > Python 2.7.16
> >
> > ~> which python3
> > /usr/local/bin/python3
> > ~> python3 --version
> > Python 3.7.4
> >
> > ~> which pip
> > /usr/local/bin/pip
> > ~> pip --version
> > pip 19.0.3 from /usr/local/lib/python2.7/site-packages/pip (python 2.7)
> >
> > ~> which pip3
> > /usr/local/bin/pip3
> > ~> pip3 --version
> > pip 19.1.1 from /usr/local/lib/python3.7/site-packages/pip (python 3.7)
> >
> > Both pythons are 'brew' versions. Chris Johns said we should only use
> > the native installed versions. However other tools I may choose to used
> > often need to be installed using 'brew' and you would be amazed how many
> > of those have python as a (brew) dependency.
> >
> > Looking in /System/Library/Frameworks/Python.framework/Versions
> > we find folders 2.3 2.5 2.6 2.7 Current
> > Current contains 2.7.10
> >
> > Attempt 1 - use the 'brew' versions
> >
> > >pip3 install doorstop
> >
> > --- log -
> > Collecting doorstop
> >   Downloading
> https://files.pythonhosted.org/packages/d3/20/315248b287ee6b3055d23d02c00801a38f44a0baf4ebd225c63bf66c0812/doorstop-1.6-py3-none-any.whl
> (276kB)
> >  || 276kB 2.6MB/s
> > Collecting Markdown<3,>=2 (from doorstop)
> >   Downloading
> https://files.pythonhosted.org/packages/6d/7d/488b90f470b96531a3f5788cf12a93332f543dbab13c423a5e7ce96a0493/Markdown-2.6.11-py2.py3-none-any.whl
> (78kB)
> >  || 81kB 20.2MB/s
> > Collecting plantuml-markdown<4.0,>=3.0 (from doorstop)
> >   Downloading
> https://files.pythonhosted.org/packages/9a/62/f23ad5e2cf3b196d253cba258bc97862de3057d4861c52df485be11ca060/plantuml_markdown-3.1.3-py3-none-any.whl
> > Requirement already satisfied: PyYAML<6.0,>=5.1 in
> /usr/local/lib/python3.7/site-packages (from doorstop) (5.1)
> > Collecting openpyxl<3.0,>=2.6 (from doorstop)
> >   Downloading
> https://files.pythonhosted.org/packages/d6/26/eb28e975b7a37aad38d7ec4f7a0f652bdee6ecf36e6bd06f473c5af9b87b/openpyxl-2.6.4.tar.gz
> (173kB)
> >  || 174kB 33.4MB/s
> > Collecting pyficache==0.3.1 (from doorstop)
> >   Downloading
> https://files.pythonhosted.org/packages/5a/97/859698b53eea27b92746105170417d881bfe99304626efc770d505323be4/pyficache-0.3.1.tar.gz
> > Collecting mdx_outline<2.0.0,>=1.3.0 (from doorstop)
> >   Downloading
> https://files.pythonhosted.org/packages/01/88/2c978ced5a64a5fb6be8a788bac64e2cc5eaf603535ccec2b51cd98a388c/mdx_outline-1.3.0.tar.gz
> > Collecting bottle==0.12.13 (from doorstop)
> >   Downloading
> https://files.pythonhosted.org/packages/bd/99/04dc59ced52a8261ee0f965a8968717a255ea84a36013e527944dbf3468c/bottle-0.12.13.tar.gz
> (70kB)
> >  || 71kB 20.0MB/s
> > Collecting python-markdown-math==0.6 (from doorstop)
> >   Downloading
> https://files.pythonhosted.org/packages/7c/81/2c86570437821d77b90a6d939d54e11b507b71785850840a5e56d8febeca/python_markdown_math-0.6-py2.py3-none-any.whl
> > Requirement already satisfied: requests<3,>=2 in
> /usr/local/lib/python3.7/site-packages (from doorstop) (2.22.0)
> > Collecting plantuml (from plantuml-markdown<4.0,>=3.0->doorstop)
> >   Downloading
> https://files.pythonhosted.org/packages/1e/92/0754877e9f3752216717f53ef3c66b238ffaa4043402f4ecde1173c8d0d5/plantuml-0.2.1-py3-none-any.whl
> > Collecting jdcal (from openpyxl<3.0,>=2.6->doorstop)
> >   Downloading
> https://files.pythonhosted.org/packages/f0/da/572cbc0bc582390480bbd7c4e93d14dc46079778ed915b505dc494b37c57/jdcal-1.4.1-py2.py3-none-any.whl
> > Collecting et_xmlfile (from openpyxl<3.0,>=2.6->doorstop)
> >   Downloading
> 

Re: installing Doorstop on macOS (for RTEMS use)

[Gedare Bloom]

On Thu, Oct 10, 2019 at 8:34 AM Andrew Butterfield
 wrote:
>
> Dear RTEMS Users,
>
>  Sebastian Huber asked me to check the availability of Doorstop 
> (https://pypi.org/project/doorstop/) for macOS, and to report my experience 
> on this mailing list.
>
>  It is planned to use this for RTEMS requirements in the RTEMS qualification 
> project.
>
I would like to clarify and request confirmation that the use of
Doorstop tools will not be required for "casual" RTEMS users. It will
be necessary for RTEMS maintainers and for users who want to be
involved in the pre-certification effort. Correct?

> It turned out to install really easily on my machine, in few 10s of seconds
>
> The following is a record of my system setup w.r.t. python,
> and the installation process.
>
>
> Hardware/OS: MacBook Pro, 2.8Ghz i7, 16GB ram, 500GB flash, macOS 10.14.6
>
> python state:
>
> ~> which python
> /usr/local/bin/python
> ~> python --version
> Python 2.7.16
>
> ~> which python3
> /usr/local/bin/python3
> ~> python3 --version
> Python 3.7.4
>
> ~> which pip
> /usr/local/bin/pip
> ~> pip --version
> pip 19.0.3 from /usr/local/lib/python2.7/site-packages/pip (python 2.7)
>
> ~> which pip3
> /usr/local/bin/pip3
> ~> pip3 --version
> pip 19.1.1 from /usr/local/lib/python3.7/site-packages/pip (python 3.7)
>
> Both pythons are 'brew' versions. Chris Johns said we should only use
> the native installed versions. However other tools I may choose to used
> often need to be installed using 'brew' and you would be amazed how many
> of those have python as a (brew) dependency.
>
> Looking in /System/Library/Frameworks/Python.framework/Versions
> we find folders 2.3 2.5 2.6 2.7 Current
> Current contains 2.7.10
>
> Attempt 1 - use the 'brew' versions
>
> >pip3 install doorstop
>
> --- log -
> Collecting doorstop
>   Downloading 
> https://files.pythonhosted.org/packages/d3/20/315248b287ee6b3055d23d02c00801a38f44a0baf4ebd225c63bf66c0812/doorstop-1.6-py3-none-any.whl
>  (276kB)
>  || 276kB 2.6MB/s
> Collecting Markdown<3,>=2 (from doorstop)
>   Downloading 
> https://files.pythonhosted.org/packages/6d/7d/488b90f470b96531a3f5788cf12a93332f543dbab13c423a5e7ce96a0493/Markdown-2.6.11-py2.py3-none-any.whl
>  (78kB)
>  || 81kB 20.2MB/s
> Collecting plantuml-markdown<4.0,>=3.0 (from doorstop)
>   Downloading 
> https://files.pythonhosted.org/packages/9a/62/f23ad5e2cf3b196d253cba258bc97862de3057d4861c52df485be11ca060/plantuml_markdown-3.1.3-py3-none-any.whl
> Requirement already satisfied: PyYAML<6.0,>=5.1 in 
> /usr/local/lib/python3.7/site-packages (from doorstop) (5.1)
> Collecting openpyxl<3.0,>=2.6 (from doorstop)
>   Downloading 
> https://files.pythonhosted.org/packages/d6/26/eb28e975b7a37aad38d7ec4f7a0f652bdee6ecf36e6bd06f473c5af9b87b/openpyxl-2.6.4.tar.gz
>  (173kB)
>  || 174kB 33.4MB/s
> Collecting pyficache==0.3.1 (from doorstop)
>   Downloading 
> https://files.pythonhosted.org/packages/5a/97/859698b53eea27b92746105170417d881bfe99304626efc770d505323be4/pyficache-0.3.1.tar.gz
> Collecting mdx_outline<2.0.0,>=1.3.0 (from doorstop)
>   Downloading 
> https://files.pythonhosted.org/packages/01/88/2c978ced5a64a5fb6be8a788bac64e2cc5eaf603535ccec2b51cd98a388c/mdx_outline-1.3.0.tar.gz
> Collecting bottle==0.12.13 (from doorstop)
>   Downloading 
> https://files.pythonhosted.org/packages/bd/99/04dc59ced52a8261ee0f965a8968717a255ea84a36013e527944dbf3468c/bottle-0.12.13.tar.gz
>  (70kB)
>  || 71kB 20.0MB/s
> Collecting python-markdown-math==0.6 (from doorstop)
>   Downloading 
> https://files.pythonhosted.org/packages/7c/81/2c86570437821d77b90a6d939d54e11b507b71785850840a5e56d8febeca/python_markdown_math-0.6-py2.py3-none-any.whl
> Requirement already satisfied: requests<3,>=2 in 
> /usr/local/lib/python3.7/site-packages (from doorstop) (2.22.0)
> Collecting plantuml (from plantuml-markdown<4.0,>=3.0->doorstop)
>   Downloading 
> https://files.pythonhosted.org/packages/1e/92/0754877e9f3752216717f53ef3c66b238ffaa4043402f4ecde1173c8d0d5/plantuml-0.2.1-py3-none-any.whl
> Collecting jdcal (from openpyxl<3.0,>=2.6->doorstop)
>   Downloading 
> https://files.pythonhosted.org/packages/f0/da/572cbc0bc582390480bbd7c4e93d14dc46079778ed915b505dc494b37c57/jdcal-1.4.1-py2.py3-none-any.whl
> Collecting et_xmlfile (from openpyxl<3.0,>=2.6->doorstop)
>   Downloading 
> https://files.pythonhosted.org/packages/22/28/a99c42aea746e18382ad9fb36f64c1c1f04216f41797f2f0fa567da11388/et_xmlfile-1.0.1.tar.gz
> Collecting coverage (from pyficache==0.3.1->doorstop)
>   Downloading 
> https://files.pythonhosted.org/packages/93/07/8302163cdbe2008441aa69f2119750110fde15ffd8a56a687311b143365a/coverage-4.5.4-cp37-cp37m-macosx_10_13_x86_64.whl
>  (181kB)
>  || 184kB 31.0MB/s
> Requirement already satisfied: pygments>=2.0 in 
> /usr/local/lib/python3.7/site-packages (from 

Re: installing Doorstop on macOS (for RTEMS use)

[Sebastian Huber]

Hello Chris,

I know that you don't like homebrew based solutions on macOS. The 
reasons for this are understandable. This is why I suggested to use the 
installer from python.org:


https://lists.rtems.org/pipermail/users/2019-October/067192.html

There are Python 3 installers available for macOS from python.org:

https://www.python.org/downloads/mac-osx/

According to the pip project site it is already installed for Python 2 
>=2.7.9 or Python 3 >=3.4:


https://pip.pypa.io/en/stable/installing/

For example to install Python 3.7.4 on macOS you can use:

https://www.python.org/ftp/python/3.7.4/python-3.7.4-macosx10.9.pkg

I don't have a Mac and cannot test this.

The Python 2.7 end of life is in 2 months and 20 days (January 1, 2020). 
The first Python 3 release was in 2008. Are there plans from Apple to 
update their Python support in Xcode to a state of the art version? 
Using the doorstop tool is not absolutely necessary right now. The file 
format is so easy, you can do almost everything with a text editor by 
hand (and scripts). What you cannot easily do is the calculation of the 
fingerprint, however, this can be done by the one who commits a patch. 
So, in case a Python 3 support with pipenv is on the Apple roadmap for 
the next year, this would make this easier.


--
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: installing Doorstop on macOS (for RTEMS use)

[Joel Sherrill]

On Thu, Oct 10, 2019 at 4:26 PM Chris Johns  wrote:

> On 11/10/19 1:15 am, Andrew Butterfield wrote:
> > Dear RTEMS Users,
> >
> >  Sebastian Huber asked me to check the availability of Doorstop (
> https://pypi.org/project/doorstop/) for macOS, and to report my
> experience on this mailing list.
> >
> >  It is planned to use this for RTEMS requirements in the RTEMS
> qualification project.
> >
> > It turned out to install really easily on my machine, in few 10s of
> seconds
> >
>
> 
>
> > The following is a record of my system setup w.r.t. python,
> > and the installation process.
> >
> >
> > Hardware/OS: MacBook Pro, 2.8Ghz i7, 16GB ram, 500GB flash, macOS 10.14.6
> >
> > python state:
> >
> > ~> which python
> > /usr/local/bin/python
>   ^^
> Hmmm ...
> > ~> python --version
> > Python 2.7.16
> >
> > ~> which python3
> > /usr/local/bin/python3
> > ~> python3 --version
> > Python 3.7.4
> >
> > ~> which pip
> > /usr/local/bin/pip
> > ~> pip --version
> > pip 19.0.3 from /usr/local/lib/python2.7/site-packages/pip (python 2.7)
> >
> > ~> which pip3
> > /usr/local/bin/pip3
> > ~> pip3 --version
> > pip 19.1.1 from /usr/local/lib/python3.7/site-packages/pip (python 3.7)
> >
> > Both pythons are 'brew' versions. Chris Johns said we should only use
> > the native installed versions.
>
> I am actually saying this is currently all we need to build our tool set. I
> cannot afford to have homebrew or macport packages installed because what I
> might have installed at any point in time may effect the building of the
> tools
> and I would never know and if I step on a bug where is the problem.
>
> I do not have the time or resources to maintain our tool sets when
> building with
> homebrew and macports packages installed. If an issue is found is the
> problem in
> the tools or an installed package. I would need to determine which part
> and look
> for a solution. I do not want to become a Mac package maintainer or a MacOS
> expert in a wide number of open source packages.
>
> I have found the Xcode command line tools from Apple to be stable over a
> number
> of years and I have found Apple and GCC to be responsive to any issues I
> raise.
> I have raised a number of bugs with both parties and in each case I seem
> to be
> one of first to uncover them.
>
> > However other tools I may choose to used
> > often need to be installed using 'brew' and you would be amazed how many
> > of those have python as a (brew) dependency.
>
> This is one alternative and one that brings other often more complicated
> issues.
>
> How do we managing building all the tools for all architectures making
> sure they
> build and work with any mix of installed packages at whatever versions they
> have? Our mailing list has a number of posts about the RSB not building
> tools on
> MacOS and my first question is always "are any packages installed from
> homebrew
> or macports?" and it normally ends up being related.
>
> I have no idea how you would control and specify a set of suitable
> packages for
> homebrew or macports. I do know if you use a specific version of Xcode on a
> specific version of MacOS you will end up with the same tool set I have
> built
> and tested. I think this is important and important for our users.
>

I'm a CentOS user and there is a parallel type of situation. I avoid using
odd repositories
and have resisted using the official "software collections" which include a
newer Python.
CentOS 7 ships by default with Python 2.7.5 and I will stay with that.

Disclaimer: For Sphinx support, I use the Python 3 software collection.
Sphinx's need for
a newer Python is what drove me off CentOS 6.

Sticking with base installs and official sources of packages keeps us as
maintainers
inline with what "real" users have. Large organization uses in the US are
CentOS/RHEL
users with strict security controls. Those are our corporate and scientific
users. I try hard
to suffer as much as they do. They can't just switch to Mint, FreeBSD, or
install something
from an odd repo.

RTEMS isn't a hobby (or toy) project and most of its users are stuck in
serious industrial
settings. As core developers, we have to respect that and suffer along.

--joel


>
> Chris
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
>
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: installing Doorstop on macOS (for RTEMS use)

[Chris Johns]

On 11/10/19 1:15 am, Andrew Butterfield wrote:
> Dear RTEMS Users,
> 
>  Sebastian Huber asked me to check the availability of Doorstop 
> (https://pypi.org/project/doorstop/) for macOS, and to report my experience 
> on this mailing list.
> 
>  It is planned to use this for RTEMS requirements in the RTEMS qualification 
> project.
> 
> It turned out to install really easily on my machine, in few 10s of seconds
> 



> The following is a record of my system setup w.r.t. python,
> and the installation process.
> 
> 
> Hardware/OS: MacBook Pro, 2.8Ghz i7, 16GB ram, 500GB flash, macOS 10.14.6
> 
> python state:
> 
> ~> which python
> /usr/local/bin/python
  ^^
Hmmm ...
> ~> python --version
> Python 2.7.16
> 
> ~> which python3
> /usr/local/bin/python3
> ~> python3 --version
> Python 3.7.4
> 
> ~> which pip
> /usr/local/bin/pip
> ~> pip --version
> pip 19.0.3 from /usr/local/lib/python2.7/site-packages/pip (python 2.7)
> 
> ~> which pip3
> /usr/local/bin/pip3
> ~> pip3 --version
> pip 19.1.1 from /usr/local/lib/python3.7/site-packages/pip (python 3.7)
>
> Both pythons are 'brew' versions. Chris Johns said we should only use
> the native installed versions.

I am actually saying this is currently all we need to build our tool set. I
cannot afford to have homebrew or macport packages installed because what I
might have installed at any point in time may effect the building of the tools
and I would never know and if I step on a bug where is the problem.

I do not have the time or resources to maintain our tool sets when building with
homebrew and macports packages installed. If an issue is found is the problem in
the tools or an installed package. I would need to determine which part and look
for a solution. I do not want to become a Mac package maintainer or a MacOS
expert in a wide number of open source packages.

I have found the Xcode command line tools from Apple to be stable over a number
of years and I have found Apple and GCC to be responsive to any issues I raise.
I have raised a number of bugs with both parties and in each case I seem to be
one of first to uncover them.

> However other tools I may choose to used
> often need to be installed using 'brew' and you would be amazed how many
> of those have python as a (brew) dependency.

This is one alternative and one that brings other often more complicated issues.

How do we managing building all the tools for all architectures making sure they
build and work with any mix of installed packages at whatever versions they
have? Our mailing list has a number of posts about the RSB not building tools on
MacOS and my first question is always "are any packages installed from homebrew
or macports?" and it normally ends up being related.

I have no idea how you would control and specify a set of suitable packages for
homebrew or macports. I do know if you use a specific version of Xcode on a
specific version of MacOS you will end up with the same tool set I have built
and tested. I think this is important and important for our users.

Chris
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users