Python 2.7 Support about declarativewidgets

[lbustelo]

@zackmorris is looking into this

[lbustelo]

The priorities of this issue whould be as follow:

1. Enable the use of a Python 2.7+ kernel
2. Enable Python unit tests to run on Python 2.7
3. Verify that there is nothing Python 3 related being used on our import server extension (Modify accordingly)
4. Installation of our package on a Python 2 install of Jupyter (setup.py)
5. Modify our Makefile to allow running relevan targets (dev, server, install) with Python 3 or 2 support
6. Modify travis setup to run System Tests on top of both Python versions

[thibaudh]

That is very helpful. Any guess for the number of man-days to accomplish all this?

On Nov 10, 2015, at 7:00 AM, Gino Bustelo [email protected] wrote:

The priorities of this issue whould be as follow:

1. Enable the use of a Python 2.7+ kernel
2. Enable Python unit tests to run on Python 2.7
3. Verify that there is nothing Python 3 related being used on our import server extension (Modify accordingly)
4. Installation of our package on a Python 2 install of Jupyter (setup.py)
5. Modify our Makefile to allow running relevan targets (dev, server, install) with Python 3 or 2 support
6. Modify travis setup to run System Tests on top of both Python versions

—
Reply to this email directly or view it on GitHub #50 (comment).

[lbustelo]

I'm hoping we get this before the end of the week.

Gino B.

On Nov 10, 2015, at 11:23 AM, Thibaud [email protected] wrote:

That is very helpful. Any guess for the number of man-days to accomplish all this?

On Nov 10, 2015, at 7:00 AM, Gino Bustelo [email protected] wrote:

The priorities of this issue whould be as follow:

1. Enable the use of a Python 2.7+ kernel
2. Enable Python unit tests to run on Python 2.7
3. Verify that there is nothing Python 3 related being used on our import server extension (Modify accordingly)
4. Installation of our package on a Python 2 install of Jupyter (setup.py)
5. Modify our Makefile to allow running relevan targets (dev, server, install) with Python 3 or 2 support
6. Modify travis setup to run System Tests on top of both Python versions

—
Reply to this email directly or view it on GitHub #50 (comment).

—
Reply to this email directly or view it on GitHub.

[parente]

If it helps, the PR jupyter/dashboards#122 has all the Makefile changes needed to test, dev, and install against both Python 2 and 3. (Steps 4 and 5 above). There was only one Python 2.7 compatibility problem in the rest of the code as far as we know so far.

[lbustelo]

Here are the list of problems we are trying to solve:

• urth-import NB server extension is using concurrent.futures
• python unit tests that yield Syntax Errors due to use of function annotations.
• Used of introspection in urth-core-function support
• Syntax use for metaclasses in serialization code
• Some of our examples might need changes
• Update README with Python 2 support
  • Add python 2.7 in requirement area
  • Add statement about requiring https://pypi.python.org/pypi/futures

[lbustelo]

Some good info here

[lbustelo]

We were able to fix the import support by using https://pypi.python.org/pypi/futures

[lbustelo]

@parente What are your thoughts on requiring https://pypi.python.org/pypi/futures to work on Python 2.7?

[parente]

Seems reasonable if it works. The only other option I can think of is to use Tornado's async subprocess module, which I think @zackmorris attempted originally.

[lbustelo]

Going with requiring pip install futures==3.0.3

[lbustelo]

@thibaudh #95 just passed all test. We want to give it another look on Monday, but I would appreciate if you can give it a try and give us any feedback.

[thibaudh]

Great. I will test it on Monday.

Thibaud

On Nov 13, 2015, at 3:48 PM, Gino Bustelo [email protected] wrote:

@thibaudh https://github.com/thibaudh #95 #95 just passed all test. We want to give it another look on Monday, but I would appreciate if you can give it a try and give us any feedback.

—
Reply to this email directly or view it on GitHub #50 (comment).

[thibaudh]

When running setup.py install, I got the following error:

tbh@Thibauds-MacBook-Pro:~/graphistry/declarativewidgets$ python setup.py install
Traceback (most recent call last):
  File "setup.py", line 17, in <module>
    with open(os.path.join(HERE, 'urth/widgets/ext/_version.py')) as f:
IOError: [Errno 2] No such file or directory: '/Users/tbh/graphistry/declarativewidgets/urth/widgets/ext/_version.py’

I am on commit cbdba0a. Did the install procedure change? I used to do make sdist followed by setup.py install

Thibaud

On Nov 13, 2015, at 4:40 PM, Thibaud Hottelier [email protected] wrote:

Great. I will test it on Monday.

Thibaud

On Nov 13, 2015, at 3:48 PM, Gino Bustelo [email protected] wrote:

@thibaudh #95 just passed all test. We want to give it another look on Monday, but I would appreciate if you can give it a try and give us any feedback.

—
Reply to this email directly or view it on GitHub.

[lbustelo]

'make sdist' will create the tar. Then you use 'pip' to install. I never run setup.py directly.

Gino B.

On Nov 16, 2015, at 12:34 PM, Thibaud [email protected] wrote:

When running setup.py install, I got the following error:

tbh@Thibauds-MacBook-Pro:~/graphistry/declarativewidgets$ python setup.py install
Traceback (most recent call last):
File "setup.py", line 17, in <module>
with open(os.path.join(HERE, 'urth/widgets/ext/_version.py')) as f:
IOError: [Errno 2] No such file or directory: '/Users/tbh/graphistry/declarativewidgets/urth/widgets/ext/_version.py’

I am on commit cbdba0a. Did the install procedure change? I used to do make sdist followed by setup.py install

Thibaud

On Nov 13, 2015, at 4:40 PM, Thibaud Hottelier [email protected] wrote:

Great. I will test it on Monday.

Thibaud

On Nov 13, 2015, at 3:48 PM, Gino Bustelo [email protected] wrote:

@thibaudh #95 just passed all test. We want to give it another look on Monday, but I would appreciate if you can give it a try and give us any feedback.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

[lbustelo]

Also remember that the packaging is done under dist/.

Gino B.

On Nov 16, 2015, at 12:34 PM, Thibaud [email protected] wrote:

When running setup.py install, I got the following error:

tbh@Thibauds-MacBook-Pro:~/graphistry/declarativewidgets$ python setup.py install
Traceback (most recent call last):
File "setup.py", line 17, in <module>
with open(os.path.join(HERE, 'urth/widgets/ext/_version.py')) as f:
IOError: [Errno 2] No such file or directory: '/Users/tbh/graphistry/declarativewidgets/urth/widgets/ext/_version.py’

I am on commit cbdba0a. Did the install procedure change? I used to do make sdist followed by setup.py install

Thibaud

On Nov 13, 2015, at 4:40 PM, Thibaud Hottelier [email protected] wrote:

Great. I will test it on Monday.

Thibaud

On Nov 13, 2015, at 3:48 PM, Gino Bustelo [email protected] wrote:

@thibaudh #95 just passed all test. We want to give it another look on Monday, but I would appreciate if you can give it a try and give us any feedback.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

[thibaudh]

Oh right. setup.py now works without errors. But when running the demo notebook, I am still getting loading errors:

http://localhost:8888/notebooks/demos/urth_components/paper-input/paper-input.html Failed to load resource: the server responded with a status of 404 (Not Found)

:8888/static/services/sessions/session.js?v=20151116120427:52 Session: kernel_created (0996144d-ea01-47b3-a6b0-49ce18f8b444)

:8888/static/services/kernels/kernel.js?v=20151116120427:440 Starting WebSockets: ws://localhost:8888/api/kernels/00373f90-e001-4033-ac0e-e4c6bd85108d

:8888/nbextensions/urth_widgets/js/main.js?v=20151116120427:10 Custom JS loaded

:8888/static/base/js/utils.js?v=20151116120427:29 Loaded extension: urth_dash_js/notebook/main

:8888/static/base/js/utils.js?v=20151116120427:29 Loaded extension: urth_widgets/js/main

http://localhost:8888/urth_components/webcomponentsjs/webcomponents-lite.min.js Failed to load resource: the server responded with a status of 404 (Not Found)

:8888/nbextensions/urth_widgets/js/init/init.js?v=20151116120427:115 Failed to load web components polyfill: [object Event]

On Nov 16, 2015, at 11:13 AM, Gino Bustelo [email protected] wrote:

Also remember that the packaging is done under dist/.

Gino B.

On Nov 16, 2015, at 12:34 PM, Thibaud [email protected] wrote:

When running setup.py install, I got the following error:

tbh@Thibauds-MacBook-Pro:~/graphistry/declarativewidgets$ python setup.py install
Traceback (most recent call last):
File "setup.py", line 17, in <module>
with open(os.path.join(HERE, 'urth/widgets/ext/_version.py')) as f:
IOError: [Errno 2] No such file or directory: '/Users/tbh/graphistry/declarativewidgets/urth/widgets/ext/_version.py’

I am on commit cbdba0a. Did the install procedure change? I used to do make sdist followed by setup.py install

Thibaud

On Nov 13, 2015, at 4:40 PM, Thibaud Hottelier [email protected] wrote:

Great. I will test it on Monday.

Thibaud

On Nov 13, 2015, at 3:48 PM, Gino Bustelo [email protected] wrote:

@thibaudh #95 just passed all test. We want to give it another look on Monday, but I would appreciate if you can give it a try and give us any feedback.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

[lbustelo]

Make sure you also installed the additional Pip requirements for Python 2.
https://github.com/jupyter-incubator/declarativewidgets/tree/Python2Support#install

Aside from that... not sure what else is different from our test environment. You can see the image where we are testing at https://github.com/jupyter-incubator/declarativewidgets/blob/Python2Support/etc/images/all-spark-notebook-bower/Dockerfile

[thibaudh]

That was the missing piece. Happy to report that Python 2.7 works for me :)

On Nov 16, 2015, at 12:49 PM, Gino Bustelo [email protected] wrote:

Make sure you also installed the additional Pip requirements for Python 2.
https://github.com/jupyter-incubator/declarativewidgets/tree/Python2Support#install https://github.com/jupyter-incubator/declarativewidgets/tree/Python2Support#install
Aside from that... not sure what else is different from our test environment. You can see the image where we are testing at https://github.com/jupyter-incubator/declarativewidgets/blob/Python2Support/etc/images/all-spark-notebook-bower/Dockerfile https://github.com/jupyter-incubator/declarativewidgets/blob/Python2Support/etc/images/all-spark-notebook-bower/Dockerfile
—
Reply to this email directly or view it on GitHub #50 (comment).