Skip to main content

Python on Windows 10

Last weekend I wanted to clean up my python installation on Windows 10. In the past, I used a combination of Anaconda, Python app from the Windows Store, and Python distributions from python.org. Most of these were older versions that I have not updated in a while since I spend most of my time in WSL.

I started by deleting everything and cleaning up the installs. Afterwards, I downloaded python 3.8 from python.org, and proceeded with the installation. I selected install python for everyone and adding it to the %PATH% environment variable.

After the installation completed everything worked like a charm, until I started installing packages.

I started with installing TensorFlow:

pip install tensorflow

and got a cryptic error that one of the TensorFlow files was missing.

A quick internet search revealed that it is due to a missing setting for long filenames in Windows 10.  Following the instructions in this Stackoverflow post to enable long filenames option in the local computer policy, resolved the issue, and the installation proceeded smoothly.

Then I installed keras, and jupyterlab

pip install keras jupyterlab

and tried to run jupyter lab, which failed because Jupyter was not in the %PATH%.  Instead of adding another directory to the %PATH% variable, I ran jupyterlab through:

python -m jupyterlab

 

More keystrokes but works uniformly for any python module.

Now with python and the ML frameworks installed on Windows 10, I can make use of the GPU again. But not for long, since WSL is planning on adding GPU support soon, and there will be no need to live outside of WSL anymore.

Labels:

Comments

Post a Comment

Popular posts from this blog

Kindle Paperwhite

I have always been allergic to buying specialized electronic devices that do only one thing, such as the Kindle, the iPod, and fitness trackers. Why buy these when technology evolves so fast that a multi-purpose device such as the phone or a smart watch can eventually do the same thing, but with the convenience of updates that fix bugs and add functionality? So, I was shocked when this weekend I made an impulse buy and got the newest Kindle Paperwhite—a special purpose device for reading eBooks. I was walking past the Amazon store in the mall and saw that the newest Kindle Paperwhites were marked down by $40 for the holidays. The device looked good in the display, so I went in to look at it closely. The Paperwhite is small and light, with a 6” screen that is backlit and waterproof.   The text was crisp and readable, and in the ambient light, it felt like I am reading a printed book. I was sold and bought it on the spot. At home I have struggled to put it down. The bo...
2 comments
Read more

A paper a day keeps the doctor away: NoDB

In most database systems, the user defines the shape of the data that is stored and queried using concepts such as entities and relations. The database system takes care of translating that shape into physical storage, and managing its lifecycle. Most of the systems store data in the form of tuples, either in row format, or broken down into columns and stored in columnar format. The system also stores metadata associated with the data, that helps with speedy retrieval and processing. Defining the shape of the data a priori, and transforming it from the raw or ingestion format to the storage format is a cost that database systems incur to make queries faster. What if we can have fast queries without incurring that initial cost? In the paper " NoDB: Efficient Query Execution on Raw Data Files ", the authors examine that question, and advocate a system (NoDB) that answers it. The authors start with the motivation for such a system. With the recent explosion of data...
Post a Comment
Read more

A paper a day keeps the doctor away: MillWheel: Fault-Tolerant Stream Processing at Internet Scale

The recent data explosion, and the increase in appetite for fast results spurred a lot of interest in low-latency data processing systems. One such system is MillWheel, presented in the paper " MillWheel: Fault-Tolerant Stream Processing at Internet Scale ", which is widely used at Google. In MillWheel, the users specify a directed computation graph that describe what they would like to do, and write application code that runs on each individual node in the graph. The system takes care of managing the flow of data within the graph, persisting the state of the computation, and handling any failures that occur, relieving the users from that burden. MillWheel exposes an API for record processing, that handles each record in an idempotent fashion, with an exactly once delivery semantics. The system checkpoints progress with a fine granularity, removing the need to buffer data between external senders. The authors describe the system using the Zeitgeist produ...
Post a Comment
Read more