pts, and then be able to run them without
> > regard to PATH?
>
> Absolut correct. This works.
>
> The question is if this is a "good" or "elegant" way from the viewpoint
> of different communities/projects (e.g. Python, setuptools, pip, other
> build-sy
s is a "good" or "elegant" way from the viewpoint
of different communities/projects (e.g. Python, setuptools, pip, other
build-systems, distros, something I forgot).
I assume that I'm not the first person with such a use case. So there
could be solutions out there. Maybe
On Mon, 19 Dec 2022 at 17:30, wrote:
>
> Am 18.12.2022 22:37 schrieb Mats Wichmann:
> > the which command uses your PATH, so I'm not sure you're buying
> > anything new there
>
> I'm using which before entering pkexec. ;)
>
> I'll show a demonstrator project later.
Hmm, then I'm not sure what
quot;pypa/pip" project pointed to from there own README.md [1].
To be complete. I also asked in in context of "pypa/setuptools" [2] and
on the debian-python mailing list.
Not all questions are exactly the same but touching the same meta topic.
"pypa/setuptools" themself
Am 18.12.2022 22:37 schrieb Mats Wichmann:
the which command uses your PATH, so I'm not sure you're buying
anything new there
I'm using which before entering pkexec. ;)
I'll show a demonstrator project later.
--
https://mail.python.org/mailman/listinfo/python-list
On 12/18/22 14:07, c.bu...@posteo.jp wrote:
Dear Chris,
thank you for your reply.
Am 18.12.2022 20:27 schrieb Chris Angelico:
Does it have to be in path? Can't you say
/usr/local/bin/entrypointname? Not sure what constitutes an elegant
solution here.
I asked that myself. My current solution
> On 18 Dec 2022, at 17:57, c.bu...@posteo.jp wrote:
>
> Hello,
>
> when I install a package on a GNU/Linux system via "sudo python3 -m pip
> install -e ." that defines entry points in its pyproject.toml the entry
> point starter scripts are located in /usr/locale/bin.
>
> That folder is in P
Dear Chris,
thank you for your reply.
Am 18.12.2022 20:27 schrieb Chris Angelico:
Does it have to be in path? Can't you say
/usr/local/bin/entrypointname? Not sure what constitutes an elegant
solution here.
I asked that myself. My current solution do determine the full path of
the entrypoint
Pip is fine for most packages, as it looks like you know. Some distros
put some packages in unusual places, and those are the ones that either
are not or should not be installed via pip. Which ones varies from
distro to distro. (I just include this information here for others who
haven't dis
On Mon, 19 Dec 2022 at 04:56, wrote:
>
> Hello,
>
> when I install a package on a GNU/Linux system via "sudo python3 -m pip
> install -e ." that defines entry points in its pyproject.toml the entry
> point starter scripts are located in /usr/locale/bin.
>
> That folder is in PATH for "regular" roo
Dear Gerard,
thank you for your reply.
Am 18.12.2022 19:45 schrieb Weatherby,Gerard:
"sudo python3 -m pip
install -e ."
You’ve already started down a problematic road. I recommend installing
root level Python packages through your system package manager. (apt
for debian, or whatever RedHat is u
2:56 PM
To: Python-list@python.org
Subject: pip/setuptools: Entry points not visible from pkexec-root-environment
*** Attention: This is an external email. Use caution responding, opening
attachments or clicking on links. ***
Hello,
when I install a package on a GNU/Linux system via "sudo
Hello,
when I install a package on a GNU/Linux system via "sudo python3 -m pip
install -e ." that defines entry points in its pyproject.toml the entry
point starter scripts are located in /usr/locale/bin.
That folder is in PATH for "regular" root users and by "sudo su" roots
users.
But I need to
On Fri, 18 Dec 2020, Joseph L. Casale wrote:
I just ran into this recently, I don't recall the actual source but it was
the version of setuptools having been so old. Your version is from Jun 3,
2016...
Update it, that was what worked for me.
jlc,
Upgraded to python-setuptools-51.0.0-x
> Installed on this Slackware-14.2/x86_64 workstation with python-3.9.1 are:
> python-setuptools-22.0.5-x86_64-1
I just ran into this recently, I don't recall the actual source but it was the
version
of setuptools having been so old. Your version is from Jun 3, 2016...
Update it, th
I want to use tkcalendar and dateentry in my application but have problems
with tkcalendar's dependency on babel and setuptools.
When I try to build babel it fails:
Traceback (most recent call last):
File "/tmp/SBo/babel-2.8.1/setup.py", line 7, in
from setuptoo
On 10May2020 13:00, John Ladasky wrote:
On Saturday, May 9, 2020 at 8:17:19 PM UTC-7, Cameron Simpson wrote:
I also autopatch the module itself to
set __version__ to match when I make that release tag.
Yes, that's exactly what the module I wrote for my company's internal use does. The
offic
On Saturday, May 9, 2020 at 8:17:19 PM UTC-7, Cameron Simpson wrote:
> I also autopatch the module itself to
> set __version__ to match when I make that release tag.
Yes, that's exactly what the module I wrote for my company's internal use does.
The official version number is hard-coded into se
On 08May2020 18:07, John Ladasky wrote:
I just came across a package in PyPI which is in a state of neglect. The
official version on the PyPI page is 1.3.1 -- but the installed module reports
its version as 1.2.0. This is confusing.
There are several bugs in this package besides the mismatc
On Friday, May 8, 2020 at 6:07:33 PM UTC-7, John Ladasky wrote:
> Is there a recommended way to keep the internal reference and the setup.py
> reference in sync? Is there any reason someone would NOT want these numbers
> to match?
Replying to myself... I just found this:
https://packaging.pyth
I just came across a package in PyPI which is in a state of neglect. The
official version on the PyPI page is 1.3.1 -- but the installed module reports
its version as 1.2.0. This is confusing.
There are several bugs in this package besides the mismatched version number.
I've forked a copy of
n source code that I am developing. I regularly
> change this code and "distribute" it to myself using setuptools. From the
> command prompt in the module's base folder, I execute:
>
> python3 setup.py sdist
> sudo python3 setup.py install
>
> That p
to myself using setuptools. From the
command prompt in the module's base folder, I execute:
python3 setup.py sdist
sudo python3 setup.py install
That process has been working for me for years. But after recent rebuilds,
when I try to import those modules today, I get ModuleNotFoundErrors f
On 09Nov2019 13:15, Cameron Simpson wrote:
On 08Nov2019 09:14, Chris Green wrote:
Cameron Simpson wrote:
Have you tried this?
pip install onkyo-eiscp
I have now and it worked perfectly. So why do the install
instructions for onkyo-eiscp say do "easy_install onkyo-eiscp"? It
definitely m
On 08Nov2019 09:14, Chris Green wrote:
Cameron Simpson wrote:
Have you tried this?
pip install onkyo-eiscp
I have now and it worked perfectly. So why do the install
instructions for onkyo-eiscp say do "easy_install onkyo-eiscp"? It
definitely means from the command line. I mean it's no
t;easy_install: command not found" when I try that. I do have
> >setuptools installed on my system and I can see "easy_install.py" in
> >the package installation area.
> >
> >This is on an xubuntu 19.04 Linux system.
> >
> >So what is wrong?
&g
On 07Nov2019 21:38, Chris Green wrote:
I'm a bit flummoxed.
I'm trying to install a Python package from pypi.org, it says it
should be installed by running "easy_install onkyo-eiscp" but I just
get "easy_install: command not found" when I try that. I do have
set
I'm a bit flummoxed.
I'm trying to install a Python package from pypi.org, it says it
should be installed by running "easy_install onkyo-eiscp" but I just
get "easy_install: command not found" when I try that. I do have
setuptools installed on my system and I ca
sted, I have checked the traceback and found the exception is
> > caused by
> > `/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/test/test_winreg.py`
> > on my machine with homebrew-installed Python3.
> >
> > I have realized that t
test` in my
> `setup.py`. `setuptools` will find the `test` package. But the package it
> found is not in my project. It found
> `/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/test`.
Yes. Apparently, you run the Python test suite - and de
/test_winreg.py`
on my machine with homebrew-installed Python3.
I have realized that the problem may be caused of `test-suite=test` in my
`setup.py`. `setuptools` will find the `test` package. But the package it found
is not in my project. It found
`/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework
No, it doesn't. The stackoverflow question you posted is about the renaming of
`winreg`. `_winreg` is renamed to `winreg`. That's why the poster can't find
the module. My program is written for and running on unix-like systems. I
think `winreg` should not appear here. I have tried running `pi
YuXuan Dong writes:
> I met a problem while I ran `python setup.py test`:
>
> unittest.case.SkipTest: No module named 'winreg'
> ... no windows modules should be necessary ...
I know apparently unexplainable "no module named ..." messages as
a side effect of the use of "six".
"six" is use
On Monday, 2 September 2019 04:44:29 UTC+10, YuXuan Dong wrote:
> Hi, everybody:
>
> I have met a problem while I ran `python setup.py test`:
>
> unittest.case.SkipTest: No module named 'winreg'
>
> I ran the command in MacOS and my project is written for only UNIX-like
> systems. I don'
Hi, everybody:
I have met a problem while I ran `python setup.py test`:
unittest.case.SkipTest: No module named 'winreg'
I ran the command in MacOS and my project is written for only UNIX-like
systems. I don't use any Windows-specified API. How dose `winreg` come here?
In my `setup.py`
Hi, everybody:
I met a problem while I ran `python setup.py test`:
unittest.case.SkipTest: No module named 'winreg'
I ran the command in MacOS and my project is written for only UNIX-like
systems. I don't use any Windows-specified API. How dose `winreg` come here?
In my `setup.py`:
stall python3-pip
Reading package lists... Done
Building dependency tree
Reading state information... Done
python3-pip is already the newest version (8.1.1-2ubuntu0.4).
> In any case, setuptools is listed in the recommends.
If setuptools isn't included, pip can fail.
I don't know if it will
from with:
$ apt-cache policy python3-pip
It probably means you have multiple package sources configured; or
perhaps you have one installed currently, and you could upgrade to a
slightly updated version.
In any case, setuptools is listed in the recommends.
ChrisA
--
https://mail.python.org/mailman/listinfo/python-list
ze: 556
Depends: ca-certificates, python-pip-whl (= 8.1.1-2ubuntu0.4),
python3:any (>= 3.4~)
Recommends: build-essential, python3-dev (>= 3.2), python3-setuptools,
python3-wheel
Filename: pool/universe/p/python-pip/python3-pip_8.1.1-2ubuntu0.4_all.deb
Size: 108962
MD5sum: e3dc92b0b965
On Thu, Jul 5, 2018 at 5:37 PM, Steven D'Aprano
wrote:
> I'm trying to install pip on a Linux Mint box. The maintainers of Mint
> (or possibly their upstream distro, Ubuntu) decided in their infinite
> wisdom to remove the ensurepip package, so
>
> python3 -m ensurepip
In Debian distros, a cu
ll-dev (>= 2.6), python-
setuptools,
python-wheel
...
Tags: admin::package-management, devel::lang:python, devel::packaging,
implemented-in::python, role::program
And:
~ $ aptitude show python3-pip
Package: python3-pip
Version: 9.0.1-2
...
Maintainer: Debian Pytho
pip
>
> fails ("No module named ensurepip"). Okay, let's do this the hard way:
>
> sudo apt install python3-pip
>
> Yay, that worked! So then I try using it:
>
> python3 -m pip install blahblahblah
>
> and after downloading the entire package, it
d way:
sudo apt install python3-pip
Yay, that worked! So then I try using it:
python3 -m pip install blahblahblah
and after downloading the entire package, it crashes:
ImportError: No module named 'setuptools'
because *of course* why would you treat setuptools as a depen
On 27/04/18 06:06, jimbo1qaz wrote:
> Frequently I have encountered projects packaged using setuptools, with a
> setup.py. To find out how to install it, I usually turned to Stack Overflow
> (https://stackoverflow.com/a/1472014) which doesn't explain what options
> exist or do.
Frequently I have encountered projects packaged using setuptools, with a
setup.py. To find out how to install it, I usually turned to Stack Overflow
(https://stackoverflow.com/a/1472014) which doesn't explain what options
exist or do.
Surprisingly, neither "setup.py" nor "setu
the lower level of
> Python package management. I started with pip, moved to setuptools and now
> set my sight on distlib.
>
> Can someone describe the specific dependencies of all the *packaging*
> libraries that `virtualenv` uses? And the dependencies between them?
>
> I be
I was working on a bugfix for Virtualenv, regarding very long shebang lines
that are breaking things. In the process, I realized that if I want really fix
to my particular issue it likely needs to be done on the lower level of Python
package management. I started with pip, moved to setuptools
ring/2016/04/11/unable-to-find-vcvarsall-bat/.
Following the directions of that blog:
o I installed Visual C++ Build Tools 2015. I tried running the program again
straight away (without updating setuptools) and I received a lot of error
messages which I didn't write down.
o Fol
On Friday, September 9, 2016 at 7:52:32 PM UTC+12, Mark Summerfield wrote:
> So, I need to have some hook that lets me run a python script after the build
> dir has been populated but before the distributable is made -- is this
> possible?
You can subclass distutils.command.build with your own cus
Hi,
I use setuptools (in my case with cx_Freeze) to package some of my Python
applications.
As part of this process a build\exe.win-amd64-3.4 dir is created with all the
necessary files, and then a separate dist\ dir is created with the
distributable package (e.g., a .msi file).
I'd li
On Sat, Jul 11, 2015 at 10:01 AM, wrote:
> On 2015-07-10 09:39 Chris Warrick wrote:
>> And you should not create the files in your install script. Instead,
>> install them to a different data dir (somewhere in 'share/appname', or
>> alongside your package). When someone runs your app, only then
On 2015-07-10 09:39 Chris Warrick wrote:
> And you should not create the files in your install script. Instead,
> install them to a different data dir (somewhere in 'share/appname', or
> alongside your package). When someone runs your app, only then you
> should copy this file to user’s config di
Hi Chris,
thank you for your answer.
On 2015-07-10 09:39 Chris Warrick wrote:
> You should NEVER use sudo with pip. Instead, use virtualenvs as a
> regular user, or create your own .deb packages.
I am not sure, but maybe this is an Ubuntu-specific "problem"?
When I don't use sudo I got error
s.
You can also use pip install --user to install to ~/.local
>> And you should not create the files in your install script. Instead,
>> install them to a different data dir (somewhere in 'share/appname'
>
> What do you mean with "data dir"? For a default config-fi
On 10 July 2015 at 03:11, wrote:
> I am using setuptools to create a wheel file.
>
> There is a conf-file I want to install into the users config-diretory.
> e.g. /home/user/.config/appname/app.conf
>
> setup(...,
> data_files = [ ('~/.config/appname/', [&#
I am using setuptools to create a wheel file.
There is a conf-file I want to install into the users config-diretory.
e.g. /home/user/.config/appname/app.conf
setup(...,
data_files = [ ('~/.config/appname/', ['app.conf']) ]
)
I see two problems here:
1.
I don&#x
Rob Gaddi writes:
> I'm having two issues trying to make setuptools do what I want to package
> up an application.
Those questions are on-topic here. It's worth noting, though, that you
may get better discussion of this by asking in the Distutils forum
https://www.python.or
I'm having two issues trying to make setuptools do what I want to package
up an application. Well, actually I'm having many issues, but I'll start
with the two that are foremost right now.
First, I've got documentation in RestructuredText format that I want to
cook down t
On Mon, Mar 16, 2015 at 7:10 AM, Wolfgang Maier <
wolfgang.ma...@biologie.uni-freiburg.de> wrote:
> On 03/16/2015 12:53 AM, Jason Friedman wrote:
>
>> Hello,
>>
>> This is Python 3.3.2 on Linux.
>> I downloaded Setuptools
>> (https://pypi.python.org/p
On 03/16/2015 12:53 AM, Jason Friedman wrote:
Hello,
This is Python 3.3.2 on Linux.
I downloaded Setuptools
(https://pypi.python.org/packages/source/s/setuptools/setuptools-14.3.tar.gz),
exploded the tarball, and I get:
python setup.py build
Traceback (most recent call last):
File "&q
Hello,
This is Python 3.3.2 on Linux.
I downloaded Setuptools (
https://pypi.python.org/packages/source/s/setuptools/setuptools-14.3.tar.gz),
exploded the tarball, and I get:
python setup.py build
Traceback (most recent call last):
File "", line 1521, in
_find_and_load_unlocked
Attr
I'm sure I've just misconfigured my setup.py, requirements.txt and/or project
structure, but I've tried:
* install_requires
* requirements.txt
* install_requires + dependency_links
With (for install_requires):
* bettertutors_sql_models==dev
* bettertutors_sql_models
For requirements.txt, depende
Ned, thank you for your insight on this problem. I will take your
advice and do some more digging. You've been very helpful.
Regards,
-
Matt Taylor
OS Community Flag-Bearer
Numenta
On Wed, Feb 11, 2015 at 4:23 PM, Ned Deily wrote:
> In article
> ,
> Matthew Taylor wrote:
>> Does this
In article
,
Matthew Taylor wrote:
> Does this make sense to anyone? I'm still a little new to Python in
> general (especially binary packaging), and it seems like this would be
> a common problem for any projects with C extensions that need broad
> binary distribution. Does anyone have any sugg
Hello pythonistas,
This is my first message to this mailing list, so if my question is
off-topic, please direct me to the correct mailing list.
I manage the NuPIC [1] open source machine intelligence project, which
is a python project with C extensions. We have a build on Travis-CI
[2] that creat
Ethan Furman writes:
> On 02/06/2015 02:56 PM, Ben Finney wrote:
> > It is a deliberate design decision that direct import of a module
> > makes that module blind to its location in the package hierarchy.
> >
> > That's a design decision I deplore, because it makes something that
> > should be e
On 02/06/2015 06:56 PM, Steven D'Aprano wrote:
Dave Angel wrote:
And don't name any source code __main__.py,
That's incorrect.
Starting from Python 2.6, __main__.py is reserved for the application main
script in packages. That is, if you design your application as a package
(not a single fi
Dave Angel wrote:
> And don't name any source code __main__.py,
That's incorrect.
Starting from Python 2.6, __main__.py is reserved for the application main
script in packages. That is, if you design your application as a package
(not a single file) with this structure:
myapplication/
+-- __i
On 02/06/2015 02:56 PM, Ben Finney wrote:
>
> It's not Setuptools per se, it's Python's import mechanism. It is a
> deliberate design decision that direct import of a module makes that
> module blind to its location in the package hierarchy.
>
> That's a
On Friday, 6 February 2015 22:20:58 UTC, Rob Gaddi wrote:
> I found a recommendation at https://chriswarrick.com/blog/2014/09/15/
> python-apps-the-right-way-entry_points-and-scripts/ that seems to say
> that I should get around this by simply having an empty __init__. I
> guess I can move the
nd narrow, well-specified
interfaces.
> Under other circumstances when the app has become substantial, the
> bulk of the application code winds up in, e.g. mainwindow.py, and the
> __main__ does nothing but call mainwindow.main().
Great! So you already have an entry point for Setuptoo
On 02/06/2015 02:20 PM, Rob Gaddi wrote:
>
> My library code isn't in __init__.py (or previously in __main__) because
> I'm trying to dodge recursive imports; it's there because the code is
> short enough and tightly-coupled enough that I didn't see upside in
> splitting any of it out to a sepa
prove the
>> ecosystem in recent years.
>>
>>> I'm developing applications of various size for internal deployment.
>>> When I'm actually getting the whole thing written, I've got my
>>> initialization stub in __main__.py, because it's an applicati
e thing written, I've got my
initialization stub in __main__.py, because it's an application rather
than a library. But then when I migrated over to setuptools I had to
switch it to __init__.py and change around all my import statements to
compensate. Then I can reference it as an entr
y
> initialization stub in __main__.py, because it's an application rather
> than a library. But then when I migrated over to setuptools I had to
> switch it to __init__.py and change around all my import statements to
> compensate. Then I can reference it as an entry point.
Yes,
ation stub in __main__.py, because it's an application rather
than a library. But then when I migrated over to setuptools I had to
switch it to __init__.py and change around all my import statements to
compensate. Then I can reference it as an entry point.
This feels silly. I'm sure I cou
.
I was trying to install scipy-0.14.0, it gives following error:
Warning (from warnings module):
File "C:\Python27\lib\distutils\dist.py", line 267
warnings.warn(msg)
UserWarning: Unknown distribution option: 'test_suite'
So I thought maybe I need to install setuptools f
- Original Message -
> From: "Surbhi Gupta"
> OK, the problem is now resolved: I just found out that we need to
> install from prompt instead of IDLE.
> Setuptools is installed, but I am not able to use easy_install from
> prompt. It says:
> easy_install : Th
on: 'test_suite'
>
> So I thought maybe I need to install setuptools first. I ran setup.py file in
> IDLE. it runs fine and then I can import it in current session. But when I
> run session, it still says 'no module named setuptools'. Same thing happened
> w
gives following error:
Warning (from warnings module):
File "C:\Python27\lib\distutils\dist.py", line 267
warnings.warn(msg)
UserWarning: Unknown distribution option: 'test_suite'
So I thought maybe I need to install setuptools first. I ran setup.py file in
IDLE. it runs
On 2014-10-23, Simon Kennedy wrote:
> If you're creating an sdist then you'll need to create a MANIFEST.in
> file in the same folder as setup.py with the following contents
>
> include share/test_file.txt
>
> If you're creating a bdist (egg or wheel) the parameter name you need
> is
>
> p
On Wednesday, 22 October 2014 19:43:25 UTC+1, luc2 wrote:
> hello, would you know how to make data_files work in setuptools ?
> i can't figure out how to put datas in the generated .tar.gz
If you're creating an sdist then you'll need to create a MANIFEST.in file in
the sa
hello, would you know how to make data_files work in setuptools ?
i can't figure out how to put datas in the generated .tar.gz
$ find .
./hello
./hello/__init__.py
./share
./share/test_file.txt
./setup.py
$ cat ./hello/__init__.py
def hello():
print( 'hello' )
$ cat ./shar
python setup.py bdist_wininst --install-script tklsystem-post-install.py
After I install my package using created windows installer, I can't
find where my shorcut is created, nor I can confirm whether my script
run or not.
How can I make setuptools generated windows installer to create
desktop or start menu shortcuts?
--
http://ysar.net/
--
https://mail.python.org/mailman/listinfo/python-list
es it started failing,
with the main error seemingly being the title, full error reported is
> pip install Jinja2
Wheel installs require setuptools >= 0.8 for dist-info support.
pip's wheel support requires setuptools >= 0.8 for dist-info support.
I've googled for this error,
On Fri, Jan 3, 2014 at 9:26 AM, wrote:
> File "C:\Python\lib\mimetypes.py", line 255, in read_windows_registry
> with _winreg.OpenKey(hkcr, subkeyname) as subkey:
> TypeError: OpenKey() argument 2 must be str without null characters or None,
> not str
Interestingly, I pulled up that file
setuptools 2.0.2, win7 x64, python 3.3.3 (64bit), tried as user (who is admin,
and as admin)
This started happening several versions ago. Could not track down a setuptools
support list. Any ideas?
C:\Users\tim\Desktop\setuptools-2.0.2>python setup.py install
Traceback (most recent call l
On 12/12/2013 11:13, Chandru Rajendran wrote:
Hi all,
Please help me with running Pep8 using setuptools. Also help me how to
Pep8 for files in a folder.
I don't understand what you're asking for. Can you please rephrase your
question.
Thanks & regards,
Chandru
On Thursday, 12 December 2013 11:13:51 UTC, Chandru Rajendran wrote:
> Please help me with running Pep8 using setuptools. Also help me how to Pep8
> for files in a folder.
The tool you're looking for is flake8. It integrates with setuptools, so that
you can run 'python
Hi all,
Please help me with running Pep8 using setuptools. Also help me how to Pep8
for files in a folder.
Thanks & regards,
Chandru
CAUTION - Disclaimer *
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of
Chandru Rajendran writes:
> How can we set the target folder for the package in Setuptools?
You do it at install time. In other words, it's not up to the author of
‘setup.py’ to decide; it's for the administrator installing your package
(or whoever set the defaults on that specifi
On 2013-11-25, Chris ???Kwpolska??? Warrick wrote:
> Tell your legal department that
[...]
Ha! good one!
In my experience, corporate legal departments have an "ask only" API.
All attempts to tell them things will be ignored.
--
Grant Edwards grant.b.edwardsYow! Will t
On Mon, Nov 25, 2013 at 9:35 AM, Chandru Rajendran
wrote:
>
> Hi all,
> How can we set the target folder for the package in Setuptools?
The answer likely is *you are not allowed to do this*. It’s up to the
user to set it.
Unless you are the user, and want to have the packages you inst
Hi all,
How can we set the target folder for the package in Setuptools?
Thanks & regards,
Chandru
CAUTION - Disclaimer *
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the inte
-us/library/cc755104.aspx
Setx should not require a reboot, but might require user
to log out and back in (or restart CMD). Also, note that
it modifies local environment by default and not system
environment.
[snip]
>
> Question 3: Does the Windows MSI installer from Python.org include
> Question 4: If the Windows MSI installer indeed lacks Setuptools, what is the
> best way to install it from the command line in a future-proof manner (on
> Windows)? I am imagining something like this:
>
> wget https://bitbucket.org/pypa/setuptools/raw/bootstrap/ez_se
> PIP would definitely do the trick. Does the MSI include PIP? If it does not
> include PIP, then how can I easily install it from the command line? I am
> looking for something like this:
Not yet, but I think just around the corner:
http://www.python.org/dev/peps/pep-0453/
Unlike most enhance
I am
looking for something like this:
wget https://pip.org/install/install_pip.py
python install_pip.py
This is totally theoretical. wget doesn't work, the URL is made up, and
install_pip.py is a fantasy of mine. ez_setup.py DOES exist for Setuptools,
which is why I am trying to use i
t CMD.EXE session?
Question 2: python-guide.org suggests adding C:\Python27\Scripts\ to the PATH
as well. When is that necessary or helpful? If I forget to do that and have
problems later, how can I tell the cause of the problems?
Question 3: Does the Windows MSI installer from Python.org include
> Date: Mon, 27 May 2013 21:26:21 -0700
> Subject: Re: How to: Setuptools
> From: rustompm...@gmail.com
> To: python-list@python.org
>
> On May 28, 9:09 am, Carlos Nepomuceno
> wrote:
>> --
1 - 100 of 314 matches
Mail list logo
