Re: jupyter-2.7 vs. ipython

[pagani laurent via macports-users]

Marius,

I just installed py27-jupyter today, checked the py27-future presence but it 
crashes in a similar way to what Bob reported below :

  py27-futures @3.2.0_0 (active)
  py27-tornado @5.0.1_1 (active)

NICER>jupyter-2.7 notebook
Traceback (most recent call last):
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/jupyter-notebook",
 line 6, in 
from pkg_resources import load_entry_point
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 3195, in 
@_call_aside
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 3179, in _call_aside
f(*args, **kwargs)
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 3208, in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 681, in _build_master
ws.require(__requires__)
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 999, in require
needed = self.resolve(parse_requirements(requirements))
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 885, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'testpath' distribution was not found 
and is required by nbconvert

What’s wrong ?

Thanks
Laurent

> Le 20 mars 2018 à 19:27, Marius Schamschula  a écrit :
> 
> I just posted a ticket for this very issue: 
> https://trac.macports.org/ticket/56111 
> 
> 
>> On Mar 20, 2018, at 1:19 PM, Robert Goldman > > wrote:
>> 
>> I can't tell if this is a bug in MacPorts, or if I have simply misconfigured 
>> something.
>> 
>> When I start up ipython notebook, with python-2.7 as my selected python, 
>> everything works fine, but I get a complaint echoed to the shell:
>> 
>> [TerminalIPythonApp] WARNING | Subcommand `ipython notebook` is deprecated 
>> and will be removed in future versions.
>> [TerminalIPythonApp] WARNING | You likely want to use `jupyter notebook` in 
>> the future
>> All works well, nevertheless, and I'm happy, except for the crabby note from 
>> ipython.
>> 
>> But, if I try to do what the message says, and run jupyter notebook instead, 
>> I get an error:
>> 
>> $ jupyter-2.7 notebook
>> Traceback (most recent call last):
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/jupyter-notebook",
>>  line 6, in 
>> from pkg_resources import load_entry_point
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 3195, in 
>> @_call_aside
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 3179, in _call_aside
>> f(*args, **kwargs)
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 3208, in _initialize_master_working_set
>> working_set = WorkingSet._build_master()
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 681, in _build_master
>> ws.require(__requires__)
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 999, in require
>> needed = self.resolve(parse_requirements(requirements))
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 885, in resolve
>> raise DistributionNotFound(req, requirers)
>> pkg_resources.DistributionNotFound: The 'futures' distribution was not found 
>> and is required by tornado
>> So I was wondering if there's an issue with jupyter or, if somehow I've 
>> gotten things misconfigured.
>> 
>> Thanks
>> 
> 
> Marius
> --
> Marius Schamschula
> 
> 
> 

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: Installing gcc6 on a PPC Mac Mini 10.4 gives me hell

[Michael]

On 2018-03-20, at 2:27 PM, Andreas Falkenhahn  wrote:

>> 
>> Personally, I do not understand why you are still running such an old
>> machine with macOS. 
> 
> It's retro, there doesn't have to be a rational reason for it :-)
> Besides, in the retro scene 10.4 is quite popular because it's the
> last Mac OS capable of running Mac OS 9 software. 

 I also thought that 10.4 was the last version capable of running EOF software.

---
Entertaining minecraft videos
http://YouTube.com/keybounce

Re: jupyter-2.7 vs. ipython

[Nathan Brazil]

In my experience, “jupyter notebook” is the correct startup command.  Here is 
what I do, using Python 2.7:
Install pyenv (https://github.com/pyenv/pyenv)
pyenv install 2.7.14
sudo port install py27-virtualenv
mkdir jupyter
cd jupyter
pyenv virtualenv 2.7.14 jupyter
echo "jupyter" > .python-version
pip install jupyter
jupyter notebook

—

> On Mar 20, 2018, at 11:27 AM, Marius Schamschula  
> wrote:
> 
> I just posted a ticket for this very issue: 
> https://trac.macports.org/ticket/56111 
> 
> 
>> On Mar 20, 2018, at 1:19 PM, Robert Goldman > > wrote:
>> 
>> I can't tell if this is a bug in MacPorts, or if I have simply misconfigured 
>> something.
>> 
>> When I start up ipython notebook, with python-2.7 as my selected python, 
>> everything works fine, but I get a complaint echoed to the shell:
>> 
>> [TerminalIPythonApp] WARNING | Subcommand `ipython notebook` is deprecated 
>> and will be removed in future versions.
>> [TerminalIPythonApp] WARNING | You likely want to use `jupyter notebook` in 
>> the future
>> All works well, nevertheless, and I'm happy, except for the crabby note from 
>> ipython.
>> 
>> But, if I try to do what the message says, and run jupyter notebook instead, 
>> I get an error:
>> 
>> $ jupyter-2.7 notebook
>> Traceback (most recent call last):
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/jupyter-notebook",
>>  line 6, in 
>> from pkg_resources import load_entry_point
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 3195, in 
>> @_call_aside
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 3179, in _call_aside
>> f(*args, **kwargs)
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 3208, in _initialize_master_working_set
>> working_set = WorkingSet._build_master()
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 681, in _build_master
>> ws.require(__requires__)
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 999, in require
>> needed = self.resolve(parse_requirements(requirements))
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 885, in resolve
>> raise DistributionNotFound(req, requirers)
>> pkg_resources.DistributionNotFound: The 'futures' distribution was not found 
>> and is required by tornado
>> So I was wondering if there's an issue with jupyter or, if somehow I've 
>> gotten things misconfigured.
>> 
>> Thanks
>> 
> 
> Marius
> --
> Marius Schamschula
> 
> 
> 

Re: Installing gcc6 on a PPC Mac Mini 10.4 gives me hell

[Bill Cole]

On 21 Mar 2018, at 14:23, miniupnp wrote:


On the other hand, it is also fun to read message about someone afraid
of his hardware burned by a hours long macports build  :)


This is a serious concern. I've had 3 Macs (Cube, G5 iMac, MacBook) that 
got worse at heat dissipation over time to the point that they could no 
longer do anything CPU-heavy for more than about 15 minutes straight 
without the thermal protection halting the system or in the case of the 
Cube, sometimes NOT halting it before a seemingly hardware-generated 
panic. It's not unreasonable to suspect that as thermal paste ages and 
heat sinks get a layer of insulating dust, the baseline thermal wear is 
a bit higher and high-load events become increasingly risky.

Re: Installing gcc6 on a PPC Mac Mini 10.4 gives me hell

[Andreas Falkenhahn]

On 20.03.2018 at 23:51 Ryan Schmidt wrote:

> There is not a great deal of interest in Tiger anymore, but I
> understand that the computers that are still running Tiger are slow
> and are thus the ones that might most benefit from the existence of binaries.

Definitely. Having binaries would be a great benefit for those old
systems.

-- 
Best regards,
 Andreas Falkenhahnmailto:andr...@falkenhahn.com

Re: Installing gcc6 on a PPC Mac Mini 10.4 gives me hell

[miniupnp]

Le 21.03.2018 à 19:29, Daniel J. Luke a écrit :
> On Mar 21, 2018, at 2:23 PM, miniupnp  wrote:
>> It's quite fun to read exhortations to use upgrade to a more recent
>> system. I'm trying to imagine which hacker could spend time to exploit
>> Mac PPC machines to include them in a bitcoin mining botnet ;)
> or DDOS or SPAM or other abusive behavior that makes it harder for others to 
> utilize a shared resource.
>
> but hey - at least you're having fun...
>
> [It's possible to safely use old systems, but it's not trivial. The easiest 
> way to keep that old hardware useful is to run an OS that is still being 
> supported - it's unfortunate that Apple doesn't keep releasing security 
> patches for older systems, but there's nothing that we can do about that].
You seems afraid of our 10.4 machines currently being exploited to abuse
the internet.
Let me reassure your : mine is currently turned off. Of course I would
not use such machine for production use...
I'm pretty sure that a turned off G4 Mac is less likely to send SPAM
than a state of the art intel machine which even "turned off" is still
running the ME.
You also minimize the economics aspects of security. As someone pointed
out, there are very few PowerPC 10.4 around. Even if easier to exploit
than newer system, who would invest in Mac OS 10.4 support for a SPAM
spending botnet ???
I would really want to see some statistics about the amount of DDOS
attacks or SPAM sent depending on OS/architectures.

Re: Installing gcc6 on a PPC Mac Mini 10.4 gives me hell

[Daniel J. Luke]

On Mar 21, 2018, at 2:23 PM, miniupnp  wrote:
> It's quite fun to read exhortations to use upgrade to a more recent
> system. I'm trying to imagine which hacker could spend time to exploit
> Mac PPC machines to include them in a bitcoin mining botnet ;)

or DDOS or SPAM or other abusive behavior that makes it harder for others to 
utilize a shared resource.

but hey - at least you're having fun...

[It's possible to safely use old systems, but it's not trivial. The easiest way 
to keep that old hardware useful is to run an OS that is still being supported 
- it's unfortunate that Apple doesn't keep releasing security patches for older 
systems, but there's nothing that we can do about that].

-- 
Daniel J. Luke

Re: Installing gcc6 on a PPC Mac Mini 10.4 gives me hell

[miniupnp]

I'm one of the guys who run a 10.4 G4 "just because I can". Some call it
retro computing :)
I'm glad macports still supports it and try to help to fix things when a
port is not building on it.

but I'm not expecting the project to spend resources in building
binaries for this kind of system.
When I need something, I just launch the "port install" command before
going to bed and let the build take the time it takes.

It's quite fun to read exhortations to use upgrade to a more recent
system. I'm trying to imagine which hacker could spend time to exploit
Mac PPC machines to include them in a bitcoin mining botnet ;)
On the other hand, it is also fun to read message about someone afraid
of his hardware burned by a hours long macports build  :)

Regards


Le 20.03.2018 à 23:55, Chris Jones a écrit :
>> On 20 Mar 2018, at 8:43 pm, Andreas Falkenhahn  
>> wrote:
>>
>>> On 20.03.2018 at 21:35 Ken Cunningham wrote:
>>>
>>> On 10.5 you installed a prebuilt binary.
>>> gcc6 takes 12 to 24 hrs to build on a PPC machine.
>> Oh my, that's too much for me, I've just hit CTRL-C. Of course this might 
>> leave me with a corrupt installation but I'm just too paranoid about Mac 
>> Ports killing my hardware. 
>>
>> IMHO there really should be prebuilt binaries for 10.4. It's a waste of 
>> energy and resources to have everybody build this on his own...
> The user base still using 10.4 is tiny tending to zero. It simply is not 
> worth the effort.

Re: Installing gcc6 on a PPC Mac Mini 10.4 gives me hell

[Andreas Falkenhahn]

On 21.03.2018 at 00:34 David Strubbe wrote:

> For the record, you can always stop a build by typing CTRL-C, and
> it will not corrupt anything. Only at the install stage are any
> files permanently changed. If you do "port clean" after stopping the
> build, you will be right back where you were before the build.

Thanks, that's good to know!

-- 
Best regards,
 Andreas Falkenhahnmailto:andr...@falkenhahn.com

Re: Installing gcc6 on a PPC Mac Mini 10.4 gives me hell

[Andreas Falkenhahn]

On 20.03.2018 at 23:59 Chris Jones wrote:

> You can call these OSes ‘retro’ if you want, to make it sound good,
> but all they really are, are outdated and insecure.

I've always preferred freedom over security. And by the way, I have
a feeling that with each new Mac OS version the system becomes more and
more curious about me, tries to collect data, hides things from me,
and tries to infantilize me by pretending to know what is good and bad
for me (Gatekeeper anyone?)

In that regard, the older Mac OS versions are really much more pleasant
than the latest releases which seem to take away more and more control
from the user. That might be very good for people without a clue about
computing but for coders it's a pain in the "donkey". 

It's time to regain control - the OS is here to serve, not to spy on me
or impose its will on me :-)

$0.02

-- 
Best regards,
 Andreas Falkenhahnmailto:andr...@falkenhahn.com

Re: Trouble compiling with gcc 4.8 on 10.5 PowerPC

[Kenneth F. Cunningham]

On 2018-03-18, at 8:44 AM, Kenneth F. Cunningham wrote:


>> There's just one little problem remaining: I cannot use gcc-ar-mp-6 because
>> it reports the following error: "Cannot find plugin liblto_plugin.so".
> 

Looks like this is just broken on all MacPorts versions of gcc, for example on 
this Intel 10.7.5 box I have with me now:

$ /opt/local/bin/x86_64-apple-darwin11-gcc-ar-mp-7
/opt/local/bin/x86_64-apple-darwin11-gcc-ar-mp-7: Cannot find plugin 
'liblto_plugin.so'