diff --git a/.devcontainer.json b/.devcontainer.json deleted file mode 100644 index 54ddfa1a130f8..0000000000000 --- a/.devcontainer.json +++ /dev/null @@ -1,28 +0,0 @@ -// For format details, see https://aka.ms/vscode-remote/devcontainer.json or the definition README at -// https://github.com/microsoft/vscode-dev-containers/tree/master/containers/python-3-miniconda -{ - "name": "pandas", - "context": ".", - "dockerFile": "Dockerfile", - - // Use 'settings' to set *default* container specific settings.json values on container create. - // You can edit these settings after create using File > Preferences > Settings > Remote. - "settings": { - "python.pythonPath": "/usr/local/bin/python", - "python.formatting.provider": "black", - "python.linting.enabled": true, - "python.linting.flake8Enabled": true, - "python.linting.pylintEnabled": false, - "python.linting.mypyEnabled": true, - "python.testing.pytestEnabled": true, - "python.testing.pytestArgs": [ - "pandas" - ] - }, - - // Add the IDs of extensions you want installed when the container is created in the array below. - "extensions": [ - "ms-python.python", - "ms-vscode.cpptools" - ] -} diff --git a/.gitattributes b/.gitattributes index bc7dec642df0f..44b689cb53915 100644 --- a/.gitattributes +++ b/.gitattributes @@ -65,14 +65,12 @@ pandas/_version.py export-subst asv_bench export-ignore ci export-ignore doc export-ignore -gitpod export-ignore MANIFEST.in export-ignore scripts/** export-ignore typings export-ignore web export-ignore CITATION.cff export-ignore codecov.yml export-ignore -Dockerfile export-ignore environment.yml export-ignore setup.py export-ignore diff --git a/.github/workflows/code-checks.yml b/.github/workflows/code-checks.yml index 82b1ef586e5dc..656d0ed21ba05 100644 --- a/.github/workflows/code-checks.yml +++ b/.github/workflows/code-checks.yml @@ -131,33 +131,6 @@ jobs: asv machine --yes asv run --quick --dry-run --durations=30 --python=same --show-stderr - build_docker_dev_environment: - name: Build Docker Dev Environment - runs-on: ubuntu-24.04 - defaults: - run: - shell: bash -el {0} - - concurrency: - # https://github.community/t/concurrecy-not-work-for-push/183068/7 - group: ${{ github.event_name == 'push' && github.run_number || github.ref }}-build_docker_dev_environment - cancel-in-progress: true - - steps: - - name: Clean up dangling images - run: docker image prune -f - - - name: Checkout - uses: actions/checkout@v5 - with: - fetch-depth: 0 - - - name: Build image - run: docker build --pull --no-cache --tag pandas-dev-env . - - - name: Show environment - run: docker run --rm pandas-dev-env python -c "import pandas as pd; print(pd.show_versions())" - requirements-dev-text-installable: name: Test install requirements-dev.txt runs-on: ubuntu-24.04 diff --git a/.gitpod.yml b/.gitpod.yml deleted file mode 100644 index 5bf028750f30f..0000000000000 --- a/.gitpod.yml +++ /dev/null @@ -1,60 +0,0 @@ -# Building pandas on init -# Might delegate this later to prebuild with Q2 improvements on gitpod -# https://www.gitpod.io/docs/config-start-tasks/#configuring-the-terminal -# ------------------------------------------------------------------------- - -# images for gitpod pandas are in https://hub.docker.com/r/pandas/pandas-gitpod/tags -# we're using the Dockerfile in the base of the repo -image: - file: Dockerfile -tasks: - - name: Prepare development environment - init: | - mkdir -p .vscode - cp gitpod/settings.json .vscode/settings.json - git fetch --tags - python -m pip install -ve . --no-build-isolation -Ceditable-verbose=true - pre-commit install --install-hooks - command: | - python -m pip install -ve . --no-build-isolation -Ceditable-verbose=true - echo "✨ Pre-build complete! You can close this terminal ✨ " - -# -------------------------------------------------------- -# exposing ports for liveserve -ports: - - port: 5500 - onOpen: notify - -# -------------------------------------------------------- -# some useful extensions to have -vscode: - extensions: - - ms-python.python - - yzhang.markdown-all-in-one - - eamodio.gitlens - - lextudio.restructuredtext - - ritwickdey.liveserver - # add or remove what you think is generally useful to most contributors - # avoid adding too many. they each open a pop-up window - -# -------------------------------------------------------- -# Using prebuilds for the container -# With this configuration the prebuild will happen on push to main -github: - prebuilds: - # enable for main/default branch - main: true - # enable for other branches (defaults to false) - branches: false - # enable for pull requests coming from this repo (defaults to true) - pullRequests: false - # enable for pull requests coming from forks (defaults to false) - pullRequestsFromForks: false - # add a check to pull requests (defaults to true) - addCheck: false - # add a "Review in Gitpod" button as a comment to pull requests (defaults to false) - addComment: false - # add a "Review in Gitpod" button to the pull request's description (defaults to false) - addBadge: false - # add a label once the prebuild is ready to pull requests (defaults to false) - addLabel: false diff --git a/Dockerfile b/Dockerfile deleted file mode 100644 index 6d919e80191bc..0000000000000 --- a/Dockerfile +++ /dev/null @@ -1,31 +0,0 @@ -FROM python:3.11.13 -WORKDIR /home/pandas - -# https://docs.docker.com/reference/dockerfile/#automatic-platform-args-in-the-global-scope -ARG TARGETPLATFORM - -RUN apt-get update && \ - apt-get --no-install-recommends -y upgrade && \ - apt-get --no-install-recommends -y install \ - build-essential \ - bash-completion \ - # hdf5 needed for pytables installation - libhdf5-dev \ - # libgles2-mesa needed for pytest-qt - libgles2-mesa-dev && \ - rm -rf /var/lib/apt/lists/* - -COPY requirements-dev.txt /tmp - -RUN case "$TARGETPLATFORM" in \ - linux/arm*) \ - # Drop PyQt5 for ARM GH#61037 - sed -i "/^pyqt5/Id" /tmp/requirements-dev.txt \ - ;; \ - esac && \ - python -m pip install --no-cache-dir --upgrade pip && \ - python -m pip install --no-cache-dir -r /tmp/requirements-dev.txt -RUN git config --global --add safe.directory /home/pandas - -ENV SHELL="/bin/bash" -CMD ["/bin/bash"] diff --git a/doc/source/conf.py b/doc/source/conf.py index f222a228531ff..63c723eb67672 100644 --- a/doc/source/conf.py +++ b/doc/source/conf.py @@ -828,7 +828,6 @@ def setup(app) -> None: "https://github.com/pandas-dev/pandas/blob/v0.20.2/pandas/core/generic.py#L568", "https://github.com/pandas-dev/pandas/blob/v0.20.2/pandas/core/frame.py#L1495", "https://github.com/pandas-dev/pandas/issues/174151", - "https://gitpod.io/#https://github.com/USERNAME/pandas", "https://manishamde.github.io/blog/2013/03/07/pandas-and-python-top-10/", "https://matplotlib.org/api/axes_api.html#matplotlib.axes.Axes.table", "https://nipunbatra.github.io/blog/visualisation/2013/05/01/aggregation-timeseries.html", diff --git a/doc/source/development/contributing_environment.rst b/doc/source/development/contributing_environment.rst index c09e8595f0241..67fe71dd5e648 100644 --- a/doc/source/development/contributing_environment.rst +++ b/doc/source/development/contributing_environment.rst @@ -16,13 +16,11 @@ locally before pushing your changes. It's recommended to also install the :ref:` :maxdepth: 2 :hidden: - contributing_gitpod.rst Step 1: install a C compiler ---------------------------- -How to do this will depend on your platform. If you choose to use ``Docker`` or ``GitPod`` -in the next step, then you can skip this step. +How to do this will depend on your platform. **Windows** @@ -163,51 +161,6 @@ should already exist. # Install the build dependencies python -m pip install -r requirements-dev.txt -Option 3: using Docker -~~~~~~~~~~~~~~~~~~~~~~ - -pandas provides a ``DockerFile`` in the root directory to build a Docker image -with a full pandas development environment. - -**Docker Commands** - -Build the Docker image:: - - # Build the image - docker build -t pandas-dev . - -Run Container:: - - # Run a container and bind your local repo to the container - # This command assumes you are running from your local repo - # but if not alter ${PWD} to match your local repo path - docker run -it --rm -v ${PWD}:/home/pandas pandas-dev - -*Even easier, you can integrate Docker with the following IDEs:* - -**Visual Studio Code** - -You can use the DockerFile to launch a remote session with Visual Studio Code, -a popular free IDE, using the ``.devcontainer.json`` file. -See https://code.visualstudio.com/docs/remote/containers for details. - -**PyCharm (Professional)** - -Enable Docker support and use the Services tool window to build and manage images as well as -run and interact with containers. -See https://www.jetbrains.com/help/pycharm/docker.html for details. - -Option 4: using Gitpod -~~~~~~~~~~~~~~~~~~~~~~ - -Gitpod is an open-source platform that automatically creates the correct development -environment right in your browser, reducing the need to install local development -environments and deal with incompatible dependencies. - -If you are a Windows user, unfamiliar with using the command line or building pandas -for the first time, it is often faster to build with Gitpod. Here are the in-depth instructions -for :ref:`building pandas with GitPod `. - Step 3: build and install pandas -------------------------------- diff --git a/doc/source/development/contributing_gitpod.rst b/doc/source/development/contributing_gitpod.rst deleted file mode 100644 index 447b7b20a8ae5..0000000000000 --- a/doc/source/development/contributing_gitpod.rst +++ /dev/null @@ -1,274 +0,0 @@ -.. _contributing-gitpod: - -Using Gitpod for pandas development -=================================== - -This section of the documentation will guide you through: - -* using Gitpod for your pandas development environment -* creating a personal fork of the pandas repository on GitHub -* a quick tour of pandas and VSCode -* working on the pandas documentation in Gitpod - -Gitpod ------- - -`Gitpod`_ is an open-source platform for automated and ready-to-code -development environments. It enables developers to describe their dev -environment as code and start instant and fresh development environments for -each new task directly from your browser. This reduces the need to install local -development environments and deal with incompatible dependencies. - - -Gitpod GitHub integration -------------------------- - -To be able to use Gitpod, you will need to have the Gitpod app installed on your -GitHub account, so if -you do not have an account yet, you will need to create one first. - -To get started just login at `Gitpod`_, and grant the appropriate permissions to GitHub. - -We have built a python 3.10 environment and all development dependencies will -install when the environment starts. - - -Forking the pandas repository ------------------------------ - -The best way to work on pandas as a contributor is by making a fork of the -repository first. - -#. Browse to the `pandas repository on GitHub`_ and `create your own fork`_. - -#. Browse to your fork. Your fork will have a URL like - https://github.com/noatamir/pandas-dev, except with your GitHub username in place of - ``noatamir``. - -Starting Gitpod ---------------- -Once you have authenticated to Gitpod through GitHub, you can install the -`Gitpod Chromium or Firefox browser extension `_ -which will add a **Gitpod** button next to the **Code** button in the -repository: - -.. image:: ./gitpod-imgs/pandas-github.png - :alt: pandas repository with Gitpod button screenshot - -#. If you install the extension - you can click the **Gitpod** button to start - a new workspace. - -#. Alternatively, if you do not want to install the browser extension, you can - visit https://gitpod.io/#https://github.com/USERNAME/pandas replacing - ``USERNAME`` with your GitHub username. - -#. In both cases, this will open a new tab on your web browser and start - building your development environment. Please note this can take a few - minutes. - -#. Once the build is complete, you will be directed to your workspace, - including the VSCode editor and all the dependencies you need to work on - pandas. The first time you start your workspace, you will notice that there - might be some actions running. This will ensure that you have a development - version of pandas installed. - -#. When your workspace is ready, you can :ref:`test the build` by - entering:: - - $ python -m pytest pandas - - Note that this command takes a while to run, so once you've confirmed it's running you may want to cancel it using ctrl-c. - -Quick workspace tour --------------------- -Gitpod uses VSCode as the editor. If you have not used this editor before, you -can check the Getting started `VSCode docs`_ to familiarize yourself with it. - -Your workspace will look similar to the image below: - -.. image:: ./gitpod-imgs/gitpod-workspace.png - :alt: Gitpod workspace screenshot - -We have marked some important sections in the editor: - -#. Your current Python interpreter - by default, this is ``pandas-dev`` and - should be displayed in the status bar and on your terminal. You do not need - to activate the conda environment as this will always be activated for you. -#. Your current branch is always displayed in the status bar. You can also use - this button to change or create branches. -#. GitHub Pull Requests extension - you can use this to work with Pull Requests - from your workspace. -#. Marketplace extensions - we have added some essential extensions to the pandas - Gitpod. Still, you can also install other extensions or syntax highlighting - themes for your user, and these will be preserved for you. -#. Your workspace directory - by default, it is ``/workspace/pandas-dev``. **Do not - change this** as this is the only directory preserved in Gitpod. - -We have also pre-installed a few tools and VSCode extensions to help with the -development experience: - -* `VSCode rst extension `_ -* `Markdown All in One `_ -* `VSCode GitLens extension `_ -* `VSCode Git Graph extension `_ - -Development workflow with Gitpod --------------------------------- -The :ref:`contributing` section of this documentation contains -information regarding the pandas development workflow. Make sure to check this -before working on your contributions. - -When using Gitpod, git is pre configured for you: - -#. You do not need to configure your git username, and email as this should be - done for you as you authenticated through GitHub. Unless you are using GitHub - feature to keep email address private. You can check the git - configuration with the command ``git config --list`` in your terminal. Use - ``git config --global user.email “your-secret-email@users.noreply.github.com”`` - to set your email address to the one you use to make commits with your github - profile. -#. As you started your workspace from your own pandas fork, you will by default - have both ``upstream`` and ``origin`` added as remotes. You can verify this by - typing ``git remote`` on your terminal or by clicking on the **branch name** - on the status bar (see image below). - - .. image:: ./gitpod-imgs/pandas-gitpod-branches.png - :alt: Gitpod workspace branches plugin screenshot - -Rendering the pandas documentation ----------------------------------- -You can find the detailed documentation on how rendering the documentation with -Sphinx works in the :ref:`contributing.howto-build-docs` section. To build the full -docs you need to run the following command in the ``/doc`` directory:: - - $ cd doc - $ python make.py html - -Alternatively you can build a single page with:: - - python make.py --single development/contributing_gitpod.rst - -You have two main options to render the documentation in Gitpod. - -Option 1: using Liveserve -~~~~~~~~~~~~~~~~~~~~~~~~~ - -#. View the documentation in ``pandas/doc/build/html``. -#. To see the rendered version of a page, you can right-click on the ``.html`` - file and click on **Open with Live Serve**. Alternatively, you can open the - file in the editor and click on the **Go live** button on the status bar. - - .. image:: ./gitpod-imgs/vscode-statusbar.png - :alt: Gitpod workspace VSCode start live serve screenshot - -#. A simple browser will open to the right-hand side of the editor. We recommend - closing it and click on the **Open in browser** button in the pop-up. -#. To stop the server click on the **Port: 5500** button on the status bar. - -Option 2: using the rst extension -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -A quick and easy way to see live changes in a ``.rst`` file as you work on it -uses the rst extension with docutils. - -.. note:: This will generate a simple live preview of the document without the - ``html`` theme, and some backlinks might not be added correctly. But it is an - easy and lightweight way to get instant feedback on your work, without - building the html files. - -#. Open any of the source documentation files located in ``doc/source`` in the - editor. -#. Open VSCode Command Palette with :kbd:`Cmd-Shift-P` in Mac or - :kbd:`Ctrl-Shift-P` in Linux and Windows. Start typing "restructured" - and choose either "Open preview" or "Open preview to the Side". - - .. image:: ./gitpod-imgs/vscode-rst.png - :alt: Gitpod workspace VSCode open rst screenshot - -#. As you work on the document, you will see a live rendering of it on the editor. - - .. image:: ./gitpod-imgs/rst-rendering.png - :alt: Gitpod workspace VSCode rst rendering screenshot - -If you want to see the final output with the ``html`` theme you will need to -rebuild the docs with ``make html`` and use Live Serve as described in option 1. - -FAQ's and troubleshooting -------------------------- - -How long is my Gitpod workspace kept for? -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Your stopped workspace will be kept for 14 days and deleted afterwards if you do -not use them. - -Can I come back to a previous workspace? -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Yes, let's say you stepped away for a while and you want to carry on working on -your pandas contributions. You need to visit https://gitpod.io/workspaces and -click on the workspace you want to spin up again. All your changes will be there -as you last left them. - -Can I install additional VSCode extensions? -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Absolutely! Any extensions you installed will be installed in your own workspace -and preserved. - -I registered on Gitpod but I still cannot see a ``Gitpod`` button in my repositories. -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Head to https://gitpod.io/integrations and make sure you are logged in. -Hover over GitHub and click on the three buttons that appear on the right. -Click on edit permissions and make sure you have ``user:email``, -``read:user``, and ``public_repo`` checked. Click on **Update Permissions** -and confirm the changes in the GitHub application page. - -.. image:: ./gitpod-imgs/gitpod-edit-permissions-gh.png - :alt: Gitpod integrations - edit GH permissions screenshot - -How long does my workspace stay active if I'm not using it? -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -If you keep your workspace open in a browser tab but don't interact with it, -it will shut down after 30 minutes. If you close the browser tab, it will -shut down after 3 minutes. - -My terminal is blank - there is no cursor and it's completely unresponsive -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Unfortunately this is a known-issue on Gitpod's side. You can sort this -issue in two ways: - -#. Create a new Gitpod workspace altogether. -#. Head to your `Gitpod dashboard `_ and locate - the running workspace. Hover on it and click on the **three dots menu** - and then click on **Stop**. When the workspace is completely stopped you - can click on its name to restart it again. - -.. image:: ./gitpod-imgs/gitpod-dashboard-stop.png - :alt: Gitpod dashboard and workspace menu screenshot - -I authenticated through GitHub but I still cannot commit to the repository through Gitpod. -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Head to https://gitpod.io/integrations and make sure you are logged in. -Hover over GitHub and click on the three buttons that appear on the right. -Click on edit permissions and make sure you have ``public_repo`` checked. -Click on **Update Permissions** and confirm the changes in the -GitHub application page. - -.. image:: ./gitpod-imgs/gitpod-edit-permissions-repo.png - :alt: Gitpod integrations - edit GH repository permissions screenshot - -Acknowledgments ---------------- - -This page is lightly adapted from the `NumPy`_ project . - -.. _Gitpod: https://www.gitpod.io/ -.. _pandas repository on GitHub: https://github.com/pandas-dev/pandas -.. _create your own fork: https://help.github.com/en/articles/fork-a-repo -.. _VSCode docs: https://code.visualstudio.com/docs/getstarted/tips-and-tricks -.. _NumPy: https://www.numpy.org/ diff --git a/doc/source/development/gitpod-imgs/gitpod-dashboard-stop.png b/doc/source/development/gitpod-imgs/gitpod-dashboard-stop.png deleted file mode 100644 index b64790a986646..0000000000000 Binary files a/doc/source/development/gitpod-imgs/gitpod-dashboard-stop.png and /dev/null differ diff --git a/doc/source/development/gitpod-imgs/gitpod-edit-permissions-gh.png b/doc/source/development/gitpod-imgs/gitpod-edit-permissions-gh.png deleted file mode 100644 index ec21a9064c83d..0000000000000 Binary files a/doc/source/development/gitpod-imgs/gitpod-edit-permissions-gh.png and /dev/null differ diff --git a/doc/source/development/gitpod-imgs/gitpod-edit-permissions-repo.png b/doc/source/development/gitpod-imgs/gitpod-edit-permissions-repo.png deleted file mode 100644 index 8bfaff81cfb69..0000000000000 Binary files a/doc/source/development/gitpod-imgs/gitpod-edit-permissions-repo.png and /dev/null differ diff --git a/doc/source/development/gitpod-imgs/gitpod-workspace.png b/doc/source/development/gitpod-imgs/gitpod-workspace.png deleted file mode 100644 index daf763e9adb05..0000000000000 Binary files a/doc/source/development/gitpod-imgs/gitpod-workspace.png and /dev/null differ diff --git a/doc/source/development/gitpod-imgs/pandas-github.png b/doc/source/development/gitpod-imgs/pandas-github.png deleted file mode 100644 index 010b0fc5ea33d..0000000000000 Binary files a/doc/source/development/gitpod-imgs/pandas-github.png and /dev/null differ diff --git a/doc/source/development/gitpod-imgs/pandas-gitpod-branches.png b/doc/source/development/gitpod-imgs/pandas-gitpod-branches.png deleted file mode 100644 index f95c66056ca37..0000000000000 Binary files a/doc/source/development/gitpod-imgs/pandas-gitpod-branches.png and /dev/null differ diff --git a/doc/source/development/gitpod-imgs/rst-rendering.png b/doc/source/development/gitpod-imgs/rst-rendering.png deleted file mode 100644 index b613c621c398b..0000000000000 Binary files a/doc/source/development/gitpod-imgs/rst-rendering.png and /dev/null differ diff --git a/doc/source/development/gitpod-imgs/vscode-rst.png b/doc/source/development/gitpod-imgs/vscode-rst.png deleted file mode 100644 index 5b574c115a2b7..0000000000000 Binary files a/doc/source/development/gitpod-imgs/vscode-rst.png and /dev/null differ diff --git a/doc/source/development/gitpod-imgs/vscode-statusbar.png b/doc/source/development/gitpod-imgs/vscode-statusbar.png deleted file mode 100644 index dad25369fedfd..0000000000000 Binary files a/doc/source/development/gitpod-imgs/vscode-statusbar.png and /dev/null differ diff --git a/gitpod/Dockerfile b/gitpod/Dockerfile deleted file mode 100644 index dd4ddf64d16b4..0000000000000 --- a/gitpod/Dockerfile +++ /dev/null @@ -1,100 +0,0 @@ -# -# Dockerfile for pandas development -# -# Usage: -# ------- -# -# To make a local build of the container, from the 'Docker-dev' directory: -# docker build --rm -f "Dockerfile" -t "." -# -# To use the container use the following command. It assumes that you are in -# the root folder of the pandas git repository, making it available as -# /home/pandas in the container. Whatever changes you make to that directory -# are visible in the host and container. -# The docker image is retrieved from the pandas dockerhub repository -# -# docker run --rm -it -v $(pwd):/home/pandas pandas/pandas-dev: -# -# By default the container will activate the conda environment pandas-dev -# which contains all the dependencies needed for pandas development -# -# To build and install pandas run: -# python setup.py build_ext -j 4 -# python -m pip install -e . --no-build-isolation -# -# This image is based on: Ubuntu 20.04 (focal) -# https://hub.docker.com/_/ubuntu/?tab=tags&name=focal -# OS/ARCH: linux/amd64 -FROM gitpod/workspace-base:latest - -ARG MAMBAFORGE_VERSION="23.1.0-3" -ARG CONDA_ENV=pandas-dev -ARG PANDAS_HOME="/home/pandas" - - -# ---- Configure environment ---- -ENV CONDA_DIR=/home/gitpod/mambaforge3 \ - SHELL=/bin/bash -ENV PATH=${CONDA_DIR}/bin:$PATH \ - WORKSPACE=/workspace/pandas - -# ----------------------------------------------------------------------------- -# ---- Creating as root - note: make sure to change to gitpod in the end ---- -USER root - -# Avoid warnings by switching to noninteractive -ENV DEBIAN_FRONTEND=noninteractive - -# Configure apt and install packages -RUN apt-get update \ - && apt-get -y install --no-install-recommends apt-utils dialog 2>&1 \ - # - # Install tzdata and configure timezone (fix for tests which try to read from "/etc/localtime") - && apt-get -y install tzdata \ - && ln -fs /usr/share/zoneinfo/Etc/UTC /etc/localtime \ - && dpkg-reconfigure -f noninteractive tzdata \ - # - # Verify git, process tools, lsb-release (common in install instructions for CLIs) installed - && apt-get -y install git iproute2 procps iproute2 lsb-release \ - # - # cleanup - && apt-get autoremove -y \ - && apt-get clean -y \ - && rm -rf /var/lib/apt/lists/* - -# Switch back to dialog for any ad-hoc use of apt-get -ENV DEBIAN_FRONTEND=dialog - -# Allows this Dockerfile to activate conda environments -SHELL ["/bin/bash", "--login", "-o", "pipefail", "-c"] - -# ----------------------------------------------------------------------------- -# ---- Installing mamba ---- -RUN wget -q -O mambaforge3.sh \ - "https://github.com/conda-forge/miniforge/releases/download/$MAMBAFORGE_VERSION/Mambaforge-$MAMBAFORGE_VERSION-Linux-x86_64.sh" && \ - bash mambaforge3.sh -p ${CONDA_DIR} -b && \ - rm mambaforge3.sh - -# ----------------------------------------------------------------------------- -# ---- Copy needed files ---- -# basic workspace configurations -COPY ./gitpod/workspace_config /usr/local/bin/workspace_config - -RUN chmod a+rx /usr/local/bin/workspace_config && \ - workspace_config - -# the container to create a conda environment from it -COPY environment.yml /tmp/environment.yml - -# ---- Create conda environment ---- -RUN mamba env create -f /tmp/environment.yml && \ - conda activate $CONDA_ENV && \ - mamba install ccache -y && \ - # needed for docs rendering later on - python -m pip install --no-cache-dir sphinx-autobuild && \ - conda clean --all -f -y && \ - rm -rf /tmp/* - -# ----------------------------------------------------------------------------- -# Always make sure we are not root -USER gitpod diff --git a/gitpod/gitpod.Dockerfile b/gitpod/gitpod.Dockerfile deleted file mode 100644 index ab3f25b231e67..0000000000000 --- a/gitpod/gitpod.Dockerfile +++ /dev/null @@ -1,48 +0,0 @@ -# Doing a local shallow clone - keeps the container secure -# and much slimmer than using COPY directly or making a -# remote clone -ARG BASE_CONTAINER="pandas/pandas-dev:latest" -FROM gitpod/workspace-base:latest as clone - -# the clone should be deep enough for versioneer to work -RUN git clone https://github.com/pandas-dev/pandas --depth 12 /tmp/pandas - -# ----------------------------------------------------------------------------- -# Using the pandas-dev Docker image as a base -# This way, we ensure we have all the needed compilers and dependencies -# while reducing the build time -FROM ${BASE_CONTAINER} as build - -# ----------------------------------------------------------------------------- -USER root - -# ----------------------------------------------------------------------------- -# ---- ENV variables ---- -# ---- Directories needed ---- -ENV WORKSPACE=/workspace/pandas/ \ - CONDA_ENV=pandas-dev - -# Allows this micromamba.Dockerfile to activate conda environments -SHELL ["/bin/bash", "--login", "-o", "pipefail", "-c"] - -# Copy over the shallow clone -COPY --from=clone --chown=gitpod /tmp/pandas ${WORKSPACE} - -# Everything happens in the /workspace/pandas directory -WORKDIR ${WORKSPACE} - -# Build pandas to populate the cache used by ccache -RUN git config --global --add safe.directory /workspace/pandas -RUN conda activate ${CONDA_ENV} && \ - python -m pip install -e . --no-build-isolation && \ - python setup.py build_ext --inplace && \ - ccache -s - -# Gitpod will load the repository into /workspace/pandas. We remove the -# directory from the image to prevent conflicts -RUN rm -rf ${WORKSPACE} - -# ----------------------------------------------------------------------------- -# Always return to non privileged user -RUN chown -R gitpod:gitpod /home/gitpod/.cache/ -USER gitpod diff --git a/gitpod/settings.json b/gitpod/settings.json deleted file mode 100644 index 2c2c3b551e1d1..0000000000000 --- a/gitpod/settings.json +++ /dev/null @@ -1,5 +0,0 @@ -{ - "esbonio.server.pythonPath": "/usr/local/bin/python", - "restructuredtext.linter.disabledLinters": ["doc8","rst-lint", "rstcheck"], - "python.defaultInterpreterPath": "/usr/local/bin/python" -} diff --git a/gitpod/workspace_config b/gitpod/workspace_config deleted file mode 100644 index d49c93ec83db9..0000000000000 --- a/gitpod/workspace_config +++ /dev/null @@ -1,54 +0,0 @@ -#!/bin/bash -# Basic configurations for the workspace - -set -e - -# gitpod/workspace-base needs at least one file here -touch /home/gitpod/.bashrc.d/empty - -# Add git aliases -git config --global alias.co checkout -git config --global alias.ci commit -git config --global alias.st status -git config --global alias.br branch -git config --global alias.hist "log --pretty=format:'%h %ad | %s%d [%an]' --graph --date=short" -git config --global alias.type 'cat-file -t' -git config --global alias.dump 'cat-file -p' - -# Enable basic vim defaults in ~/.vimrc -echo "filetype plugin indent on" >>~/.vimrc -echo "set colorcolumn=80" >>~/.vimrc -echo "set number" >>~/.vimrc -echo "syntax enable" >>~/.vimrc - -# Vanity custom bash prompt - makes it more legible -echo "PS1='\[\e]0;\u \w\a\]\[\033[01;36m\]\u\[\033[m\] > \[\033[38;5;141m\]\w\[\033[m\] \\$ '" >>~/.bashrc - -# Enable prompt color in the skeleton .bashrc -# hadolint ignore=SC2016 -sed -i 's/^#force_color_prompt=yes/force_color_prompt=yes/' /etc/skel/.bashrc - -# .gitpod.yml is configured to install pandas from /workspace/pandas -echo "export PYTHONPATH=${WORKSPACE}" >>~/.bashrc - -# make conda activate command available from /bin/bash (login and interactive) -if [[ ! -f "/etc/profile.d/conda.sh" ]]; then - ln -s ${CONDA_DIR}/etc/profile.d/conda.sh /etc/profile.d/conda.sh -fi -echo ". ${CONDA_DIR}/etc/profile.d/conda.sh" >>~/.bashrc -echo "conda activate pandas-dev" >>~/.bashrc - -# Enable prompt color in the skeleton .bashrc -# hadolint ignore=SC2016 -sed -i 's/^#force_color_prompt=yes/force_color_prompt=yes/' /etc/skel/.bashrc - -# .gitpod.yml is configured to install pandas from /workspace/pandas -echo "export PYTHONPATH=/workspace/pandas" >>~/.bashrc - -# Set up ccache for compilers for this Dockerfile -# REF: https://github.com/conda-forge/compilers-feedstock/issues/31 -echo "conda activate pandas-dev" >>~/.startuprc -echo "export CC=\"ccache \$CC\"" >>~/.startuprc -echo "export CXX=\"ccache \$CXX\"" >>~/.startuprc -echo "source ~/.startuprc" >>~/.profile -echo "source ~/.startuprc" >>~/.bashrc diff --git a/scripts/validate_rst_title_capitalization.py b/scripts/validate_rst_title_capitalization.py index 243f70b4b8fcd..8dbea1947eb46 100755 --- a/scripts/validate_rst_title_capitalization.py +++ b/scripts/validate_rst_title_capitalization.py @@ -54,7 +54,6 @@ "MultiIndex", "NumFOCUS", "sklearn", - "Docker", "PeriodIndex", "NA", "NaN", @@ -161,7 +160,6 @@ "Numba", "Timestamp", "PyArrow", - "Gitpod", "Liveserve", "I", "VSCode",