Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

standard tasks don't call overridden tasks #157

Open
DanLipsitt opened this issue Feb 20, 2016 · 1 comment
Open

standard tasks don't call overridden tasks #157

DanLipsitt opened this issue Feb 20, 2016 · 1 comment
Projects

Comments

@DanLipsitt
Copy link

I thought that if I overrode a command such as build, standard distutils tasks such as bdist would then call my version of the task instead of the original. This doesn't appear to be the case. Do I need to override every single task downstream from the one I want to change (bdist, bdist_wheel, etc.)?

Here's my example pavement.py:

from paver.easy import *
from paver.setuputils import setup

setup()

@task
def build():
    print('### running overridden build command ###')

When I run paver build, it prints out my message as expected. However, when I run paver bdist, it doesn't runs the standard build task instead of mine:

$ paver bdist
running bdist
running bdist_dumb
running build
installing to build/bdist.macosx-10.8-x86_64/dumb
running install
# etc...

Am I doing something wrong, or am I misunderstanding how paver is supposed to work?

I have tested this with paver 1.2.4 on python 2.7 and 3.5.

@Almad
Copy link
Member

Almad commented May 8, 2016

Note to self, still a thing. Probably to be solved with #162

@Almad Almad added this to To Do in Paver 1.3 Dec 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Paver 1.3
  
To Do
Development

No branches or pull requests

2 participants