HPDA: archive old lesson and name of the new lesson

[ashwinvis]

If we archive we allow old participants to refer to the old content. What is the name of the new lesson. Ideas in comments below 👇

Also react in this comment:

• 👍 let's archive
• 👎 let's keep the old repo and make a new release

[ashwinvis]

python-for-hpda

another obvious choice, because julia-for-hpda exists, but does it confuse with the old one?

[ashwinvis]

python-for-big-data

is this term more approachable or dated?

[qianglise]

I would suggest that we archive the old one and create a new repo for the hpda part

[ffrancesco94]

python-for-big-data

is this term more approachable or dated?

Might be me but it feels more "old fashioned".

[ashwinvis]

It is very 2010s, but hpda is even worse, a term used only in HPC circles I think.

https://books.google.com/ngrams/graph?content=hpda%2Cbig+data%2Cdata+analytics%2C+hpc&year_start=1800&year_end=2022&corpus=en&smoothing=3

[ashwinvis]

@jadgt, @ffrancesco94, @qianglise, and @code4yonglei can we settle this today?

[jadgt]

High-performance data analysis with python. It's long but it's accurate.

[ffrancesco94]

I like Juan's idea a lot.

…

On Fri, 3 Oct 2025, 17:21 Juan de Gracia, ***@***.***> wrote: *jadgt* left a comment (ENCCS/hpda-python#104) <#104 (comment)> High-performance data analysis with python. It's long but it's accurate. — Reply to this email directly, view it on GitHub <#104 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGGGVZMBGKFDGOQ56GIGCBL3V2H6LAVCNFSM6AAAAACHO2SZT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNRWGE3DENBVHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ashwinvis]

Ok that can be the title, and in fact the current title is actually High Performance Data Analytics in Python link. Not too different.

However the repo and the resulting URL should not be too long.

[ashwinvis]

If we want to keep the same name, we can keep using the same repository.

[jadgt]

For the repo I would keep the same name. I think it is very appropriate

[code4yonglei]

i suggest to keep the same repo, and just (remove) update some episodes to a new repo for python HPC.

[ashwinvis]

We have inbound links to this current lesson. So I think it is worthwhile to keep it as it is and not break too many pages.

See for example here, and who knows where else.

https://aaltoscicomp.github.io/python-for-scicomp/parallel/#see-also