chore: Update org name from altair-viz to vega

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -9,7 +9,7 @@ body:
         
         Note that since Altair is a Python wrapper around the Vega-Lite visualization grammar, [most bugs should be reported directly to Vega-Lite](https://github.com/vega/vega-lite/issues). You can click the Action Button (`...`) of your Altair chart and "Open in Vega Editor" to see if you get the same error in the Vega Editor.
         
-        If you can't reproduce the bug in the Vega Editor, then make sure you are using [the latest version of Altair](https://github.com/altair-viz/altair/releases) and search for duplicate issues before filling out the form below.
+        If you can't reproduce the bug in the Vega Editor, then make sure you are using [the latest version of Altair](https://github.com/vega/altair/releases) and search for duplicate issues before filling out the form below.
   - type: textarea
     id: what-happened
     attributes:

.github/ISSUE_TEMPLATE/config.yml

@@ -4,5 +4,5 @@ contact_links:
     url: https://stackoverflow.com/tags/altair
     about: Please ask questions such as "How do I do X?" or "Why does this not work?" on Stack Overflow using the `altair` tag.
   - name: Discussion
-    url: https://github.com/altair-viz/altair/discussions
+    url: https://github.com/vega/altair/discussions
     about: If you want to discuss a topic or ask a question that is not a good fit for Stack Overflow, please open a new disscussion here on GitHub.

.github/workflows/build.yml

@@ -36,7 +36,7 @@ jobs:
         # We uninstall pyarrow and vegafusion for one job to test that we have not
         # accidentally introduced a hard dependency on these libraries.
         # Uninstalling for Python 3.8 is an arbitrary choice.
-        # Also see https://github.com/altair-viz/altair/pull/3114
+        # Also see https://github.com/vega/altair/pull/3114
         if: ${{ matrix.python-version == '3.8' }}
         run: |
           pip uninstall -y pyarrow vegafusion vegafusion-python-embed

CONTRIBUTING.md

@@ -1,15 +1,15 @@
 # Feedback and Contribution
 
 We welcome any input, feedback, bug reports, and contributions via [Altair's
-GitHub Repository](http://github.com/altair-viz/altair/). In particular, we
+GitHub Repository](http://github.com/vega/altair/). In particular, we
 welcome companion efforts from other visualization libraries to render the
 Vega-Lite specifications output by Altair. We see this portion of the effort
 as much bigger than Altair itself: the Vega and Vega-Lite specifications are
 perhaps the best existing candidates for a principled *lingua franca* of data
 visualization.
 
 We are also seeking contributions of additional Jupyter notebook-based examples
-in our separate GitHub repository: https://github.com/altair-viz/altair_notebooks.
+in our separate GitHub repository: https://github.com/vega/altair_notebooks.
 
 All contributions, suggestions, and feedback you submitted are accepted under the [Project's license](./LICENSE). You represent that if you do not own copyright in the code that you have the authority to submit it under the [Project's license](./LICENSE). All feedback, suggestions, or contributions are not confidential. The Project abides by the Vega Organization's [code of conduct](https://github.com/vega/.github/blob/main/CODE_OF_CONDUCT.md) and [governance](https://github.com/vega/.github/blob/main/project-docs/GOVERNANCE.md).
 

README.md

@@ -1,6 +1,6 @@
 # Vega-Altair <a href="https://altair-viz.github.io/"><img align="right" src="https://altair-viz.github.io/_static/altair-logo-light.png" height="50"></img></a>
 
-[![github actions](https://github.com/altair-viz/altair/workflows/build/badge.svg)](https://github.com/altair-viz/altair/actions?query=workflow%3Abuild)
+[![github actions](https://github.com/vega/altair/workflows/build/badge.svg)](https://github.com/vega/altair/actions?query=workflow%3Abuild)
 [![typedlib_mypy](https://www.mypy-lang.org/static/mypy_badge.svg)](https://www.mypy-lang.org)
 [![JOSS Paper](https://joss.theoj.org/papers/10.21105/joss.01057/status.svg)](https://joss.theoj.org/papers/10.21105/joss.01057)
 [![PyPI - Downloads](https://img.shields.io/pypi/dm/altair)](https://pypi.org/project/altair)
@@ -17,7 +17,7 @@ Interactive Data Lab](https://idl.cs.washington.edu/).*
 
 ## Documentation
 
-See [Vega-Altair's Documentation Site](https://altair-viz.github.io) as well as the [Tutorial Notebooks](https://github.com/altair-viz/altair_notebooks). You can
+See [Vega-Altair's Documentation Site](https://altair-viz.github.io) as well as the [Tutorial Notebooks](https://github.com/vega/altair_notebooks). You can
 run the notebooks directly in your browser by clicking on one of the following badges:
 
 [![Binder](https://beta.mybinder.org/badge.svg)](https://beta.mybinder.org/v2/gh/altair-viz/altair_notebooks/master)
@@ -105,7 +105,7 @@ For full installation instructions, please see [the documentation](https://altai
 
 If you have a question that is not addressed in the documentation, 
 you can post it on [StackOverflow](https://stackoverflow.com/questions/tagged/altair) using the `altair` tag.
-For bugs and feature requests, please open a [Github Issue](https://github.com/altair-viz/altair/issues).
+For bugs and feature requests, please open a [Github Issue](https://github.com/vega/altair/issues).
 
 ## Development
 
@@ -122,7 +122,7 @@ hatch run test
 ```
 
 For information on how to contribute your developments back to the Vega-Altair repository, see
-[`CONTRIBUTING.md`](https://github.com/altair-viz/altair/blob/main/CONTRIBUTING.md)
+[`CONTRIBUTING.md`](https://github.com/vega/altair/blob/main/CONTRIBUTING.md)
 
 ## Citing Vega-Altair
 

RELEASING.md

@@ -61,4 +61,4 @@
     pip package by the conda-forge bot (may take up to ~an hour):
     https://github.com/conda-forge/altair-feedstock/pulls
 
-13. Publish a new release in https://github.com/altair-viz/altair/releases/
+13. Publish a new release in https://github.com/vega/altair/releases/

altair/utils/core.py

@@ -371,7 +371,7 @@ def to_list_if_array(val):
             # This is because Javascript parses date-only times in UTC, but
             # parses full ISO-8601 dates as local time, and dates in Vega and
             # Vega-Lite are displayed in local time by default.
-            # (see https://github.com/altair-viz/altair/issues/1027)
+            # (see https://github.com/vega/altair/issues/1027)
             df[col_name] = (
                 df[col_name].apply(lambda x: x.isoformat()).replace("NaT", "")
             )
@@ -386,21 +386,18 @@ def to_list_if_array(val):
             # geopandas >=0.6.1 uses the dtype geometry. Continue here
             # otherwise it will give an error on np.issubdtype(dtype, np.integer)
             continue
-        elif (
-            dtype_name
-            in {
-                "Int8",
-                "Int16",
-                "Int32",
-                "Int64",
-                "UInt8",
-                "UInt16",
-                "UInt32",
-                "UInt64",
-                "Float32",
-                "Float64",
-            }
-        ):  # nullable integer datatypes (since 24.0) and nullable float datatypes (since 1.2.0)
+        elif dtype_name in {
+            "Int8",
+            "Int16",
+            "Int32",
+            "Int64",
+            "UInt8",
+            "UInt16",
+            "UInt32",
+            "UInt64",
+            "Float32",
+            "Float64",
+        }:  # nullable integer datatypes (since 24.0) and nullable float datatypes (since 1.2.0)
             # https://pandas.pydata.org/pandas-docs/version/0.25/whatsnew/v0.24.0.html#optional-integer-na-support
             col = df[col_name].astype(object)
             df[col_name] = col.where(col.notnull(), None)

altair/utils/schemapi.py

@@ -269,7 +269,7 @@ def _json_path(err: jsonschema.exceptions.ValidationError) -> str:
     """Drop in replacement for the .json_path property of the jsonschema
     ValidationError class, which is not available as property for
     ValidationError with jsonschema<4.0.1.
-    More info, see https://github.com/altair-viz/altair/issues/3038
+    More info, see https://github.com/vega/altair/issues/3038
     """
     path = "$"
     for elem in err.absolute_path:

doc/about/roadmap.rst

@@ -8,7 +8,7 @@ informed by the needs of the Vega-Altair community, and the priorities of the ac
 project contributors. It's designed to communicate the direction of the project,
 but it's not a commitment that these items will be completed in a particular timeframe.
 If you would like to help contribute to any of these areas, or suggest new ones,
-please `start a discussion <https://github.com/altair-viz/altair/discussions>`_.
+please `start a discussion <https://github.com/vega/altair/discussions>`_.
 
 Vega-Altair is deeply integrated with other components in the Vega ecosystem,
 and as such many items on the roadmap will require work in other projects.
@@ -107,7 +107,7 @@ Map Tile Support
 ----------------
 We want Vega-Altair to provide first-class support for displaying map tiles from
 xyz tile providers like OpenStreetMap. We've released a first version of
-`altair_tiles <https://github.com/altair-viz/altair_tiles>`_ to accomplish this. Feedback is very welcome!
+`altair_tiles <https://github.com/vega/altair_tiles>`_ to accomplish this. Feedback is very welcome!
 
 Scale/Performance Improvements
 ------------------------------

doc/conf.py

@@ -146,7 +146,7 @@
     "icon_links": [
         {
             "name": "GitHub",
-            "url": "https://github.com/altair-viz/altair",
+            "url": "https://github.com/vega/altair",
             "icon": "fab fa-github fa-lg",
             "type": "fontawesome",
         },

doc/getting_started/getting_help.rst

@@ -12,9 +12,9 @@ or by viewing the full site :ref:`genindex`.
 In addition to reading this documentation page,
 it can be helpful to also browse the `Vega-Lite documentation <https://vega.github.io/vega-lite/docs/>`_.
 
-.. _GitHub: http://github.com/altair-viz/altair
-.. _Git Issues: http://github.com/altair-viz/altair/issues
+.. _GitHub: http://github.com/vega/altair
+.. _Git Issues: http://github.com/vega/altair/issues
 .. _Vega: http://vega.github.io/vega
 .. _Vega-Lite: http://vega.github.io/vega-lite
-.. _bugs and feature requests: https://github.com/altair-viz/altair/issues/new/choose
+.. _bugs and feature requests: https://github.com/vega/altair/issues/new/choose
 .. _StackOverflow: https://stackoverflow.com/tags/altair

doc/getting_started/installation.rst

@@ -46,14 +46,14 @@ development version directly from GitHub using:
 
 .. code-block:: bash
 
-    pip install -e git+https://github.com/altair-viz/altair.git
+    pip install -e git+https://github.com/vega/altair.git
 
-Please see `CONTRIBUTING.md <https://github.com/altair-viz/altair/blob/main/CONTRIBUTING.md>`_
+Please see `CONTRIBUTING.md <https://github.com/vega/altair/blob/main/CONTRIBUTING.md>`_
 for details on how to contribute to the Altair project.
 
 .. _conda: https://docs.conda.io/
 .. _Vega-Lite: http://vega.github.io/vega-lite
 .. _vega_datasets: https://github.com/altair-viz/vega_datasets
 .. _JupyterLab: http://jupyterlab.readthedocs.io/
 .. _Jupyter Notebook: https://jupyter-notebook.readthedocs.io/
-.. _Altair source repository: http://github.com/altair-viz/altair
+.. _Altair source repository: http://github.com/vega/altair

doc/getting_started/resources.rst

@@ -3,7 +3,7 @@
 Resources
 =========
 
-We hope to make it easier to find learning resources and projects related to Altair by listing them here. If you know of a project that should be added, please let us know by opening an `Issue on GitHub <https://github.com/altair-viz/altair/issues>`_.
+We hope to make it easier to find learning resources and projects related to Altair by listing them here. If you know of a project that should be added, please let us know by opening an `Issue on GitHub <https://github.com/vega/altair/issues>`_.
 
 .. _learning-resources:
 

doc/index.rst

@@ -59,11 +59,11 @@ Vega-Altair: Declarative Visualization in Python
    User Guide <user_guide/data>
    Examples <gallery/index>
    API <user_guide/api>
-   Release Notes <https://github.com/altair-viz/altair/releases>
+   Release Notes <https://github.com/vega/altair/releases>
    About <about/roadmap>
 
-.. _GitHub: http://github.com/altair-viz/altair
-.. _Git Issues: http://github.com/altair-viz/altair/issues
+.. _GitHub: http://github.com/vega/altair
+.. _Git Issues: http://github.com/vega/altair/issues
 .. _Vega-Lite: http://vega.github.io/vega-lite
-.. _bugs and feature requests: https://github.com/altair-viz/altair/issues/new/choose
+.. _bugs and feature requests: https://github.com/vega/altair/issues/new/choose
 .. _StackOverflow: https://stackoverflow.com/tags/altair

doc/releases/changes.rst

@@ -3,4 +3,4 @@
 Release Notes
 =============
 
-We have moved the release notes to GitHub. You can now find them `here <https://github.com/altair-viz/altair/releases>`_.
+We have moved the release notes to GitHub. You can now find them `here <https://github.com/vega/altair/releases>`_.

doc/user_guide/display_frontends.rst

@@ -177,7 +177,7 @@ Package
 The above mentioned frameworks all require you to run a web application on a server if you want to share your work with others. A web application gives you a lot of flexibility, you can for example fetch data from a database based on the value of a dropdown menu in the dashboard. However, it comes with some complexity as well. 
 For use cases where the interactivity provided by Altair itself is enough, you can also use tools which generate HTML pages which do not require a web server such as `Quarto <https://quarto.org/>`_ or `Jupyter Book <https://jupyterbook.org/>`_.
 
-If you are using a dashboarding package that is not listed here, please `open an issue <https://github.com/altair-viz/altair/issues>`_ on GitHub so that we can add it.
+If you are using a dashboarding package that is not listed here, please `open an issue <https://github.com/vega/altair/issues>`_ on GitHub so that we can add it.
 
 .. _display-general:
 

doc/user_guide/encodings/channels.rst

@@ -163,7 +163,7 @@ The same approach works for other mark types, like stacked areas charts.
 Note that unlike the ``sort`` parameter to positional encoding channels,
 the :class:`Order` channel cannot take a list of values to sort by
 and is not automatically sorted when an ordered pandas categorical column is passed.
-If we want to sort stacked segments in a custom order, we can `follow the approach in this issue comment <https://github.com/altair-viz/altair/issues/245#issuecomment-748443434>`_, although there might be edge cases where this is not fully supported. This workaround also makes the order of the segments align with the order that the colors shows up in a legend that uses custom sorting for the color domain.
+If we want to sort stacked segments in a custom order, we can `follow the approach in this issue comment <https://github.com/vega/altair/issues/245#issuecomment-748443434>`_, although there might be edge cases where this is not fully supported. This workaround also makes the order of the segments align with the order that the colors shows up in a legend that uses custom sorting for the color domain.
 
 For line marks, the :class:`Order` channel encodes the order in which data points are connected. This can be useful for creating a scatter plot that draws lines between the dots using a different field than the x and y axes.
 

doc/user_guide/internals.rst

@@ -110,7 +110,7 @@ Altair's python object structure and Vega-Lite's schema definition structure.
 One of the nice features of Altair is that this low-level object hierarchy is not
 constructed by hand, but rather *programmatically generated* from the Vega-Lite
 schema, using the ``generate_schema_wrapper.py`` script that you can find in
-`Altair's repository <https://github.com/altair-viz/altair/blob/main/tools/generate_schema_wrapper.py>`_.
+`Altair's repository <https://github.com/vega/altair/blob/main/tools/generate_schema_wrapper.py>`_.
 This auto-generation of code propagates descriptions from the vega-lite schema
 into the Python class docstrings, from which the
 `API Reference <http://altair-viz.github.io/user_guide/API.html>`_

doc/user_guide/jupyter_chart.rst

@@ -20,7 +20,7 @@ Tested environments include:
 
 .. note::
     If you try ``JupyterChart`` in another environment that supports Jupyter Widgets,
-    `let us know how it goes <https://github.com/altair-viz/altair/issues>`_ so that we can keep
+    `let us know how it goes <https://github.com/vega/altair/issues>`_ so that we can keep
     this list up to date.
 
 Basic Usage

doc/user_guide/marks/geoshape.rst

@@ -466,7 +466,7 @@ The :class:`FacetChart` pattern, accessible via the :meth:`Chart.facet` method
 provides a convenient interface for a particular type of horizontal or vertical
 concatenation of a dataset where one field contain multiple ``variables``.
 
-Unfortunately, until https://github.com/altair-viz/altair/issues/2369 is resolved
+Unfortunately, until https://github.com/vega/altair/issues/2369 is resolved
 regular faceting will not work for geographic visualization:
 
 .. altair-plot::

doc/user_guide/transform/filter.rst

@@ -170,7 +170,7 @@ selection. This can be accomplished using the various logical operand classes:
 - :class:`~LogicalNotPredicate`
 
 These are not yet part of the Altair interface
-(see `Issue 695 <https://github.com/altair-viz/altair/issues/695>`_)
+(see `Issue 695 <https://github.com/vega/altair/issues/695>`_)
 but can be constructed explicitly; for example, here we plot US population
 distributions for all data *except* the years 1950-1960,
 by applying a ``LogicalNotPredicate`` schema to a ``FieldRangePredicate``:

paper/paper.md

@@ -102,6 +102,6 @@ on the bar chart. The selections drive filters in the other plot. The code for t
 # Acknowledgements
 
 We thank the many contributors that created examples, wrote documentation, and reported bugs. You can find [an up-to-date
-list of contributors on GitHub](https://github.com/altair-viz/altair/graphs/contributors).
+list of contributors on GitHub](https://github.com/vega/altair/graphs/contributors).
 
 # References

pyproject.toml

@@ -54,7 +54,7 @@ classifiers = [
 
 [project.urls]
 Documentation = "https://altair-viz.github.io"
-Source = "https://github.com/altair-viz/altair"
+Source = "https://github.com/vega/altair"
 
 [project.optional-dependencies]
 all = [

tests/utils/test_dataframe_interchange.py

@@ -24,7 +24,7 @@ def windows_has_tzdata():
 
 
 # Skip test on Windows when the tz database is not configured.
-# See https://github.com/altair-viz/altair/issues/3050.
+# See https://github.com/vega/altair/issues/3050.
 @pytest.mark.skipif(
     sys.platform == "win32" and not windows_has_tzdata(),
     reason="Timezone database is not installed on Windows",

tools/generate_schema_wrapper.py

@@ -803,7 +803,7 @@ def _create_encode_signature(
 
         # dict stands for the return types of alt.datum, alt.value as well as
         # the dictionary representation of an encoding channel class. See
-        # discussions in https://github.com/altair-viz/altair/pull/3208
+        # discussions in https://github.com/vega/altair/pull/3208
         # for more background.
         union_types = ["str", field_class_name, "dict"]
         docstring_union_types = ["str", rst_syntax_for_class(field_class_name), "Dict"]

tools/schemapi/schemapi.py

@@ -267,7 +267,7 @@ def _json_path(err: jsonschema.exceptions.ValidationError) -> str:
     """Drop in replacement for the .json_path property of the jsonschema
     ValidationError class, which is not available as property for
     ValidationError with jsonschema<4.0.1.
-    More info, see https://github.com/altair-viz/altair/issues/3038
+    More info, see https://github.com/vega/altair/issues/3038
     """
     path = "$"
     for elem in err.absolute_path: