Skip to content
This repository has been archived by the owner on Dec 5, 2019. It is now read-only.

Update python-dateutil to 2.6.0 #117

Closed
wants to merge 1 commit into from

Conversation

pyup-bot
Copy link
Contributor

There's a new version of python-dateutil available.
You are currently using 2.5.3. I have updated it to 2.6.0

These links might come in handy: PyPI | Changelog | Docs

Changelog

2.6.0


  • Added PEP-495-compatible methods to address ambiguous and imaginary dates in
    time zones in a backwards-compatible way. Ambiguous dates and times can now
    be safely represented by all dateutil time zones. Many thanks to Alexander
    Belopolski (abalkin) and Tim Peters tim-one for their inputs on how to
    address this. Original issues reported by Yupeng and zed (lP: 1390262,
    gh issues 57, 112, 249, 284, 286, prs 127, 225, 248, 264, 302).
  • Added new methods for working with ambiguous and imaginary dates to the tz
    module. datetime_ambiguous() determines if a datetime is ambiguous for a given
    zone and datetime_exists() determines if a datetime exists in a given zone.
    This works for all fold-aware datetimes, not just those provided by dateutil.
    (gh issue 253, gh pr 302)
  • Fixed an issue where dst() in Portugal in 1996 was returning the wrong value
    in tz.tzfile objects. Reported by abalkin (gh issue 128, pr 225)
  • Fixed an issue where zoneinfo.ZoneInfoFile errors were not being properly
    deep-copied. (gh issue 226, pr 225)
  • Refactored tzwin and tzrange as a subclass of a common class, tzrangebase, as
    there was substantial overlapping functionality. As part of this change,
    tzrange and tzstr now expose a transitions() function, which returns the
    DST on and off transitions for a given year. (gh issue 260, pr 302)
  • Deprecated zoneinfo.gettz() due to confusion with tz.gettz(), in favor of
    get() method of zoneinfo.ZoneInfoFile objects. (gh issue 11, pr 310)
  • For non-character, non-stream arguments, parser.parse now raises TypeError
    instead of AttributeError. (gh issues 171, 269, pr 247)
  • Fixed an issue where tzfile objects were not properly handling dst() and
    tzname() when attached to datetime.time objects. Reported by ovacephaloid.
    (gh issue 292, pr 309)
  • /usr/share/lib/zoneinfo was added to TZPATHS for compatibility with Solaris
    systems. Reported by dhduvall (gh issue 276, pr 307)
  • tzoffset and tzrange objects now accept either a number of seconds or a
    datetime.timedelta() object wherever previously only a number of seconds was
    allowed. (gh pr 264, 277)
  • datetime.timedelta objects can now be added to relativedelta objects. Reported
    and added by Alec Nikolas Reiter (justanr) (gh issue 282, pr 283
  • Refactored relativedelta.weekday and rrule.weekday into a common base class
    to reduce code duplication. (gh issue 140, pr 311)
  • An issue where the WKST parameter was improperly rendering in str(rrule) was
    reported and fixed by Daniel LePage (dplepage). (gh issue 262, pr 263)
  • A replace() method has been added to rrule objects by jendas1, which creates
    new rrule with modified attributes, analogous to datetime.replace (gh pr 167)
  • Made some significant performance improvements to rrule objects in Python 2.x
    (gh pr 245)
  • All classes defining equality functions now return NotImplemented when
    compared to unsupported classes, rather than raising TypeError, to allow other
    classes to provide fallback support. (gh pr 236)
  • Several classes have been marked as explicitly unhashable to maintain
    identical behavior between Python 2 and 3. Submitted by Roy Williams
    (rowillia) (gh pr 296)
  • Trailing whitespace in easter.py has been removed. Submitted by OmgImAlexis
    (gh pr 299)
  • Windows-only batch files in build scripts had line endings switched to CRLF.
    (gh pr 237)
  • adamchainz updated the documentation links to reflect that the canonical
    location for readthedocs links is now at .io, not .org. (gh pr 272)
  • Made some changes to the CI and codecov to test against newer versions of
    Python and pypy, and to adjust the code coverage requirements. For the moment,
    full pypy3 compatibility is not supported until a new release is available,
    due to upstream bugs in the old version affecting PEP-495 support.
    (gh prs 265, 266, 304, 308)
  • The full PGP signing key fingerprint was added to the README.md in favor of
    the previously used long-id. Reported by valholl (gh issue 287, pr 304)
  • Updated zoneinfo to 2016i. (gh issue 298, gh pr 306)

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 🤖

@mozilla-autolander-deprecated

Autolander could not find a bug number in your pull request title. All pull requests should be in the format of: Bug [number] - [description].

@codecov-io
Copy link

codecov-io commented Jan 13, 2017

Current coverage is 78.27% (diff: 100%)

Merging #117 into master will not change coverage

@@             master       #117   diff @@
==========================================
  Files            40         40          
  Lines          1169       1169          
  Methods           0          0          
  Messages          0          0          
  Branches        122        122          
==========================================
  Hits            915        915          
  Misses          230        230          
  Partials         24         24          

Powered by Codecov. Last update 7051fb7...3090ae0

@jezdez jezdez closed this Jan 17, 2017
@jezdez jezdez deleted the pyup-update-python-dateutil-2.5.3-to-2.6.0 branch January 17, 2017 10:39
jezdez pushed a commit that referenced this pull request Nov 12, 2018
Bumps [pycparser](https://github.com/eliben/pycparser) from 2.18 to 2.19.
<details>
<summary>Changelog</summary>

*Sourced from [pycparser's changelog](https://github.com/eliben/pycparser/blob/master/CHANGES).*

> + Version 2.19 (2018.09.19)
> 
>   - PR [#277](https://github-redirect.dependabot.com/eliben/pycparser/issues/277): Fix parsing of floating point literals
>   - PR [#254](https://github-redirect.dependabot.com/eliben/pycparser/issues/254): Add support for parsing empty structs
>   - PR [#240](https://github-redirect.dependabot.com/eliben/pycparser/issues/240): Fix enum formatting in generated C code (also [#216](https://github-redirect.dependabot.com/eliben/pycparser/issues/216))
>   - PR [#222](https://github-redirect.dependabot.com/eliben/pycparser/issues/222): Add support for #pragma in struct declarations
>   - There are reports that this release doesn't work with Python 2.6 ([#281](https://github-redirect.dependabot.com/eliben/pycparser/issues/281)).
>     Please note that the minimal supported version is 2.7; the required versions
>     are listed in the README file. 
> 
> + Version 2.18 (2017.07.04)
> 
>   - PR [#161](https://github-redirect.dependabot.com/eliben/pycparser/issues/161) & [#184](https://github-redirect.dependabot.com/eliben/pycparser/issues/184): Update bundled PLY version to 3.10
>   - PR [#158](https://github-redirect.dependabot.com/eliben/pycparser/issues/158): Add support for the __int128 type.
>   - PR [#169](https://github-redirect.dependabot.com/eliben/pycparser/issues/169): Handle more tricky TYPEID in declarators.
>   - PR [#178](https://github-redirect.dependabot.com/eliben/pycparser/issues/178): Add columns to the coord of each node
> 
> + Version 2.17 (2016.10.29)
> 
>   - Again functionality identical to 2.15 and 2.16; the difference is that the
>     tarball now contains Python files with properly set permissions.
> 
> + Version 2.16 (2016.10.18)
> 
>   - Functionally identical to 2.15, but fixes a packaging problem that caused
>     failed installation (_build_tables wasn't rerun in the pycparser/ dir).
> 
> + Version 2.15 (2016.10.18)
> 
>   - PR [#121](https://github-redirect.dependabot.com/eliben/pycparser/issues/121): Update bundled PLY version to 3.8
>   - Issue [#117](https://github-redirect.dependabot.com/eliben/pycparser/issues/117): Fix parsing of extra semi-colons inside structure declarations.
>   - PR [#109](https://github-redirect.dependabot.com/eliben/pycparser/issues/109): Update c_generator to add {} around nested named initializers.
>   - PR [#101](https://github-redirect.dependabot.com/eliben/pycparser/issues/101): Added support for parsing pragmas into the AST.
>   - Additional fake headers and typedefs, manifest fixes ([#97](https://github-redirect.dependabot.com/eliben/pycparser/issues/97), [#106](https://github-redirect.dependabot.com/eliben/pycparser/issues/106), [#111](https://github-redirect.dependabot.com/eliben/pycparser/issues/111)).
>   - Testing with Python 3.5 instead of 3.3 now (3.4 and 3.5 are the 3.x versions
>     tested).
>   - PR [#145](https://github-redirect.dependabot.com/eliben/pycparser/issues/145): More complete support for offsetof()
>   - Issue [#116](https://github-redirect.dependabot.com/eliben/pycparser/issues/116): Fix line numbers recorded for empty and compound statements.
>   - Minor performance improvement to the invalid string literal regex.
> 
> + Version 2.14 (2015.06.09)
> 
>   - Added CParser parameter to specify output directory for generated parsing
>     tables ([#84](https://github-redirect.dependabot.com/eliben/pycparser/issues/84)).
>   - Removed lcc's cpp and its license from the distribution. Using lcc's cpp
>     is no longer recommended, now that Clang has binary builds available for
>     Windows.
> 
> + Version 2.13 (2015.05.12)
> 
></table> ... (truncated)
</details>
<details>
<summary>Commits</summary>

- [`caa4c11`](eliben/pycparser@caa4c11) Bump versions to 2.19
- [`bcb5f9f`](eliben/pycparser@bcb5f9f) Reformat dates in CHANGES to yyyy.mm.dd format
- [`40f0d91`](eliben/pycparser@40f0d91) Add test for parsing a hex float constant to the right type
- [`a915c3d`](eliben/pycparser@a915c3d) Correct Parsing of Floating Point Literals, issue [#253](https://github-redirect.dependabot.com/eliben/pycparser/issues/253) ([#277](https://github-redirect.dependabot.com/eliben/pycparser/issues/277))
- [`ccd673e`](eliben/pycparser@ccd673e) Merge branch 'master' of github.com:eliben/pycparser
- [`92f65b6`](eliben/pycparser@92f65b6) Add tests for empty struct/union typedecls
- [`8ff8088`](eliben/pycparser@8ff8088) Trim whitespace in test file
- [`a301cbb`](eliben/pycparser@a301cbb) Drop testing for EOL Pythons 3.2 & 3.3 ([#271](https://github-redirect.dependabot.com/eliben/pycparser/issues/271))
- [`0baa8f4`](eliben/pycparser@0baa8f4) Remove unnecessary __future__ import ([#266](https://github-redirect.dependabot.com/eliben/pycparser/issues/266))
- [`1d86699`](eliben/pycparser@1d86699) Use https:// for all project links where available ([#267](https://github-redirect.dependabot.com/eliben/pycparser/issues/267))
- Additional commits viewable in [compare view](eliben/pycparser@release_v2.18...release_v2.19)
</details>
<br />

[![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=pycparser&package-manager=pip&previous-version=2.18&new-version=2.19)](https://dependabot.com/compatibility-score.html?dependency-name=pycparser&package-manager=pip&previous-version=2.18&new-version=2.19)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

---

**Note:** This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking `Bump now` in your [Dependabot dashboard](https://app.dependabot.com).

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

</details>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants