Gotcha!
On Sun, Jul 22, 2018 at 4:12 PM, Paul G wrote:
> That's what "calendar based versioning" means. It refers to the year of
> release. See https://calver.org
>
>
> On July 22, 2018 11:07:58 PM UTC, Bill Deegan
> wrote:
>>
>> I noticed the v
?
Thanks,
Bill Deegan
SCons Project Co-Manager
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
Daniel,
Perhaps the better way to go about it than to call scons N times is to have
N variant dirs? where there's a variant dir for each build type you want,
and then youd call
scons build_wheel
which is aliased Alias('build_wheel','variant_dir for building wheel path')
Maybe bring this up on
Greetings,
I recently uploaded version 2.4.0 of SCons.
For some reason pip wasn't installing 2.4.0 but was pulling 2.3.6 so I
figured I'd delete the release and re-upload.
Then I get the following errors:
Submitting dist/scons-2.4.0.tar.gz to https://pypi.python.org/pypi
Upload failed (400):
Gordon,
If you are sure that your dev and production environments match, then you
should have same shared libraries on both, and no need for static linkage?
-Bill
On Mon, Mar 23, 2015 at 11:36 AM, Dan Stromberg drsali...@gmail.com wrote:
On Thu, Sep 11, 2014 at 5:28 AM, gordon
