Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
RPM packaging and nose
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Philip Stephens  
View profile  
 More options Apr 10 2012, 8:14 pm
From: Philip Stephens <phil.stp...@gmail.com>
Date: Tue, 10 Apr 2012 17:14:35 -0700 (PDT)
Local: Tues, Apr 10 2012 8:14 pm
Subject: RPM packaging and nose

Hello,

I setup nose for our python library, and it works great.  I have a user
trying to package an RPM, and he runs into the issue that 'python setup.py
install' runs all nosetests -- which gets in his way.  Is this a default
behavior? How can I prevent this?

Thanks,
Phil


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
jason pellerin  
View profile  
 More options Apr 11 2012, 9:31 am
From: jason pellerin <jpelle...@gmail.com>
Date: Wed, 11 Apr 2012 09:31:53 -0400
Local: Wed, Apr 11 2012 9:31 am
Subject: Re: [nose-users] RPM packaging and nose
There's nothing that I know of in nose itself that would cause another
package to do something like run tests when 'python setup.py install`
was run, or when the package was being put into an RPM. Sounds like a
custom setup.py file or something, triggering the test command before
the install command.

JP


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »