Re: [Distutils] Unable to install packages after specifying package version

[P.J. Eby]

At 04:04 PM 12/7/2010 +0530, devyan parmar wrote:


On Fri, Dec 3, 2010 at 10:14 PM, P.J. Eby 
<p...@telecommunity.com> wrote:

At 04:25 PM 12/3/2010 +0530, devyan parmar wrote:
Hello,

i am trying to install package from my packageserver using PIP.

for example:
m trying
/bin/pip install 
--extra-index-url=<http://mypkgserver/dev>http://mypkgserver/dev 
package_name==2.4.12b



"2.4.12b" is the version of my package but in package server it is 
going as "2.4.12b_1" extra part in version is nothing but a build 
number which getting generated from hudson JOB.

is setuptool avoids extra build number which goes with my pcakage version ??


 No.  That's why it's not being found.  Ask for 
"package_name==2.4.12b-1" instead.



Is there  any way to avoid the extra hudson build number which is 
coming with my package version ??


Er, don't put it in there?

 coz i need that build number to check which package build test got 
failed...and issue is in package/setup.py i am specifying only 
versions of dependent package.


Don't use '==', then, use '>='.

and pip install is looking for only those particular version package 
in package server, but finds hudson build number attached with 
package version which is mismatching with setup.py install requires .


can you help me how version is getting identified from the package 
by setuptools.??


Thanks Regards
devyan parmar


___
Distutils-SIG maillist  -  Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] msi installer for 64-bit Windows?

[Martin v. Löwis]

> I'm trying to figure out how to produce a Windows installer for
> pure-Python packages such that it will "just run" on a 64-bit Windows
> platform.

You'll need a 64-bit Python installation to build the 64-bit installer.

> The distutils docs for Python 2.7.1 say: ""In most cases, the bdist_msi
> installer is a better choice than the bdist_wininst installer, because it
> provides better support for Win64 platforms, allows administrators to
> perform non-interactive installations, and allows installation through
> group policies.""" but give no more detail.

The Win64 part may be outdated; bdist_wininst can now create Win64
installers (for AMD64) as well.

> Does the win32 version work on win64?

Yes, but it will require a 32-bit Python to be installed on the target
system.

> Is the purpose of changing the name
> solely in order that win64 users are not deterred from using it because
> the name includes "win32"?

Yes, it only affects the resulting filename.

Regards,
Martin
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig

[Distutils] msi installer for 64-bit Windows?

[John Machin]

Hello,

I'm trying to figure out how to produce a Windows installer for
pure-Python packages such that it will "just run" on a 64-bit Windows
platform.

I'm running a 32-bit Windows (Windows 7 Pro), and the msi produced by

python setup.py bdist_msi

works just fine on Win 7 Pro. I don't have a win64 platform to test on.

The distutils docs for Python 2.7.1 say: ""In most cases, the bdist_msi
installer is a better choice than the bdist_wininst installer, because it
provides better support for Win64 platforms, allows administrators to
perform non-interactive installations, and allows installation through
group policies.""" but give no more detail.

Running

python setup.py bdist_msi --help

produces only one item of interest:

Options for 'bdist_msi' command:
  --plat-name (-p)   platform name to embed in generated filenames
(default: win32)

Does the win32 version work on win64? Is the purpose of changing the name
solely in order that win64 users are not deterred from using it because
the name includes "win32"?

Cheers,
John



___
Distutils-SIG maillist  -  Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] Unable to install packages after specifying package version

[devyan parmar]

On Fri, Dec 3, 2010 at 10:14 PM, P.J. Eby  wrote:

> At 04:25 PM 12/3/2010 +0530, devyan parmar wrote:
>
>> Hello,
>>
>> i am trying to install package from my packageserver using PIP.
>>
>> for example:
>> m trying
>> /bin/pip install --extra-index-url=
>> http://mypkgserver/dev package_name==2.4.12b
>>
>>
>> "2.4.12b" is the version of my package but in package server it is going
>> as "2.4.12b_1" extra part in version is nothing but a build number which
>> getting generated from hudson JOB.
>> is setuptool avoids extra build number which goes with my pcakage version
>> ??
>>
>
>  No.  That's why it's not being found.  Ask for "package_name==2.4.12b-1"
> instead.
>

Is there  any way to avoid the extra hudson build number which is coming
with my package version ?? coz i need that build number to check which
package build test got failed...and issue is in package/setup.py i am
specifying only versions of dependent package.
and pip install is looking for only those particular version package in
package server, but finds hudson build number attached with package version
which is mismatching with setup.py install requires .

can you help me how version is getting identified from the package by
setuptools.??

Thanks Regards
devyan parmar
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig