Where to find pkgsrc packages for Darwin ppc? #382
Assignees
Comments
|
We don't build any PPC packages, but Nia has recently been working on Tiger support, and you can find packages here: https://www.netbsd.org/~nia/tigersrc/ |
|
@jperkin My primary interest are 10.5 and 10.6, but this is interesting, thank you. I will take a look. |
|
There's a mildly obfuscated email address at the bottom of that page. The GitHub repo is the main pkgsrc repository at https://github.com/NetBSD/pkgsrc |
Aha, thank you. That is enough. |
jperkin
pushed a commit
that referenced
this issue
May 17, 2024
0.21.0 (2024-03-10) ------------------- - Improve documentation. [#483] - Add a minimum version requirement for ``asdf-wcs-schemas``. [#491] - Fix ``WCS.__str__`` for instances without transforms. [#489] 0.20.0 (2023-11-29) ------------------- - Replace ``pkg_resources`` with ``importlib.metadata``. [#478] - Serialize and deserialize ``pixel_shape`` with asdf. [#480] 0.19.0 (2023-09-15) ------------------- Bug Fixes ^^^^^^^^^ - Synchronize ``array_shape`` and ``pixel_shape`` attributes of WCS objects. [#439] - Fix failures and warnings with numpy 2.0. [#472] other ^^^^^ - Remove deprecated old ``bounding_box``. The new implementation is released with astropy v 5.3. [#458] - Refactor ``CoordinateFrame.axis_physical_types``. [#459] - ``StokesFrame`` uses now ``astropy.coordinates.StokesCoord``. [#452] - Dropped support for Python 3.8. [#451] - Fixed a call to ``astropy.coordinates`` in ``wcstools.wcs_from_points``. [#448] - Code and docstrings clean up. [#460] - Register all available asdf extension manifests from ``asdf-wcs-schemas`` except 1.0.0 (which contains duplicate tag versions). [#469] - Register empty extension for 1.0.0 to avoid warning about a missing extension when opening old files. [#475] 0.18.3 (2022-12-23) ------------------- Bug Fixes ^^^^^^^^^ - Fixed a bug in the estimate of pixel scale in the iterative inverse code. [#423] - Fixed constant term in the polynomial used for SIP fitting. Improved stability and accuracy of the SIP fitting code. [#427] 0.18.2 (2022-09-07) ------------------- Bug Fixes ^^^^^^^^^ - Corrected the reported requested forward SIP accuracy and reported fit residuals by ``to_fits_sip()`` and ``to_fits()``. [#413, #419] - Fixed a bug due to which the check for divergence in ``_fit_2D_poly()`` and hence in ``to_fits()`` and ``to_fits_sip()`` was ignored. [#414] New Features ^^^^^^^^^^^^ 0.18.1 (2022-03-15) ------------------- Bug Fixes ^^^^^^^^^ - Remove references to the ``six`` package. [#402] 0.18.0 (2021-12-22) ------------------- Bug Fixes ^^^^^^^^^ - Updated code in ``region.py`` with latest improvements and bug fixes from ``stsci.skypac.regions.py`` [#382] - Added support to ``_compute_lon_pole()`` for computation of ``lonpole`` for all projections from ``astropy.modeling.projections``. This also extends support for different projections in ``wcs_from_fiducial()``. [#389] New Features ^^^^^^^^^^^^ - Enabled ``CompoundBoundingBox`` support for wcs. [#375] - Moved schemas to standalone package ``asdf-wcs-schemas``. Reworked the serialization code to use ASDF converters. [#388] 0.17.1 (2021-11-27) ------------------- Bug Fixes ^^^^^^^^^ - Fixed a bug with StokesProfile and array types. [#384] 0.17.0 (2021-11-17) ------------------- Bug Fixes ^^^^^^^^^ - `world_axis_object_components` and `world_axis_object_classes` now ensure unique keys in `CompositeFrame` and `CoordinateFrame`. [#356] - Fix issue where RuntimeWarning is raised when there are NaNs in coordinates in angle wrapping code [#367] - Fix deprecation warning when wcs is initialized with a pipeline [#368] - Use ``CD`` formalism in ``WCS.to_fits_sip()``. [#380] New Features ^^^^^^^^^^^^ - ``wcs_from_points`` now includes fitting for the inverse transform. [#349] - Generalized ``WCS.to_fits_sip`` to be able to create a 2D celestial FITS WCS from celestial subspace of the ``WCS``. Also, now `WCS.to_fits_sip`` supports arbitrary order of output axes. [#357] API Changes ^^^^^^^^^^^ - Modified interface to ``wcs_from_points`` function to better match analogous function in astropy. [#349] - ``Model._BoundingBox`` was renamed to ``Model.ModelBoundingBox``. [#376, #377] 0.16.1 (2020-12-20) ------------------- Bug Fixes ^^^^^^^^^ - Fix a regression with ``pixel_to_world`` for output frames with one axis. [#342] 0.16.0 (2020-12-18) ------------------- New Features ^^^^^^^^^^^^ - Added an option to `to_fits_sip()` to be able to specify the reference point (``crpix``) of the FITS WCS. [#337] - Added support for providing custom range of degrees in ``to_fits_sip``. [#339] Bug Fixes ^^^^^^^^^ - ``bounding_box`` now works with tuple of ``Quantities``. [#331] - Fix a formula for estimating ``crpix`` in ``to_fits_sip()`` so that ``crpix`` is near the center of the bounding box. [#337] - Allow sub-pixel sampling of the WCS model when computing SIP approximation in ``to_fits_sip()``. [#338] - Fixed a bug in ``to_fits_sip`` due to which ``inv_degree`` was ignored. [#339]
jperkin
pushed a commit
that referenced
this issue
Jun 7, 2024
# scales 1.3.0 ## Better type support * `rescale(I(x), ...)` and `rescale_mid(I(x), ...)` return `I(x)` unaltered (@teunbrand, #403). * Add a rescale method for `difftime` objects (#382) * Add better support for `difftime` objects. `label_timespan()` adds functionality for adding correct unit suffix to timespan data, `breaks_timespan()` adds functionality for finding pleasant breakpoints across the various bases in time units, while `transform_timespan()` wraps it all together and provides an alternative to `transform_hms()` (#212) ## Ranges * `train_continuous()` coerces `new` to numeric before calculating range (@teunbrand, #369). * Training on factor data no longer sorts the range after multiple training passes if the new `fct` argument of `train_discrete()` is used (#383) * The `DiscreteRange` class now keeps track on whether it has been trained on factor data. * Attempt to make the sort behavior of the range consistent for character vectors during training. Mixing of character and factor data will make the factor level order take precedence no matter if the training starts with a charactor vector ## Transformations * Transformation function have been renamed to `transform_*`-prefixed names instead of `*_trans`-suffixed names. This allows for a better tab-completion search of transformations. The S3 class of transformations has been renamed from `"trans"` to `"transform"`. `new_transform()` replaces `trans_new()` and `trim_to_domain()` replaces `trans_range()`. All old functions are kept for posterity. * `transform_sqrt()` no longer returns an inverse for values outside of its domain (#214) * Add an inverse (area) hyperbolic sine transformation `transform_asinh()`, which provides a logarithm-like transformation of a space, but which accommodates negative values (#297) * Correct the domain calculation for `transform_compose()` (@mjskay, #408). * Transformation objects can optionally include the derivatives of the transform and the inverse transform (@mjskay, #322). ## Misc * The `scale_cut` argument in `number()` now works as advertised for values below the lowest cut value (#346) * `scale_cut` will now choose a more appropriate cut in the case of the first cut creating an irrational-ish number. * Added a new option to the `style_positive` argument in `label_*()` functions. Setting this to `"space"` will add a figure space in front of the number to make it easier to align positive and negative values as figure space takes up the same amount of space as `-` (#366) * `label_dollar()` has been superseeded by `label_currency()` for clarity (#344) * Palette functions now have the `pal_`-prefix. The old `_pal`-suffixed versions are kept for backward compatibility.
jperkin
pushed a commit
that referenced
this issue
Sep 14, 2024
ContourPy 1.3.0 adds new ContourGenerator functions multi_lines
and multi_filled to calculate contour lines and filled contours
over a sequence of levels in a single function call. There are also
new functions to render, convert and dechunk the returns from
multi_lines and multi_filled.
This release adds support for Python 3.13, including free-threaded.
The latter should be considered experimental.
The use of np.nan as the lower_level or upper_level of
ContourGenerator.filled() is no longer permitted.
Enhancements:
multi_lines and multi_filled:
ContourGenerator.multi_lines and multi_filled (#338, #340, #342, #343)
Renderer.multi_lines and multi_filled (#341)
convert_multi_lines and convert_multi_filled (#348)
dechunk_multi_lines and dechunk_multi_filled (#345)
Prevent use of np.nanas lower or upper level in filled (#339)
Compatibility:
Support CPython 3.13 including free-threaded (#382, #384, #388, #408, #410, #411, #412, #423)
Support PyPy 3.10 (#404)
Code improvements:
Support improved typing in NumPy 2.1.0 (#422)
Documentation improvements:
Simpler sphinx cross-references (#361)
Add more doc cross-references to explain returned data formats (#366)
Remove download numbers for conda packages (#428)
Documentation for multi_lines and multi_filled (#390, #431)
Document possibility of duplicate contour points (#432)
Build, testing and CI improvements:
Add pytest option to log image differences to CSV file (#335)
Label flaky test (#385)
MSVC linking and std::mutex compiler flag (#391, #395, #414, #419, #427)
Add minimal test script (#399)
Bump minimum supported NumPy to 1.23 (#403)
Build and publish nightly wheels (#413, #425)
Bump default python version in CI to 3.12 (#430)
github-actions bot
pushed a commit
that referenced
this issue
Nov 3, 2024
# cpp11 0.5.0 ## R non-API related changes * Removed usage of the following R non-API functions: * `SETLENGTH()` * `SET_TRUELENGTH()` * `SET_GROWABLE_BIT()` These functions were used as part of the efficient growable vectors that cpp11 offered, i.e. what happens under the hood when you use `push_back()`. The removal of these non-API functions means that cpp11 writable vectors that have been pushed to with `push_back()` will likely force 1 extra allocation when the conversion from `cpp11::writable::r_vector<T>` to `SEXP` occurs (typically when you return a result back to R). This does not affect the performance of `push_back()` itself, and in general these growable vectors are still quite efficient (#362). * The `environment` class no longer uses the non-API function `Rf_findVarInFrame3()` (#367). * The `exists()` method now uses the new `R_existsVarInFrame()` function. * The `SEXP` conversion operator now uses the new `R_getVar()` function. Note that this is stricter than `Rf_findVarInFrame3()` in 3 ways. The object must exist in the environment (i.e. `R_UnboundValue` is no longer returned), the object cannot be `R_MissingArg`, and if the object was a promise, that promise is now evaluated. We have backported this new strictness to older versions of R as well. ## New features * `cpp11::writable::r_vector<T>::proxy` now implements copy assignment. Practically this means that `x[i] = y[i]` now works when both `x` and `y` are writable vectors (#300, #339). * New `writable::data_frame` constructor that also takes the number of rows as input. This accounts for the edge case where the input list has 0 columns but you'd still like to specify a known number of rows (#272). * `std::max_element()` can now be used with writable vectors (#334). * Read only `r_vector`s now have a move constructor and move assignment operator (#365). ## Improvements and fixes * Repeated assignment to a `cpp11::writable::strings` vector through either `x[i] = elt` or `x.push_back(elt)` is now more performant, at the tradeoff of slightly less safety (as long as `elt` is actually a `CHARSXP` and `i` is within bounds, there is no chance of failure, which are the same kind of invariants placed on the other vector types) (#378). * Constructors for writable vectors from `initializer_list<named_arg>` now check that `named_arg` contains a length 1 object of the correct type, and throws either a `cpp11::type_error` or `std::length_error` if that is not the case (#382). * `cpp11::package` now errors if given a package name that hasn't been loaded yet. Previously it would cause R to hang indefinitely (#317). * `cpp11::function` now protects its underlying function, for maximum safety (#294). * `cpp11::writable::r_vector<T>::iterator` no longer implicitly deletes its copy assignment operator (#360). * Added the missing implementation for `x.at("name")` for read only vectors (#370). * Fixed an issue with the `writable::matrix` copy constructor where the underlying SEXP should have been copied but was not. It is now consistent with the behavior of the equivalent `writable::r_vector` copy constructor. * Fixed a memory leak with the `cpp11::writable::r_vector` move assignment operator (#338). * Fixed an issue where writable vectors were being protected twice (#365). * The approach for the protection list managed by cpp11 has been tweaked slightly. In 0.4.6, we changed to an approach that creates one protection list per compilation unit, but we now believe we've found an approach that is guaranteed by the C++ standard to create one protection list per package, which makes slightly more sense and still has all the benefits of the reduced maintanence burden mentioned in the 0.4.6 news bullet (#364). A side effect of this new approach is that the `preserved` object exposed through `protect.hpp` no longer exists. We don't believe that anyone was using this. This also means you should no longer see "unused variable" warnings about `preserved` (#249). ## Breaking changes * R >=3.6.0 is now required. This is in line with (and even goes beyond) the tidyverse standard of supporting the previous 5 minor releases of R. * Implicit conversion from `sexp` to `bool`, `size_t`, and `double` has been marked as deprecated and will be removed in the next version of cpp11. The 3 packages that were using this have been notified and sent PRs. The recommended approach is to instead use `cpp11::as_cpp<T>`, which performs type and length checking, making it much safer to use. * Dropped support for gcc 4.8, mainly an issue for extremely old CentOS 7 systems which used that as their default compiler. As of June 2024, CentOS 7 is past its vendor end of support date and therefore also out of scope for Posit at this time (#359).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To be clear, I do not expect anything very new to be pre-built, but it is not required. I am rather looking for some rather dated stuff, which could still be better than available elsewhere. For example, GHC 7.10.3 (so far I was able to fix the build of 7.6.3, but not later versions).
The text was updated successfully, but these errors were encountered: