HexChat gone? #345
Assignees
Comments
|
I'll add this to the list of required packages and make sure it's in the next build. |
Thank you! |
|
hexchat is now available again. |
jperkin
pushed a commit
that referenced
this issue
May 5, 2023
5.0.5 (2023-04-13) ------------------ Minor changes: - Added support for BYWEEKDAY in vRecur ref: #268 Bug fixes: - Fix problem with ORGANIZER in FREE/BUSY #348 5.0.4 (2022-12-29) ------------------ Minor changes: - Improved documentation Ref: #503, #504 Bug fixes: - vBoolean can now be used as an parameter Ref: #501 Fixes: #500 [jacadzaca] 5.0.3 (2022-11-23) ------------------ New features: - vDDDTypes is hashable #487 #492 [niccokunzmann] Bug fixes: - vDDDTypes' equality also checks the dt attribute #497 #492 [niccokunzmann] 5.0.2 (2022-11-03) ------------------ Minor changes: - Refactored cal.py, tools.py and completed remaining minimal refactoring in parser.py. Ref: #481 [pronoym99] - Calendar.from_ical no longer throws long errors Ref: #473 Fixes: #472 [jacadzaca] - Make datetime value shorter by removing the value parameter where possible. Fixes: #318 [jacadzaca], [niccokunzmann] New features: - source code in documentation is tested using doctest #445 [niccokunzmann] Bug fixes: - broken properties are not added to the parent component Ref: #471 Fixes: #464 [jacadzaca] 5.0.1 (2022-10-22) ------------------ Minor changes: - fixed setuptools deprecation warnings [mgorny] Bug fixes: - a well-known timezone timezone prefixed with a `/` is treated as if the slash wasn't present Ref: #467 Fixes: #466 [jacadzaca] 5.0.0 (2022-10-17) ------------------ Minor changes: - removed deprecated test checks [tuergeist] - Fix: cli does not support DURATION #354 [mamico] - Add changelog and contributing to readthedocs documentation #428 [peleccom] - fixed small typos #323 [rohnsha0] - unittest to parametrized pytest refactoring [jacadzaca] Breaking changes: - Require Python 3.7 as minimum Python version. [maurits] [niccokunzmann] - icalendar now takes a ics file directly as an input - icalendar's CLI utility program's output is different - Drop Support for Python 3.6. Versions 3.7 - 3.11 are supported and tested. New features: - icalendar utility outputs a 'Duration' row - icalendar can take multiple ics files as an input Bug fixes: - Changed tools.UIDGenerator instance methods to static methods Ref: #345 [spralja] - proper handling of datetime objects with `tzinfo` generated through zoneinfo.ZoneInfo. Ref: #334 Fixes: #333 [tobixen] - Timestamps in UTC does not need tzid Ref: #338 Fixes: #335 [tobixen] - add ``__eq__`` to ``icalendar.prop.vDDDTypes`` #391 [jacadzaca] - Refactor deprecated unittest aliases for Python 3.11 compatibility #330 [tirkarthi] 5.0.0a1 (2022-07-11) -------------------- Breaking changes: - Drop support for Python 3.4, 3.5 and PyPy2. [maurits] New features: - Document development setup Ref: #358 [niccokunzmann] Bug fixes: - Test with GitHub Actions. [maurits]
jperkin
pushed a commit
that referenced
this issue
Jun 2, 2023
################################################################################ Changed in xts 0.13.1: o Ignore attribute order in `all.equal()`. Attribute order shouldn't matter. That can be checked with `identical()`. o Only call `tzone()` and `tclass()` once in `check.TZ()`. Calling these functions multiple times throws multiple warnings for xts objects created before the tclass and tzone were attached to the index instead of the xts object. (#306) o Add instructions to update old objects. Old xts objects do not have tclass and tzone attributes on the index. Add a function to update the object attributes and add a note to the warning to show how to use it. (#306) o Return 'POSIXct' if object has no 'tclass'. An empty string is not a valid 'tclass', so it can cause an error. o Add notes on `plot.xts()` nomenclature and structure. Also add ASCII art to illustrate definitions and layout. (#103) o Remove 'tis' support. The implementation was not even a bare minimum, and it's not clear it even worked correctly. (#398) o Register missing S3 methods and update signatures. With R-devel (83995-ish), `R CMD check` notes these S3 methods are not registered. It also notes that the signatures for `as.POSIXct.tis()` and `str.replot_xts()` do not match the respective generics. It also thinks `time.frequency()` is a S3 method because `time()` is a generic. The function isn't exported, so renaming won't break any external code. Thanks to Kurt Hornik for the report. (#398) o Format each column individually before printing. The top/bottom rows could have a different number of decimal places and there are often multiple variying spaces between columns. For example: close volume ma bsi 2022-01-03 09:31:00 476.470 803961.000 NA 54191.000 2022-01-03 09:32:00 476.700 179476.000 NA 53444.791 2022-01-03 09:33:00 476.540 197919.000 NA -16334.994 ... 2023-03-16 14:52:00 394.6000 46728.0000 392.8636 28319.4691 2023-03-16 14:53:00 394.6500 64648.0000 392.8755 15137.6857 2023-03-16 14:54:00 394.6500 69900.0000 392.8873 -1167.9368 There are 4 spaces between the index and the 'close' column, 2 between 'close' and 'volume', 4 between 'volume' and 'ma', and 2 between 'ma' and 'bsi'. There should be a consistent number of spaces between the columns. Most other classes of objects print with 1 space between the columns. The top rows have 3 decimals and the bottom rows have 4. These should also be the same. (#321) o Only convert printed index values to character. Converting the entire index to character is time-consuming for xts objects with many observations. It can take more than a second to print an xts object with 1mm observations. o Make column names based on number of columns. The original code was a lot more complicated because it tried to account for truncating the number of printed columns. That functionality was removed because of how complicated it was. So now we can simply create printed column names from the number of columns. (#395) o Fix `xts()` for zero-row data.frame. The `xts()` constructor would create an object with a list for coredata when 'x' is a data.frame with no rows. It needs to convert 'x' to a matrix and throw an error if 'x' is a list. (#394) o Reduce instances when `dplyr::lag()` warning is shown. The warning was shown whenever it detected dplyr is installed, even if the user wasn't actively using dplyr. That caused an excessive amount of noise when other packages attached xts (e.g. quantmod). Thanks to Duncan Murdoch for the report and suggested fix! (#393) o Keep colname when only one non-time-based column. The subset `x[, -which.col]` would return a vector when the data frame has a time-based column and only one additional column. Do not drop dimensions, so 'x' will still be a data.frame in this case. (#391) o Treat NA the same as NULL for start or end values. NULL represents an undefined index value. NA represents an unknown or missing index value. xts does not allow NA as index values. Subsetting an xts or zoo object by NA returns a zero-length object. So a NA (unknown) index value is essentially the same as an undefined index value. (#383, #345) o Warn and remove NA when `periodicity()` called on date-time with NA. Otherwise the uninformative error below will be thrown. (#289) Error in try.xts(x, error = "'x' needs to be timeBased or xtsible") : 'x' needs to be timeBased or xtsible o Account for TZ when making names for `split.xts()`. `as.yearmon.POSIXct()` always sets `tz = "GMT"` when calling `as.POSIXlt()`, regardless of the xts' index tzone. That can cause the `as.yearmon()` results to be different days for GMT and the index's timezone. Use `format.POSIXct()` for "months" because it checks for a 'tzone' attribute before converting to POSIXlt and calling `format.POSIXlt()`. The conversion to POSIXlt is important because it checks and uses the 'tzone' attribute before considering the 'tz' argument. So it effectively ignores the `tz = "GMT"` setting in `as.yearmon()`. This is also the reason for calling `as.POSIXlt()` before calling `as.yearqtr()`. (#392) ################################################################################ Changed in xts 0.13.0: ### New Features o Added a xts method for `na.fill()` to significantly increase performance when 'fill' is a scalar. (#259) o `as.xts()` will look for a time-based column in a data.frame if it cannot create an index from the row names. (#381) o Change `print()` xts method to only show the first and last 'show.rows' rows if number of rows is > 'max.rows'. (#321) o Made `str()` output more descriptive for xts objects. It now differentiates between xts objects that are empty, zero-width, or zero-length, and defines each type of object. It also adds column names to the output. (#168, #378) o Add startup warning that `dplyr::lag()` breaks method dispatch, which means calls to `lag(my_xts)` won't work any more. o Added open-ended time of day subsetting ranges. This allows users to subset by time of day from the start/end of the day without providing the start/end times (00:00:00.000/23:59:59.999). For example: x["/T1800"] # between the start of the day and 5pm x["T0500/"] # between 5am and the end of the day Thanks to Chris Katsulis for the suggestion! (#243) o Updated `to.period()` to accept custom 'endpoints' via the 'period' argument. Now you can aggregate on something other than the times that 'endpoints()' supports. Thanks to Ethan B. Smith for the suggestion! (#302) ### Fixes o Fixed typo and expand `period.apply()` documentation. (#205) The original description has: * "the data from INDEX[k] to INDEX[k+1]" But that's not consistent with the code. It should be: * "the data from INDEX[k]+1 to INDEX[k+1]" o Calls to `merge.xts()` on zero-width objects now match `merge.zoo()`. Previously, `merge.xts()` would return empty xts objects if called on two or more zero-width xts objects. `merge.zoo()` would return a zero-width object with the correct index. (#227, #379) o Fixed `Ops.xts()` so it always returned an object with the same class as the first (left-hand side) argument. It previously returned an xts object even if the first argument was a subclass of xts. (#49) ### Other o Migrated unit tests from RUnit to tinytest. Thanks Mark van der Loo! o Updated the `endpoints()` documentation to make it clearer that the result is based on the UNIX epoch (midnight 1970, UTC). Thanks to GitHub user Eluvias for the suggestion! (#299) o Fixed `reclass()` to ensure it always adds index attributes from the 'match.to' argument. It was not copying `tclass`, `tzone`, or `tformat` from 'match.to' to the result object. (#43) o Removed an unnecessary check in `na.locf()` (which is not user-facing). Thanks to GitHub user @cgiachalis for the suggestion! (#307) o Updated C entry points so they're not able to accidentally be found via dynamic lookup (i.e. `.Call("foo", ...)`). This makes each call to the C code a few microseconds faster, which is nice. (#260) o Made `merge.xts()` results consistent with `merge.zoo()` for zero-length xts objects with columns. The result of `merge.xts()` did not include the columns of any objects that had one or more columns, but zero rows. A join should include all the columns of the joined objects, regardless of the number of rows in the object. This is consistent with `merge.zoo()`. Thanks to Ethan B. Smith for the report and testing! (#222)
jperkin
pushed a commit
that referenced
this issue
Jan 9, 2024
1.59 2023-12-31 14:52:12-08:00 America/Los_Angeles * Fixed XETRA, Tradegate and SInvestor after webpage was restructured - Issue #350 * Fidelity.pm temporarily disabled - Issue #346 * Finanzpartner.pm - Fix scraper, did not work if quote was higher than the previous day's quote. * GoogleWeb.pm - Updated to retrieve mutual fund and BATS prices - Issue #355 * BSEIndia.pm - Updated to use standardized data file at URL https://www.bseindia.com/download/BhavCopy/Equity/BSE_EQ_BHAVCOPY_{DDMMYYYY}.ZIP Eliminated need to use temp folders by storing standardized file data from URL into a variable. Updated names of source fields to conform to those in the standardized data file * IndiaMutual.pm - Eliminated need to use temp folders by storing nav file data from URL into a variable. * TMX.pm - Correct a self-reference in documentation - PR #345 * Stooq.pm - Added new currencies and a fix for commodities' prices * YahooWeb.pm - Skip rows in the price table where the prices are "-". This seems to happen sometimes with TIAA (and perhaps other) securities including TILIX and QCILIX * TSP.pm - Was not returning hash when the HTTP GET failed completely or the content did not contain the expected CSV file. - Issue #338 * BSEIndia.pm - Removed print when symbol not found - Issue #335
jperkin
pushed a commit
that referenced
this issue
Jan 25, 2024
# cpp11 0.4.7 * Internal changes requested by CRAN to fix invalid format string tokens (@paleolimbot, #345). # cpp11 0.4.6 * R >=3.5.0 is now required to use cpp11. This is in line with (and even goes beyond) the tidyverse standard of supporting the previous 5 minor releases of R. It also ensures that `R_UnwindProtect()` is available to avoid C++ memory leaks (#332). * `cpp11::preserved.release_all()` has been removed. This was intended to support expert developers on R <3.5.0 when cpp11 used a global protection list. Since cpp11 no longer uses a global protection list and requires R >=3.5.0, it is no longer needed. As far as we can tell, no package was actively using this (#332). * cpp11 now creates one protection list per compilation unit, rather than one global protection list shared across compilation units and across packages. This greatly reduces the complexity of managing the protection list state and should make it easier to make changes to the protection list structure in the future without breaking packages compiled with older versions of cpp11 (#330). * Nested calls to `cpp11::unwind_protect()` are no longer supported or encouraged. Previously, this was something that could be done for performance improvements, but ultimately this feature has proven to cause more problems than it is worth and is very hard to use safely. For more information, see the new `vignette("FAQ")` section titled "Should I call `cpp11::unwind_protect()` manually?" (#327). * The features and bug fixes from cpp11 0.4.4 have been added back in. # cpp11 0.4.5 * On 2023-07-20, cpp11 was temporarily rolled back to 0.4.3 manually by CRAN due to a bug in 0.4.4 which we could not immediately fix due to the cpp11 maintainer being on vacation. # cpp11 0.4.4 * Davis Vaughan is now the maintainer. * `as_doubles()` and `as_integers()` now propagate missing values correctly (#265, #319). * Fixed a performance issue related to nested `unwind_protect()` calls (#298). * Minor performance improvements to the cpp11 protect code. (@kevinushey) * `cpp_register()` gains an argument `extension=` governing the file extension of the `src/cpp11` file. By default it's `.cpp`, but `.cc` is now supported as well (#292, @MichaelChirico)
jperkin
pushed a commit
that referenced
this issue
Jul 1, 2024
3.15.4 Pass file_lock as positional argument by @kwist-sgr in #347 3.15.3 Add test for virtualenv stability by @gaborbernat in #344 Fix TypeError: _CountedFileLock.__init__() got an unexpected keyword argument 'timeout' by @kwist-sgr in #345 3.15.2 Use a metaclass to implement the singleton pattern by @kwist-sgr in #340
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)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was able to install HexChat using pkgsrc on my MacBook Air (M1, 2020) running macOS Monterey 12.6 (21G115)... I did reinstall of the OS and now I get this when I try to install HexChat:
Was it removed from the repository?
The text was updated successfully, but these errors were encountered: