Number of commits found: 20

devel/py-apscheduler: update to 3.6.3

Changes:	https://github.com/agronholm/apscheduler/compare/v3.6.1...v3.6.3
Reported by:	Repology

devel/py-apscheduler: update to 3.6.1

Changes:	https://github.com/agronholm/apscheduler/compare/v3.6.0...v3.6.1
Reported by:	portscout

devel/py-apscheduler: update to 3.6.0

Changes:	https://github.com/agronholm/apscheduler/compare/v3.5.3...v3.6.0

devel/py-apscheduler: bump pytest version requirment

$ make test
[...]
=============================== warnings summary ===============================
<undetermined location>
  pytest-capturelog plugin has been merged into the core, please remove it from
your requirements.

devel/py-apscheduler: update to 3.5.3

Changes:	https://github.com/agronholm/apscheduler/compare/v3.5.1...v3.5.3

Use PY_FLAVOR for dependencies.

FLAVOR is the current port's flavor, it should not be used outside of
this scope.

Sponsored by:	Absolight

Simplify Makefile: use PY_FUTURES

With hat:	python

devel/py-apscheduler: update to 3.5.1

Changes:	https://github.com/agronholm/apscheduler/compare/v3.5.0...v3.5.1

Simplify some USES=python

With hat:	portmgr

devel/py-apscheduler: update to 3.5.0

Changes:	https://github.com/agronholm/apscheduler/compare/v3.4.0...v3.5.0

Convert Python ports to FLAVORS.

  Ports using USE_PYTHON=distutils are now flavored.  They will
  automatically get flavors (py27, py34, py35, py36) depending on what
  versions they support.

  There is also a USE_PYTHON=flavors for ports that do not use distutils
  but need FLAVORS to be set.  A USE_PYTHON=noflavors can be set if
  using distutils but flavors are not wanted.

  A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
  added to cope with Python ports that did not have the Python
  PKGNAMEPREFIX but are flavored.

  USES=python now also exports a PY_FLAVOR variable that contains the

(Only the first 15 lines of the commit message are shown above )

devel/py-apscheduler: update to 3.4.0

Changes:	https://github.com/agronholm/apscheduler/compare/v3.3.1...v3.4.0

devel/py-apscheduler: update to 3.3.1

Changes:	https://github.com/agronholm/apscheduler/compare/v3.3.0...3.3.1

devel/py-apscheduler: update to 3.3.0

- Assume maintainership

Changes:	https://github.com/agronholm/apscheduler/compare/v3.2.0...v3.3.0
PR:		215187
Approved by:	wg (previous maintainer)

Invoke pytest from within desired python version

When testing a port for a non-default python py.test may fail to find
dependencies for default version because they weren't built e.g.,

$ make test PYTHON_VERSION=python3.5 -C devel/py-apscheduler
[...]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/site-packages/_pytest/config.py", line 319, in
_importconftest
    mod = conftestpath.pyimport()
  File "/usr/local/lib/python3.5/site-packages/py/_path/local.py", line 650, in
pyimport
    __import__(modname)
  File
"/usr/ports/devel/py-apscheduler/work/APScheduler-3.2.0/tests/conftest.py", line
8, in <module>
    from apscheduler.job import Job
  File
"/usr/ports/devel/py-apscheduler/work/APScheduler-3.2.0/apscheduler/job.py",
line 4, in <module>
    import six
ImportError: No module named 'six'
ERROR: could not load
/usr/ports/devel/py-apscheduler/work/APScheduler-3.2.0/tests/conftest.py

Approved by:	portmgr blanket

devel/py-apscheduler: fix python package version after r418353

>>> import apscheduler
>>> apscheduler.__version__
'0.0.0'

PR:		210980
Submitted by:	Andrej Ebert <andrej@ebert.su>

devel/py-apscheduler: update to 3.2.0

- Convert to the testing framework

Changes:	https://github.com/agronholm/apscheduler/compare/v3.0.4...v3.2.0
PR:		210980
Submitted by:	Andrej Ebert <andrej@ebert.su> (based on)

Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g.

With hat:	portmgr
Sponsored by:	Absolight

devel/py-apscheduler: update to 3.0.4

devel/py-apscheduler: add new port

Advanced Python Scheduler (APScheduler) is a Python library that lets
you schedule your Python code to be executed later, either just once
or periodically. You can add new jobs or remove old ones on the fly as
you please. If you store your jobs in a database, they will also
survive scheduler restarts and maintain their state. When the
scheduler is restarted, it will then run all the jobs it should have
run while it was offline.

https://pypi.python.org/pypi/APScheduler

Approved by:	wg (maintainer)
Differential Revision:	https://reviews.freebsd.org/D3566

Number of commits found: 20

9 vulnerabilities affecting 58 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities

Last updated:
2020-02-19 18:07:17