[jupyter] Declarative widgets project status

[Jason Grout]

Hi everyone,

There have been some questions recently about the status of the declarative
widgets project at https://github.com/jupyter-widgets/declarativewidgets.
In https://github.com/jupyter-widgets/declarativewidgets/issues/570, the
people involved in the repo said that the project is currently unmaintained
(though one comment indicated there might be another forthcoming project
that supersedes the work in that repo). I would like to move the repo to
the Jupyter-attic GitHub organization to make the retired status clear.
However, before I do, is there anyone here willing to step forward to
maintain the project?

(If I don't hear anything within a week, I'll go ahead and move the repo to
jupyter-attic.)

Finally, I want to say as a member of the Jupyter community to those that
worked on declarative widgets: thanks very much for your work there and
pushing that experiment forward. We appreciate it!

Thanks,

Jason

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAPDWZHy4FVB8kUqg9_1X0U%3D1cj2HpGbCW3UNY2hHTMxqqd8j0A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] remove up-down arrows on numeric widgets?

[Jason Grout]

That's a browser rendering thing since we now use the html 5 numeric types.
I don't know of a way to get the browser to not render those increment
arrows.

Jason


On Thu, Mar 22, 2018 at 11:17 AM Randy Heiland 
wrote:

> Is it possible to remove the little up-down arrows to increment values in
> a numeric widget? My desire to do so is to save on horizontal space when I
> want several such widgets. Thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/74bd836e-5471-4a38-86cf-93b6cc185a4c%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAPDWZHyENCN6o2oCjuKsa8tJ2onVq_WWppjWaFHCcEPYB01y1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Running the proxy without SSL

[Michael Milligan]

Hi Norman -

You are correct that Jupyterhub will serve without SSL simply by not
providing the SSL keys. There used to be an explicit "--no-ssl" flag but
that was deprecated with the 0.7 release.

My suspicion is that this is going to be more finicky than you would like.
Presumably you want users to be able to connect to the service using either
endpoint. The simplest approach would be to run two fully parallel
Jupyterhub stacks, but in that case your users would get two independent
sessions if they connected through both endpoints. Maybe that is acceptable
for your use case.

If not, you thus need to ensure that both Hub/Proxy pairs know about
sessions and routes modified by the other. You can do this by pointing them
at a common database backend, but I don't think this has been extensively
tested and there may be corner cases where one Hub fails to query the DB at
the right time. Certainly you will want to use a RDBMS server backend,
since the default sqlite implementation is not safe for parallel access.

Alternately, and possibly more robustly, you could subclass the Proxy
interface to make a single Hub drive two copies of the Proxy component.
https://jupyterhub.readthedocs.io/en/latest/reference/proxy.html

Personally, I would just run a single Jupyterhub stack (without SSL) behind
nginx, and also have nginx or the Proxy (see "--redirect-port" at
https://github.com/jupyterhub/configurable-http-proxy) serve a redirect
from port 8000 to the nginx endpoint.

Regards,
Michael

On Thu, Mar 22, 2018 at 1:04 PM, Norman Gray 
wrote:

>
> Roland, hello.
>
> On 22 Mar 2018, at 8:22, Roland Weber wrote:
>
> Afaik, listening on two different ports is not possible without changing
>> code.
>>
>
> Righto -- thanks for confirming.
>
> You could also solve your problem by keeping JupyterHub on the deprecated
>> SSL port, and encrypting the connection between the SSL-terminating proxy
>> and JupyterHub.
>>
>
> Yes -- I'm going to run two servers, an exposed SSL one and a
> reverse-proxied non-SSL one.
>
> Are they likely to fight with one another, do you think?  I can't think of
> a reason why they would, but I could be lacking imagination here.
>
> I'm sure that pull requests to improve the documentation will be happily
>> accepted :-)
>>
>
> I've added an issue 
> which includes some suggested text.
>
> Thanks for your help.  Best wishes,
>
> Norman
>
>
> --
> Norman Gray  :  https://nxg.me.uk
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/jupyter/2F6AB0DA-4FA4-49B9-A202-231700E5090D%40gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Michael Milligan, Ph.D. | Supercomputing Institute
Assistant Director for  | University of Minnesota
   Application Development  | milli...@umn.edu
www.msi.umn.edu/staff/milligan  | Phone: 612-624-8857

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAPuy8gpePT3_90VbpWWHj_kZoN%3DDWFAtQ5qxvXgBnLoVP%2BJpGw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] remove up-down arrows on numeric widgets?

[Randy Heiland]

Is it possible to remove the little up-down arrows to increment values in a 
numeric widget? My desire to do so is to save on horizontal space when I 
want several such widgets. Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/74bd836e-5471-4a38-86cf-93b6cc185a4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Running the proxy without SSL

[Norman Gray]

Roland, hello.

On 22 Mar 2018, at 8:22, Roland Weber wrote:

Afaik, listening on two different ports is not possible without 
changing

code.


Righto -- thanks for confirming.

You could also solve your problem by keeping JupyterHub on the 
deprecated
SSL port, and encrypting the connection between the SSL-terminating 
proxy

and JupyterHub.


Yes -- I'm going to run two servers, an exposed SSL one and a 
reverse-proxied non-SSL one.


Are they likely to fight with one another, do you think?  I can't think 
of a reason why they would, but I could be lacking imagination here.


I'm sure that pull requests to improve the documentation will be 
happily

accepted :-)


I've added an issue 
 which includes 
some suggested text.


Thanks for your help.  Best wishes,

Norman


--
Norman Gray  :  https://nxg.me.uk

--
You received this message because you are subscribed to the Google Groups "Project 
Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/2F6AB0DA-4FA4-49B9-A202-231700E5090D%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [jupyter] Using notebooks as informal packages - (non)exportable code cells

[Johannes Feist]

In case you are not aware of the possibility, what I have been doing for
this case is the "standard" python approach, i.e., simply guard the part
that shouldn't run upon import with
if __name__=='__main__':
statements. When you execute a notebook interactively, __name__ is defined
as '__main__', so the code will run, but when you import it with the hooks
you mention, __name__ is set to the module name, and the code behind the if
doesn't run. Of course it makes the notebook look a bit more ugly, but it
works well, allows to develop modules as notebooks with included tests, and
has the advantage of being immediately visible/obvious (as opposed to
metadata).

Best,
Johannes

On Thu, Mar 22, 2018 at 11:23 AM Tony Hirst  wrote:

> Recipes such as
> http://jupyter-notebook.readthedocs.io/en/stable/examples/Notebook/Importing%20Notebooks.html
> provide a means for importing the contents of a notebook as a module, but
> they do so by executing all code cells.
>
> My development notebooks tend to have functions defined as well as lots of
> little test cells that test the functions, or that include literal bits of
> code that I'm trying to test before working them up into a function.
>
> Sometimes I want to make use of the functions in other notebooks, but
> don't want to run all the other bits of code.
>
> I was thinking it might be handy to define some code cell metadata
> ('exportable':boolean, perhaps), that I could set on a code cell to say
> whether that cell was exportable as a notebook-module function or just
> littering a notebook as a bit of development testing.
>
> The notebook-as-module recipe would then test to see whether a notebook
> cell was not just a code cell, but an exportable code cell, before running
> it. The metadata could also hook into a custom template that could export
> the notebook as python with the code cells set to *exportable:False*
> commented out.
>
> Is anyone using such a recipe? Does it help with workflow?
>
> --tony
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/eba8e9fe-2173-4917-adb4-89a802f35b26%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 

Johannes Feist
IFIMAC & Departamento de Física Teórica de la Materia Condensada
Universidad Autónoma de Madrid
johannes.fe...@uam.es

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAPERba13U6Ek3dzOegCRWZVYco0pPnPJJ4i7VPA9YUSTsrnxsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Using notebooks as informal packages - (non)exportable code cells

[Tony Hirst]

Recipes such 
as 
http://jupyter-notebook.readthedocs.io/en/stable/examples/Notebook/Importing%20Notebooks.html
 
provide a means for importing the contents of a notebook as a module, but 
they do so by executing all code cells.

My development notebooks tend to have functions defined as well as lots of 
little test cells that test the functions, or that include literal bits of 
code that I'm trying to test before working them up into a function.

Sometimes I want to make use of the functions in other notebooks, but don't 
want to run all the other bits of code.

I was thinking it might be handy to define some code cell metadata 
('exportable':boolean, perhaps), that I could set on a code cell to say 
whether that cell was exportable as a notebook-module function or just 
littering a notebook as a bit of development testing.

The notebook-as-module recipe would then test to see whether a notebook 
cell was not just a code cell, but an exportable code cell, before running 
it. The metadata could also hook into a custom template that could export 
the notebook as python with the code cells set to *exportable:False* 
commented out.

Is anyone using such a recipe? Does it help with workflow?

--tony

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/eba8e9fe-2173-4917-adb4-89a802f35b26%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[jupyter] Open position: software engineer for data analysis at European X-ray Free Electron Laser (XFEL)

[Hans Fangohr]

Dear all,


Disclaimer: the positions advertised below are to work in my team on data 
analysis at European XFEL (hosting the world’s brightest laser in a 3.4km long 
tunnel) in Germany.

See the text for details, in brief we are looking for Python skills, Jupyter 
and container knowledge is very welcome, any experience in computational 
science and/or software engineering is welcome. 

The work language is English, and people stick to it. There is a payment bonus 
for non-German employees (to make life in Germany more attractive). 

If you have any questions, please get in touch with me.

Please find the position described at 
http://xfel-old.desy.de/careers/open_positions/engineering_technical_staff/e_191/
 
,
 
and main text copied below.

The position will be filled as soon as suitable applicants have been found, so 
please apply asap if interested.

Best wishes,

Hans





JOB OFFER
European XFEL is an international non-profit company located in the Hamburg 
area in Germany. It operates a 3.4 km-long X-ray laser, which produces X-rays 
of unique quality for studies in physics, chemistry, the life sciences, 
materials research and other disciplines. The diverse scientific facilities at 
European XFEL enable scientists from across the globe to carry out a wide range 
of experimental techniques. Early user operation has started in September 2017.

To ensure continuous support during the transition period we are looking for 
our Control & Analysis Software group for
Software Engineers (f/m) – Data Analysis 
The position
provide support for the use of scientific instruments, collect their data 
analysis requirements and provide solutions
working in group to design, implement, test, review, deploy and maintain 
software solutions to the requirements
support the scientific users before, during and after the experiment
Requirements
BSc or MSc or PhD degree in Computer Science, Physics, Mathematics, 
Engineering, Chemistry or similar field
strong experience writing code, ideally for science applications in Linux/UNIX 
experience
experience in Python and ideally data related libraries
familiarity with fundamental software engineering techniques (such as version 
control, testing, continuous integration)
ability to manage priorities, deadlines and deliverables
excellent communication skills and ability to work as a team player
The following skills/expertise are considered as assets:
C/C++ experience and knowledge of further languages as well as experience with 
agile software development approaches
experience with data analysis/data science/data analytics; background in 
academia, photon science, computational science, high performance computing, or 
work experience as a research software engineer
experience with Jupyter ecosystem and/or containers
interest in software sustainability, reproducibility, Open Science
For additional information contact Sandor Brockhauser 
(sandor.brockhau...@xfel.eu ).

Working place will be Schenefeld in the Hamburg metropolitan area. General 
information on working in Germany, the Hamburg area and the European XFEL can 
be found here .
Reference number
E-191
Duration
This appointment is initially limited to 3 years and may be extended.
Salary and benefits are similar to those of public service organizations in 
Germany. In addition European XFEL provides a non-contributory company pension 
scheme as well as broad relocation benefits. The European XFEL GmbH intends to 
achieve a widely international staff. Non-German candidates hired from abroad 
receive an international allowance.

Handicapped persons will be given preference over other equally qualified 
applicants. The European XFEL GmbH is an equal opportunity and affirmative 
action employer and encourages applications from women.

English is the working language, knowledge of German is considered an asset.
Application
Please apply  here 

 and provide a motivation letter next to a CV in English, as well as your work 
certificates in one single pdf-file.


---

Prof Hans Fangohr
Senior Data Analysis Scientist
European XFEL GmbH Holzkoppel 4
22869 Schenefeld
Germany

Phone:+49 (0)40 8998-6702
Fax: +49 (0)40 8998-1905
Email: hans.fang...@xfel.eu  
http://fangohr.github.io 

Managing Director: Prof. Dr. Robert Feidenhans’l

Registered as European X-Ray Free-Electron Laser Facility GmbH at Amtsgericht 
Hamburg, HRB 65


Professor of Computational Modelling 
University of Southampton
United Kingdom




-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an 

[jupyter] Re: Running the proxy without SSL

[Roland Weber]

Afaik, listening on two different ports is not possible without changing 
code.

You could also solve your problem by keeping JupyterHub on the deprecated 
SSL port, and encrypting the connection between the SSL-terminating proxy 
and JupyterHub.

I'm sure that pull requests to improve the documentation will be happily 
accepted :-)

cheers,
  Roland

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/e0c72139-9960-4448-aa98-a9e6e9b5ddb5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.